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

MelVin, if you source the nw.js files from the github repository - does that make a difference? The c2 installed files list has a couple of files that are different to those from the source, and when I replace them then I can get things working again (with no full screen, though)...

I haven't tested. I'm going to wait til Ashley comments before I go any further. This is the third time I have replaced the saved games feature. the default system just doesn't make saving/calling strings easy for me.

All this talk of workarounds seems a little premature to me. If this was the final version of NW then maybe but as it's still Alpha then everything could change and all the work done will be undone.

Except the save issue, how is NW 0.13 ? It is better than the last versions ?

Even though I'm migrating to Unity, in the meantime I would like to test the market with different games and C2 makes that easy.

And to be honest if we are waiting a little more, probably will not need NW at all: Edge on Win10 is smoking fast (and probably on WindowsPhone 10), Safari on iPhone/iPad works great... Probably we will need NW only on Android and older systems.

Except the save issue, how is NW 0.13 ? It is better than the last versions ?

Even though I'm migrating to Unity, in the meantime I would like to test the market with different games and C2 makes that easy.

And to be honest if we are waiting a little more, probably will not need NW at all: Edge on Win10 is smoking fast (and probably on WindowsPhone 10), Safari on iPhone/iPad works great... Probably we will need NW only on Android and older systems.

0.13 is about 20-25% faster on performance, using cpuutilisation as a metric for my own testing.

It doesn't suffer stutter (minus asset loading, which you can control via loading on start of layout).

We we still need a wrapper to make stand-alone .exe games for PC/MAC.

MelVin

That's what we found right away, cannot export with NWjs object, game wont start, blackscreens.

So anything that uses that object is a no-go until this bug is fixed. I'm writing a custom save/load using arrays & JSON write/read with NWjs file access, this goes into a set path, output into text files so that it may avoid future save issues. But we'll need the bugs fixed first with the current alpha5 and C2.

I tried removing the NW object in my game, but I still got blackscreen. Not sure what's causing it. :/

I hope that this gets stabilized by the next stable release of construct2!

The 20-25% faster performance is a huge huge improvement!

do you guys think that construct2 should ship with nw.js as part of the installer? I dont understand why it is separate at the moment

Info about performance is good news in did.

I hope that this gets stabilized by the next stable release of construct2!

The 20-25% faster performance is a huge huge improvement!

do you guys think that construct2 should ship with nw.js as part of the installer? I dont understand why it is separate at the moment

Because Construct 2 updates much more often than NW it would be redundant to have to download the same version of NW with every new C2 update.

Ashley

Any official input on these bugs? Are they something you guys can fix on your end or do we have to wait for the next iteration of Chromium and therefore, the next NW.Js built on that new Chromium?

Ashley

Any official input on these bugs? Are they something you guys can fix on your end or do we have to wait for the next iteration of Chromium and therefore, the next NW.Js built on that new Chromium?

Do we know if it's Chromium or NW bug?

do you guys think that construct2 should ship with nw.js as part of the installer? I dont understand why it is separate at the moment

The main reason it was separated was the download size: NW.js is ~130mb at the moment, and C2 is ~60mb. If you don't need to use NW.js and you don't have a fast connection, it's annoying to have to download 3x as much data. Also it allows us to update NW.js independently of C2.

Please allow a few weeks for bug reports to be investigated, as the guidelines describe.

Please allow a few weeks for bug reports to be investigated, as the guidelines describe.

Thanks. Perhaps prioritize the easiest bug for you guys to fix since it's C2-related:

The NW.Js C2 object is not compatible with r217 + NW 0.13.Alpha 5 NW export (blank screen on startup of .exe).

Fixing this would enable us to use the NW.Js object file read/write to work with our custom save system.

Ashley

megatronx

Colludium

MelVin

Tinimations

Danwood

MadSpy

Okay, some good news!!

Just tested the NW.Js 0.13 Alpha6 (latest live build today on github).

The cache/temporary session folder storage seems to be FIXED!

It's a set folder under:

C:\Users\bob2\AppData\Local\StarNomad2\User Data\Default\IndexedDB

In my game, its folder is: chrome-extension_ihbilmccnkojgdhdikkoikjihbfjeecf_0.indexeddb.leveldb

And it persists through game exit and relaunch.

It IS compatible with C2's Save/Load system! Hurrah!

But, still we cannot export using NW.Js plugin object, same blank screen bug on startup. So we cannot use custom save/load systems, having to go with C2's default Save/Load.

I spent a day making & testing a custom file save using NW.Js read/write, also making it possible to add mod support for the game via text files... but now the default Save/Load is working fine.

Also, Full-screen works fine. I use the Browser object to request & exit full-screen.

Going to proceed to test LocalStorage plugin see if that works too.

Basically if it does, then Alpha 6 is good to go and GreenWorks can be updated! <img src="{SMILIES_PATH}/icon_e_biggrin.gif" alt=":D" title="Very Happy">

EDIT: LocalStorage WORKS.

The triggers Exist, Missing etc works fine, retrieving data works.

0.13.alpha 6 is now operational! GreenWorks Steam plugin update time?! <img src="{SMILIES_PATH}/icon_mrgreen.gif" alt=":mrgreen:" title="Mr. Green">

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

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

— Great job on the testing! Any idea how 0.13 fares with the red loading bar issue on mac and linux?