Wild Chrome Browser Performance Vs Node Webkit

In Chrome on my browser I'm getting about 30 FPS but when I export and run on the desktop via Node Webkit I easily get 60 FPS.

Has anyone else experienced this?

Node webkit isn't chrome , awesomium was chrome ... It was reported less powerful by Scirra , I forgot where they wrote that but you get the point ...

Cheers...

It's chromium though isn't it? Are they not essentially the same thing?

Well, I don't know the major differences between the two

But Node is chromium combined with node.js ..

Ashley ?

Node-webkit is basically the Google Chrome browser (strictly speaking, Chromium). It has node.js features as well, but we don't use them much with Construct 2 (yet). It seems to work a lot better than Awesomium for us, even though they are supposed to be very similar.

Both Chrome and node-webkit v-sync their display. So if you get 59 FPS, in some circumstances it will get worst-case v-sync interaction and fall all the way to 30 FPS. So it's likely the difference is actually very small.

Ashley

Can we get some heads-up on what node.js features are you thinking about?

Ashley - so in Chrome browser my game is consistently 30fps and through Node-WebKit it's 60fps consistently.

Is this a bug with Chrome then?

No, as I said in my post it is most likely actually a very small difference, but it's interacting badly with V-sync.

Okay, is this typically indicating a performance issue with my game? Just trying to figure out how to fix the issue.