Guide: Fix Jank in r190+ Node-Webkit Export

  • 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...

  • ome6a1717

    Sorry, I just don't understand you. Are you say that node is 'janking' on preview, but not on export? Or that the 64 bit version is janking? What version of C2 are you on? I haven't migrated to r195 yet, so I'm not sure if this guide will still work with it.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • TiAm - I'm saying it works with neither preview or export, but if I export and then replace the files in the exported win32 folder, it runs fine (meaning somehow it's not loading the correct version of node-webkit on preview).

  • ome6a1717

    I'm afraid I still don't quite understand. Which files are you replacing post-export that get the game to run correctly? Have you run dxwebsetup.exe (maybe you are defaulting to canvas2d mode)?

    Anyway, I'm also bumping this thread to let everyone know that Node-Webkit 10.5 still works in C2 r195, the latest stable. Personally, I still prefer it to the latest version of node, which has been renamed NW.js.

    Still, NW.js is the best version since 10.5, so it might be worth checking out. Here's a thread by Ashley where he links to an alpha version:

  • TiAm why do you still prefer 10.5? 12 alpha2 seems to fix every jank problem for me, even though CPU usage is still weirdly higher than 10.5 and previous. But overall, i feel the game runs even smoother (placebo?).

  • Danwood

    Basically, for the very reason you mentioned: cpu use seems to be a bit higher. Also, I have seen some isolated stutter, though it's very minor and infrequent. On 0.10.5 I don't see any jitter after the first few seconds. And, of course, there is the 'alpha' part; 10.5 was a very stable release that has minimal bugs, whereas 12.x is still pretty new.

    All that being said, I'm thinking (hoping) this thread won't be relevant much longer, as the newest release is coming pretty close to parity.

  • TiAm yea let's hope to see this issue closed soon, i want the best for me gama, biatches!

  • TiAm - when you export via node-webkit, it creates 6 (I think?) folders. Linux32, 64, OSX 32, 64, and WIN32, 64. Basically I'm taking the updated files from Ashley and copying them and replacing them over the WIN32 folder from my export and running that. So when it works, it's not actually working from a preview mode in Construct, but it's working from the actually exported nw.exe file. Hopefully that makes a bit more sense?

  • 10.5 still runs better for me. Smooth as butter, baby!

  • Hey, anyone know if this still works in recent C2 builds after the change to 'nw.js'?

    I tried putting the old PC, mac and linux files into the 'NWjsForC2' folder as well as the 'NodeWebkitForC2' folder. Every time I try to export, C2 tells me that nw.js is not installed.

  • One thought: there was no 64 bit version of node for 10.5, so if you deleted all the 64 bit folders, C2 might be complaining about that. Try copying in the win/osx/linux64 folders from a newer release; leave the 32 bit folders with the 10.5 packages.

  • sqiddster

    Just tried an export from r200, works fine for me. My 32 bit binaries are all 10.5.

    Here's my whole "NodeWebkitForC2" folder; hopefully you could just copy this into program files and get it to work:

    https://drive.google.com/file/d/0B08LZ- ... sp=sharing

    If not, could be there's a path name stuck in the registry. If so, I'd try:

    1. Install an old package of node-webkit, like:

    http://downloads.scirra.com/nwjs/nodewe ... 0-11-5.exe

    mirror:

    https://drive.google.com/file/d/0B08LZ- ... sp=sharing

    2. Delete the resultant "NodeWebkitForC2" folder, and paste my folder in it's place.

  • sqiddster

    Just tried an export from r200, works fine for me. My 32 bit binaries are all 10.5.

    Here's my whole "NodeWebkitForC2" folder; hopefully you could just copy this into program files and get it to work:

    https://drive.google.com/file/d/0B08LZ- ... sp=sharing

    If not, could be there's a path name stuck in the registry. If so, I'd try:

    1. Install an old package of node-webkit, like:

    http://downloads.scirra.com/nwjs/nodewe ... 0-11-5.exe

    mirror:

    https://drive.google.com/file/d/0B08LZ- ... sp=sharing

    2. Delete the resultant "NodeWebkitForC2" folder, and paste my folder in it's place.

    Works for me. Thanks.

  • Thanks so much for this! Fixed an issue I was having with exporting crappy builds on PC

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)