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

Discussion and feedback on Construct 2

Post » Fri Nov 13, 2015 10:14 pm

Great news:

The nasty memory leak (memory-leak-in-chromium_t163711) bug in NW10.5 and NW12 is fixed! :mrgreen:

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"

Image

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
Last edited by Silverforce on Tue Nov 24, 2015 8:29 am, edited 3 times in total.
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,614

Post » Fri Nov 13, 2015 10:20 pm

that souns terrible :s
B
35
S
13
G
6
Posts: 1,645
Reputation: 8,792

Post » Fri Nov 13, 2015 10:24 pm

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. ;)
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,614

Post » Fri Nov 13, 2015 11:01 pm

I agree @Silverforce. NW a5 also doesn't (yet) support kisok mode using
Code: Select all
var gui = require('nw.gui'); gui.Window.get().enterKioskMode();


It's a long way from release status, but I am looking forward to when it becomes reliable for us to use.
I only occasionally visit - I'm learning C# for Unity, but c2 is still a respectable game engine imo....
B
73
S
19
G
66
Posts: 2,198
Reputation: 42,193

Post » Fri Nov 13, 2015 11:18 pm

Colludium wrote:I agree @Silverforce. NW a5 also doesn't (yet) support kisok mode using
Code: Select all
var gui = require('nw.gui'); gui.Window.get().enterKioskMode();


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. :x

Can only hope 0.13.a5 is improved/fixed in time and the updated GreenWorks is ready! :D
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,614

Post » Fri Nov 13, 2015 11:27 pm

I also experience bugs when loading a game cerated and saved after the update...
B
63
S
22
G
4
Posts: 357
Reputation: 6,503

Post » Fri Nov 13, 2015 11:48 pm

Danwood wrote: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.
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,614

Post » Sat Nov 14, 2015 12:24 am

@Ashley

Okay, found the bug @Danwood

NW changed its default directory for data and cache.

It's now like this:

Image

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:

Image

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.
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,614

Post » Sat Nov 14, 2015 1:11 am

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.
B
12
S
4
G
1
Posts: 137
Reputation: 1,519

Post » Sat Nov 14, 2015 2:01 am

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.
B
63
S
22
G
4
Posts: 357
Reputation: 6,503

Next

Return to Construct 2 General

Who is online

Users browsing this forum: Yahoo [Bot] and 8 guests