Yep. I keep getting logged out, then I log in, and it takes me to a login page where I need to login a second time. I've started just pressing the login button with no info inputted on the first one to just get to the second one.

Hmm... I tried adding --ignore-gpu-blacklist to the package.json and package-preview.json files you linked, and it didn't work, still getting software rendering.

What does work, however, is making a shortcut to the exported exe file, right clicking it, and editing the properties so that the target is:

"C:\path\nw.exe" --ignore-gpu-blacklist

Then running the shortcut, I get 60 fps again. I tried modifying the shortcut to use --disable-software-rasterizer, but it still didn't work. Kinda odd that --ignore-gpu-blacklist doesn't work in the package file when it works in the shortcut.

It seems that chrome 33 has helped some people, at least: https://www.scirra.com/forum/viewtopic.php?f=146&t=95751&p=740373#p740373

I tried both, and neither worked. The only thing that's worked has been enabling the flag to override the software rendering list in chrome://flags (ignore-gpu-blacklist).

Hey, cool! Take some pics of the booth while you're there, and let us know how it goes!

Awesome, Tom it's working here!

I noticed the link that I thought went to the first unread post on the topics list actually goes to the last post instead. Also, it's really, really tiny and I keep missing it on my ipad and often tap the username instead accidentally.

Could there be an extra link to go to the most recent unread post instead? I know there is one in the thread itself, but that makes it a two click process - first the topic needs to be clicked, then 'first unread post' which often requires navigating to a second page.

I can't see it either. Tom?

Sorry I wasn't clear, both chrome 33 and node webkit in 163 are affected by the performance problem, same as chrome 32. Chrome 33 has resulted in no improvement and I'm still getting single digit fps when fullscreened. I was able to get 60 fps before in chrome 31/node webkit r159.

*Lol, also just noticed that my Gravitar is still showing a different image than the one on my profile.

What's up with that?

You might have multiple avatars uploaded for different sizes - I recall you can do that with gravatar.

Argh - still getting software rendering here.

At this point I think you should release a 163.2 and reimplement the hack you had before to get it to avoid software rendering. I'm stuck on version 159 so I can keep using node webkit before it was switched to use chromium 32.