Guide: Fix Jank in r190+ Node-Webkit Export

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">

Well, related to node webkit if anyone is interested about how building works, this old tutorial of before the support was built in (the good ol' awesomium times), if it still works (it should), that may be another alternative, you just export your html, you wrap it up with the older version of node webkit you should be able to find on the internet, that may be less troublesome than making C2 believe you are using the latest one (and also could be applicable outside C2), unless C2 only activates the node webkit api depending on the chosen exporter maybe.

https://www.scirra.com/tutorials/417/ou ... ode-webkit

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

It is just that little hacks like this are working, but the fact people have trouble with the duality of C2 and node webkit is not a very good sign, thus I wanted to share somethings that sort of shows how that works behind the scenes, not that "in topic" now that I think about it (even though it shows that you just bundle files and parameters within node webkit to define what happens, which assure there is no reason for it to fail).

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.

Works in OSX 32 too?

Good work, — I kind of hope that this is made easier in future....

— media

I don't know, don't have a Mac. I assume the same approach would work. If you try it, let us know.

Colludium

Me and you both...

I know that we rely upon 3rd party wrappers or browser for - everything html5.... But I am pretty sure that if we contracted out our export to desktop option and it broke over night then the message would not be to wait until things improve (indeterminate time frame, could be 2-6 months) - a rapid reversion to what worked before would be implemented whilst the problem was addressed. I could not imagine this happening with Unity, for example. This should be no different IMO; I don't understand how a high standard of product can be confused with using a wrapper's latest update.

It's new! It must be better!

...Right?

TiAm

aaahhh... it feels smooth like hot knife going trough butter DD feels damn good after so long of seeing the newest NW

I know that we rely upon 3rd party wrappers or browser for - everything html5.... But I am pretty sure that if we contracted out our export to desktop option and it broke over night then the message would not be to wait until things improve (indeterminate time frame, could be 2-6 months) - a rapid reversion to what worked before would be implemented whilst the problem was addressed. I could not imagine this happening with Unity, for example. This should be no different IMO; I don't understand how a high standard of product can be confused with using a wrapper's latest update.

Agreed that C2 and node webkit should be completely separated (in fact, this is what they were trying to do, but the jank caught them off guard, still, they could have done it better I think, like giving the older ones and getting it to still work). But for some what da hell reason, node webkit is a part of C2 license (even though I would be confident that only the easiness of export is, as node webkit cannot be a selling point, not sure about the term of use of node webkit, that and why would it be a selling point anyway when we think about it, it is a freaking html5 engine, wrappers were always an operation to do separetely, if we have to build mobile apps via the XDK, why not for node webkit, never understood that).

I agree Aphrodite, and hope I didn't come across too harshly before. I see the reliance on third party software as a strength and a weakness with c2. The strength is it allows our one man developer coding hero to focus on the editor; the weakness is it allows our one man developer coding hero to focus on the editor.

Ashley is right to play the long game, but by dismissing the current quality of c2 desktop exports as a temporary glitch (with an unknown fix date for people who don't have the confidence to use the command prompt and manage their own export - precisely the kind of person who buys a no code game engine) it makes it appear a bit like c2 is still in development.

Or rather, we feel every third party problem - but we have control over this one so we should exercise that control. As to Ashley's inability to reproduce the problem, it might well be a system specific issue, but I imagine that any hardware with less than awesome spec will be affected (must have a 60 hz screen, I think). This test was created by someone else and it clearly shows the problem in Chrome (sorry, can't go into Node).

I didn't mean to come over unappreciative of the work done so far by Scirra, I really highly rate c2 for its unique approach to game dev... but it sometimes feels like we don't know where the wind will take us next, or when.

All those steps to get the 0.10.5 version?

just download it from here: https://github.com/rogerwang/node-webki ... d-versions

N00b!

Danwood

You sure it's the same? If so, I'd be glad to lop off the 'install r184, grab nw files out of it' steps. I'll check it out tonight.