NW.js 0.14 RC1!

http://dl.nwjs.io/live-build/03-27-2016 ... e-13916ba/

OMG, going to refresh this page all nite long! <img src="{SMILIES_PATH}/icon_e_biggrin.gif" alt=":D" title="Very Happy">

It's an omen to future export flux....

Ok, i tested the nacl version of NW.js 0.14 RC1, removed the nacl related files and it works fine, didn't made extensive performance test, but looks like there is a performance improvement for my game (that is very CPU demanding).

PS: or maybe it's just like a placebo? pls someone make a proper test

NW.js updates now just follow Chrome updates. 0.13 was a new architecture but I think the 0.14 release is just more of the same and nowhere near the jump 0.12 to 0.13 was.

NW.js updates now just follow Chrome updates. 0.13 was a new architecture but I think the 0.14 release is just more of the same and nowhere near the jump 0.12 to 0.13 was.

At least it doesn't require C2 to change for the new architecture, let's see the bright side

After many testing sessions, my partener Giulio reported our game beneficts from nw 0.14 in terms of CPU load, around 20-30% less load!

I tested as well and found the same on my i5 laptop.

Guess Chrome 50 made some improvements

Danwood, I'll give it a test in Star Nomad 2. It's also very CPU intensive.

Alright, test done. Big fleet battle scenario.

On NW 0.13 alpha and RC, I get ~50% to 60% CPU usage on the main logic thread, as reported by cpuutilization.

On NW 0.14 RC1, I get ~36% to 45% CPU usage.

This is a significant improvement under peak load conditions.

Under idling conditions, it's still around 10-15%, no change.

Looking forward to GreenWorks shipping with C2 and moving from experimental status!

RC2 is available http://dl.nwjs.io/live-build/03-31-2016/6c3b54c-7368d6c-f17e9ae-998c2db/v0.14.0-rc2/

Yeeee so we were not allucinating

Just played with RC2 and was very impressed with the performance improvement!!

However, I am still finding that the nw.js app is not always closing (clearing out the AppData folders for nw.js and my game sorts it out) but it reoccurs on occasion and I've not yet figured out the common link...