NW.js v0.12.0 alpha 3 (Chromium 41) 13th Feb, Discussion

10.5 works fine, so the question is, why update?

10.5 works fine, so the question is, why update?

I recall seeing some people complaining about some bugs with the 10.5 build (I think it was related to form controls but I am not sure), for them, updating was sort of necessary, also, 64 bit support (but losing XP support I think).

But I agree with you completely that if it does not bring anything worth it, staying at the same version is fine for now.

I checked the performance of 0.12.0-alpha3 before release and it was perfectly smooth here - hardly a jank visible.

Staying on old versions is not really a viable long-term strategy, since you will not get any of the new features or other performance improvements of future Chromium updates.

Perfect!

When one of the newer versions runs my game better than 10.5, I'll definitely switch to it.

I'm getting this problem from the Steam forum using Node Webkit 10.5

The game wont start. [Mac OS X 10.10.2] (the loading bar turns red, unlike on other Max OSX versions where it launches ok)

Seems like it's the very last version of Mac OSX. Do you guys are aware of this?

I might switch to NW.js v0.12.0 alpha 3 only for this reason if it fixes this problem, but I would have to add a timer on start as I get the initial 10sec janks after the loading.

So, if we use node-webkit as the preview browser, does it now access the NWjsForC2 installation instead of the old NodeWebkitForC2 folder?

So, if we use node-webkit as the preview browser, does it now access the NWjsForC2 installation instead of the old NodeWebkitForC2 folder?

Correct. I just keep two folders for node. When I want Construct to use a specific one I just add "_" to the beginning of the folder name to disable it.

use old node :

NodeWebkitForC2

_NWjsForC2

use new node :

_NodeWebkitForC2

NWjsForC2

Aurel - are you using the latest C2 beta? We fixed an issue with Mac NW.js exports since the last stable.

Does the new node fix the issue with missing libudev.so.0 on linux distributions causing games not to run?

Thanks — - that seems like a simple approach.

Aurel - I can confirm you're safe to use the latest beta. I've been using it for a couple weeks and no complaints from customers.

Does TTS work from Construct 2? In the past it did not work because they made the TTS part a separate plugin in nw.js.

Just tested NW.js 12.0-alpha3 with r197 :

For me, the jank is there in the first 10-15 seconds and very subtlety here and there, BUT only during NW.js preview.

On an actual export... ALL jank is gone. Not sure why this is, but I'll take what I can get.

**EDIT**

Freshly installed both r197 and NW.js alpha3 - All is good and jank/jitter free on previews and exports for PC.

So far so good

Win 7

3.3 GHz Xeon

32 GB Ram

GTX 650 Ti

C2 - r197

Aurel - are you using the latest C2 beta? We fixed an issue with Mac NW.js exports since the last stable.

Ashley Thanks for telling me!

No, by safety, I still was on r186.2 + nw10.5. I only tried the new C2 builds for pleasure (and they were very very good!)

I just installed r197 and I'm now trying to export using nw.js 0.12 alpha3 to see if this fix the Mac problem. All I get is a black screen at launch on PC, but I guess having 2 Construct and 2 different Greenworks versions doesn't help... I guess it's time for clean up AND for the leap of faith! I'll keep you posted here.

EDIT one hour later: nope, even with a clean install, NW.js export works very well with no janks with a Greenworks-free project, but only display a blackscreen with a project featuring the Greenworks plug-in.

Oh, Also, like Prominent , i would be very interested in knowing if the lastest NW.js change something on the Linux front : )

It may seems less important than PC/Mac, but a lot of publishers/partners set it mandatory now.

— Very glad to know, thanks!