A warning about the recent NW release

NW.js v0.24.0 (stable) is more CPU intensive than a previous version.

The Beta1 from june 15, from my tests, uses much less CPU.

https://dl.nwjs.io/v0.24.0-beta1/

Just a warning, i don't know what's the reason, but i reverted back to Beta1 and stick with it until next version comes out <img src="{SMILIES_PATH}/icon_rolleyes.gif" alt=":roll:" title="Rolling Eyes">

It's probably less confusing to users if you stick to the supported version on the forum.

https://www.scirra.com/nwjs

It's probably less confusing to users if you stick to the supported version on the forum.

https://www.scirra.com/nwjs

Which is exactly the one that's more CPU intensive, assuming you don't revert back to 0.23.0 <img src="{SMILIES_PATH}/icon_rolleyes.gif" alt=":roll:" title="Rolling Eyes">

You should provide tests with measurements to back up this claim, and then if you can prove it, file an issue with NW.js so they can investigate and fix the issue if something's wrong. Otherwise posts like this are little better than scaremongering.

I thought it might fix my overlay issue on steam (of course it was --in-process-gpu) and i updated to this version.

Now many people have problems with the game getting stuck after some time and i think it might be nw.js v0.24

how-do-i-know-if-quot-save-quot-and-quot-load-quot-worked_t195592

Ive downloaded v0.23 but now not even preview in Construct 2 is working at all!

Can we fix that?

And also, if you help me fix it and then upload the downgrade on steam, would it work or people have to do some things manually?

Ive deleted the files from appdata\local and it worked but have problems.

It just let the player play a bit more and it got stuck on the next level