0 Favourites

NW0.13.alpha5 Testing Report **Alpha6 Works!!**

  • Great news:

    The nasty memory leak (memory-leak-in-chromium_t163711) bug in NW10.5 and NW12 is fixed! <img src="{SMILIES_PATH}/icon_mrgreen.gif" alt=":mrgreen:" title="Mr. Green">

    Now the nw.exe process is much more aggressive in flushing memory, changing layouts will trigger a clearing a few seconds into the new layout. The memory usage does not escalate endlessly leading to stutter (& crash) after some time of play (time varies on size of game).

    Another GREAT news:

    cpuutilisation tracking shows a major reduction. This means a big performance improvement. On average, I am seeing around a 20-25% performance speed up for my logic bottlenecked RTS-style AI battles.

    A really bad news:

    Save game state not compatible with NW10.5 or NW12. LocalStorage does not carryover nor does the Save/Load state. Obviously you all can understand the implications. Pretty much if you are on an older NW and already published, updating to this = wiping your gamer's saves = not happy gamers.

    Some weirdness:

    It seems to ignore or does not process the local storage triggers like "exist/missing"

    This used to work. It would enter full-screen by default, and subsequently it checks the localstorage key first, sets it, then fullscreen or or window mode based on the saved setting. Now it does not trigger.

    Alpha 6 Download: http://dl.nwjs.io/live-build/11-23-2015 ... .0-alpha6/

    Just extract it over your NWForC2 folders, win32/64 etc.

    Post: nw0-13-alpha5-testing-report-alpha6-works_t163879?start=70

  • that souns terrible :s

  • Everytime devs mention "significantly reworked" or along those lines, I always instantly fear "save game state not compatible"... I posted that in the GreenWorks thread immediately after Ashley talked about 0.13.a5, and it is as I feared.

    But moving forward, this transition needed to happen. Most of us who publish on PC/MAC are still stuck on Chromium 36 since 38 introduced bad stutters which hasn't been fixed for a long time. On top of this, the memory leak affects bigger games real quick, stutters start after an hour of play leading to potential crash.

    So with Chromium 46 onwards, we get smoother gameplay, faster JS engine (great for mobiles, good for PC) and no more memory leak. Eventually we have to move on. Hopefully Google doesn't screw up future Chromium as badly.

  • I agree Silverforce. NW a5 also doesn't (yet) support kisok mode using

    var gui = require('nw.gui'); gui.Window.get().enterKioskMode();[/code:3ff1q81j]
    
    It's a long way from release status, but I am looking forward to when it becomes reliable for us to use.
  • I agree Silverforce. NW a5 also doesn't (yet) support kisok mode using

    var gui = require('nw.gui'); gui.Window.get().enterKioskMode();[/code:2o9bzba1]
    
    It's a long way from release status, but I am looking forward to when it becomes reliable for us to use.
    

    I'm hoping to launch next month on Steam.. at this point I can't go with NW12 because it janks and the memory leak. Can't go with NW10.5 due to memory leak as well as the incompatible save-state for future NW, it means if I go with 10.5 I'm stuck on that forever and can't use newer C2.

    Can only hope 0.13.a5 is improved/fixed in time and the updated GreenWorks is ready!

  • I also experience bugs when loading a game cerated and saved after the update...

  • I also experience bugs when loading a game cerated and saved after the update...

    I haven't had this, saves and loads fine.

    But I think Ashley may have to take a look at your project to find this bug. We all do not want save-game bugs, ever, period.

    I encourage everyone to post any bugs they find in this thread so we can keep it all together in one place for Scirra to easily see all the potential issues.

  • Ashley

    Okay, found the bug Danwood

    NW changed its default directory for data and cache.

    It's now like this:

    Before it did not have extra sub-dir /User Data/default.

    LocalStorage is empty because it's probably looking at the wrong folder to save/load keys.

    Also the save/load bug is related to this:

    Before, there was only ONE folder generated for IndexDB.

    Now each session of nw.exe game start will generate a new folder. It's behaving as if its a temporary cache.

    As such, your save data won't be recovered properly.

    The Chromium/NW.Js team messed up big-time in how they handle LocalStorage and IndexDB.

    This is basically unusable without a new Chromium/NW.Js build.

  • Construct 3

    Buy Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Buy Now Construct 3 users don't see these ads
  • I'm wondering if anyone else is not getting a mac 32 bit release now?

    I reverted back to the nw.js before this one that I was using before but still don't get a 32bit IOS release so it may be the construct update and not nw.js.

  • Great find Silverforce!

    But it also happens with the brwoser (chrome) after C217, as i save, i can't reload anymore and a bunch of bugs show up. So i think it's related on C217, not NW.js.

  • I'm wondering if anyone else is not getting a mac 32 bit release now?

    I reverted back to the nw.js before this one that I was using before but still don't get a 32bit IOS release so it may be the construct update and not nw.js.

    Support for mac 32 has been dropped in the new update

  • Definitely speed increase on the Mac side. Even when running this on Windows 8.1 VM got a large increase in performance.

  • Definitely speed increase on the Mac side. Even when running this on Windows 8.1 VM got a large increase in performance.

    Yup, its a nice speed increase as well as stability.

    Shame about the completely broken LocalStorage & Save/Load states.

    Chromium so far has been 2 steps forward, 1 step back...

    But it's getting there. It's close. I can feel it!

  • Preview seems fine but on export i just get a black screen with both 32 & 64 bit windows. No errors just opens the game window and stays black.

  • Right i found deleting the NWjs behavior allows my project to run now.. but local storage isnt working as it should, as mentioned by Silverforce.

    Thats a real shame.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)