Well, some users are having issues with the newest version of node-webkit, but your symptoms sound different. Or...maybe not.

How do you define a 'big freeze'? A few frames? A half second? Many seconds?

Have you tried exporting any of the template game projects that come with C2?

Here's a capx. Should be self explanatory.

https://www.dropbox.com/s/j07b7ppqp0q31 ... .capx?dl=0

Welcome to the community <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

Dead simple if you are using the bullet behavior. Just set a global var (BulletLife) with the maximum distance you want the bullet to travel. Then:

Foobar.Bullet.DistanceTraveled > BulletLife

--Destroy Bullet

Here's a capx:

https://www.dropbox.com/s/6rllxv4a0a7uj ... .capx?dl=0

It's a good point Aphrodite. I've been meaning to look into manual packaging of node-webkit app's, but ATM it's a way's down on my priority list. I want a finished project with a solid base of gameplay and performance before I dive into micro-tweaking. I certainly don't want to have to go thru all that fuss when I just want to preview a project. But for my final release? Yeah, manual export would certainly be worth a look.

Well, more advanced search has been a hot request for ages...but my understanding is that it's a less-than-trivial thing to implement.

You could try opening the data.js/c2runtime.js file and search for the word in there. I would suggest the excellent text editor Notepad++. It has a very advanced search function.

http://notepad-plus-plus.org/

Aphrodite

Actually, swapping out the new node for the old one is pretty straight forward; just delete the new files and copy the old ones in. I just tried to cover every little step, in case newer users needed to do this. And, of course, as with any 'hack', YMMV

Ashley

My first impression was similar to yours. The random jerking in node 0.11.1 doesn't appear as bad as Chrome v38 (in fact, it seems non-existent).

However, the v-sync appears to randomly fail, causing the terrible stop-go effect that typifies this behavior. It will even go in and out during the same session of gameplay. I cannot reproduce this in the older version of node from r184.

I am just one person, and am only testing on one computer...but others are reporting similar behavior, and google itself admits vsync issues with v38.

I don't really think there is much more to say about it.

Foreword:

This guide only applies to Windows 32-bit exports (win32). I imagine a similar procedure would work for the other exporters, but I don't have a mac platform available, and I don't have time to go thru this on linux.

64 bit exports are going to jank; there is no 'older' version for them since 64 bit support is a recent development.

To summarize: we are going to replace the new, 'jerky' version of node-webkit (0.11.1) with the older, more stable version (0.10.5) that shipped with the last stable, r184. If you wish to reverse this change later on, just reinstall 'nodewebkit-for-c2.exe'.

A.

I've updated to r190+...and all my node-webkit exports jank!

You need an earlier version of node-webkit. Get it here:

http://dl.node-webkit.org/v0.10.5/node- ... n-ia32.zip

1. Extract 'node-webkit-v0.10.5-win-ia32.zip'. Inside are 8 files and a sub-solder "locales". Copy everything EXCEPT "locales", 'credits.html', and 'nwsnapshot.exe'. You should be copying 6 files. 2. Go to 'C:\Program Files\NodeWebkitForC2\win32'. Should be 7 files there. Select all files EXCEPT 'dxwebsetup.exe'. Delete them, and paste in the 6 files copied from "node-webkit-v0.10.5-win-ia32". 3. You're done! Bring up C2 and export a project as node-webkit. Then, go to the win32 subfolder for your exported project, and launch the '.exe' file with your project's name. It should run smooth as silk.

NOTE: To re-iterate: 64 bit exports are going to jank; there is no 'older' version for them since 64 bit support is a recent development.

B.

I want to upgrade to r190+ from r184...but I don't want my node-webkit exports to jank...

1. We're going to skip re-downloading the older node-webkit files, since you already have them. Go to 'C:\Program Files\Construct 2\exporters\html5\node-webkit', select everything in the folder, and press copy. 2. Now, create a folder called "Node-Webkit for C2 - r184" somewhere else, and paste the copied files into it. 3. Take a deep breath. Then, install 'construct2-r190-setup.exe' and 'nodewebkit-for-c2.exe'. 4. Back to "Node-Webkit for C2 - r184". Go to the subfolder 'win32'. Now, select everything here EXCEPT subfolder "locales" and copy it. You should be copying 7 files. 5. Go to 'C:\Program Files\NodeWebkitForC2\win32'. There should be 7 files in it. Select them all, delete them, and paste in the files copied from the r184 folder. 6. You're done! Bring up C2 and export a project as node-webkit. Then, go to the win32 subfolder for your exported project, and launch the '.exe' file with your project's name. It should run smooth as silk.

NOTE: To re-iterate: 64 bit exports are going to jank; there is no 'older' version for them since 64 bit support is a recent development.

Hopes this helps some people out. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

Colludium Nesteris

I got the old exporter working in r190 without issue. Though...I did do the test on a secondary machine that isn't hooked up to the internet.

Anyway, I don't know if there might be hidden glitches, but it appears to work fine. I've got a writeup on how to do it that's about 95% done; it'll be up in the general forum in a few minutes.

Ashley

This isn't an issue with node, it's an issue with vsync in chromium v38, which node-webkit 0.11.1 is based on. This has been hashed over on the forum ever since v38 stable came out, and with respect to node ever since you updated it a couple beta's back.

For power users there are work around's, but anyone trying out C2 for the first time (liable to be a lot of those right now...the holidays you know) is going to go "WTF, a bouncing ball jerks?" and move on. There's nothing you can do about FF or Chrome...but this seems like a really bad time to bork desktop export for 90% of users.

Does anyone have the last version of the node? Was it ever released in the current form, ie a separate installer called "nodewebkit-for-c2.exe"? I guess I'm stuck on the last stable for now, unless r190 can have the older node installed over it...

Frankly, I'm waiting a bit on r190...but that's because of node-webkit.

I think part of the 'jerkiness' you are seeing is simply due to having a fast moving object without induced blurring. Here's a capx with a speed dependent motion blur effect added (no webGL, just an extra sprite). You can toggle the effect on and off, and adjust the timescale to see it in 'slo-mo'. You might find it useful.

https://www.dropbox.com/s/60iw05zkc9nfh ... .capx?dl=0