Guide: Fix Jank in r190+ Node-Webkit Export

Question - I'm using C2 64bit version for windows 8. Would I experience any problems by instead running C2 32bit in order to use NW 10.5? Thanks.

PSI

You shouldn't. Just smoother gameplay.

TiAm - thank you.

PSI

Actually, just to clarify, you aren't talking about the actual C2 IDE are you? Doesn't matter whether you use the 64 or 32 bit version of C2; all that matters is the version of the node-webkit exporter.

OK, got it. Thanks.

BTW - thanks for this guide - works great!

New build!

Node Webkit v0.11.5 (based on Chromium 38)

https://www.scirra.com/node-webkit

New build!

Node Webkit v0.11.5 (based on Chromium 38)

https://www.scirra.com/node-webkit

Any better? I'm thinking we won't see a significant improvement til chromium 39-40...but I'd love to be surprised. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

Thanks for this guide, was a great help, seems like this improve performances (running on 32bits and not 64bits). I will try it on a bigger project to see if it helps. I have a really noob question though. Is it possible to export for the web with a different exporter (using base construct2 web exporter) ? (Since the jerkiness happens on chrome browser with the web exporter).Thanks

> New build!

>

> Node Webkit v0.11.5 (based on Chromium 38)

>

> https://www.scirra.com/node-webkit

>

Any better? I'm thinking we won't see a significant improvement til chromium 39-40...but I'd love to be surprised. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

I was running 11.5 It's better than previous, but I have way better performance from 10.5 after following this guide. This Node issue / C2 export issue is beyond annoying. It's getting to a point where I am seriously considering switching from C2 to something that exports to desktop properly. Nothing like working on your game and then out of no where.. janky stuttering. Try and fix, and realize that Node is the root cause. Pretty dampening to the workflow, motivation, and optimization efforts. <img src="{SMILIES_PATH}/icon_neutral.gif" alt=":|" title="Neutral">

>

> > New build!

> >

> > Node Webkit v0.11.5 (based on Chromium 38)

> >

> > https://www.scirra.com/node-webkit

> >

>

> Any better? I'm thinking we won't see a significant improvement til chromium 39-40...but I'd love to be surprised. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

>

I was running 11.5 It's better than previous, but I have way better performance from 10.5 after following this guide. This Node issue / C2 export issue is beyond annoying. It's getting to a point where I am seriously considering switching from C2 to something that exports to desktop properly. Nothing like working on your game and then out of no where.. janky stuttering. Try and fix, and realize that Node is the root cause. Pretty dampening to the workflow, motivation, and optimization efforts. <img src="{SMILIES_PATH}/icon_neutral.gif" alt=":|" title="Neutral">

I was feeling the same Facecjf. It's sad, and i don't think Construct2 can do anything about it (and we are not talking about any kind of bad optimisation, since it's the same with super basic tests).

I'm annoyed too but my project was still in the prototype phase and not too advanced so ...

But for those how had games running smoothly before, it must be a real down.

I was feeling the same Facecjf. It's sad, and i don't think Construct2 can do anything about it (and we are not talking about any kind of bad optimisation, since it's the same with super basic tests).

I'm annoyed too but my project was still in the prototype phase and not too advanced so ...

But for those how had games running smoothly before, it must be a real down.

It is and it isn't. It's the nature of constructs reliance on 3rd party wrappers. I've found that what doesn't work now... will work in about 4 months.

Don't get me wrong, C2 is amazing for 2D game development, with great update cycles, stability, and features. I just wish desktop publishing was better and not reliant on Node.

For information purposes:

I tested previews and exports with the following versions of C2 and NW.

(r190, r192, and r193) + NW 11.5 = still stuttering.

I reverted back to NW 10.5 (Win 32bit) and it's smooth again.

Hardware Specs:

xeon 3.5ghz

32 gb ram

solid states

nvidia gtx650 ti

These are just my findings, though I am curious of others results as well

For information purposes:

I tested previews and exports with the following versions of C2 and NW.

(r190, r192, and r193) + NW 11.5 = still stuttering.

I reverted back to NW 10.5 (Win 32bit) and it's smooth again.

Hardware Specs:

xeon 3.5ghz

32 gb ram

solid states

nvidia gtx650 ti

These are just my findings, though I am curious of others results as well

Thanks for testing and sharing.

I looked at the changelog and it seems pretty minor, just two changes listed:

Fix: Normal frame should not simulate user input events (File input dialog) Fix: crash in debug session of WebStorm (WEB-14378)

I am a bit curious what that first change means exactly. Anybody here understand the platform well enough to explain?

This doesn't exactly seem to be working for me. I replaced the files in BOTH 32 and 64, but it still seems janky. However, when I export it and replace the files in the export 32 folder, it plays fine. I'm wondering if I have it set to always use 64 bit node webkit. Is there a way to change this to make sure it's loading the 32 bit? I even tried placing the 32 bit in the 64 bit folder...