NW.js 13 Beta 2 improvements and problems

Discussion and feedback on Construct 2

Post » Thu Jan 07, 2016 12:34 pm

Just letting you know that the lagspike issue is still a thing in the latest release. It seems to be less common now, and mostly happens shortly after booting. However it never truly goes away. Other than that the game runs mega smooth.

NWjs finally runs properly with the nvidia GPU again on optimus setups.

Horrible performance on my intergrated intel card though. Lagspikes very frequent and common here. v0.12 ran better.

Anyone else experiencing the lagspike issues?

Edit: @Ashley Unfortunately I can't test in chrome since I've been unable to boot Klang in chrome preview for well over a year now. Something about the download size or something.
B
27
S
9
Posts: 336
Reputation: 2,848

Post » Thu Jan 07, 2016 2:28 pm

@Tinimations

Can you maybe strip some layouts out before export, to test with chrome?
Would be really interesting to see if this is indeed a NW-problem or more like.. project rot.
B
70
S
27
G
32
Posts: 476
Reputation: 19,573

Post » Sat Jan 09, 2016 8:18 pm

I updated C2 and node-webkit today and suddenly I have new problems:

- C2 "run layout" preview not working when choosing Nw.js preview browser.
- Construct 2 does not shut nw.exe properly when closing the program (steam version - I need to open the task manager to shut nw.exe down).
- Still have random bad performance/stuttering/lags with low framerate (around 45 fps). This problem appears randomly, because my game runs at 60 fps every time.
B
10
S
2
Posts: 19
Reputation: 698

Post » Sat Jan 09, 2016 9:21 pm

@bkcove having the same issues but only with my project. If I create a new project I don't have issues with NW.js
Also, when testing in Chrome I dont have lag anymore. But Ive been optimizing.
B
43
S
12
G
14
Posts: 488
Reputation: 10,570

Post » Thu Jan 14, 2016 12:20 am

@Eisenhans

Been trying around a bit. Lagspikes didn't seem to happen to my mega small gamejam game, but it's not saying much. For all I know I just had to play for 10 times longer for it to kick in. Therefore I figured there was no point in stripping Klang down, since a potential lack of lagspike in chrome wouldn't mean anything.

I tried to just run around back and forth in the smallest layout in the game, where practically nothing happens. There didn't seem to be no lagspikes after a while. Also as these lagspikes was never really an issue in 12 (but I remember having similar issues earlier in development), I'm pretty certain it isn't project rot. This is a chrome/NW problem. The problem persists in Beta 3, and I'm becoming worried that this thing won't be fixed...
B
27
S
9
Posts: 336
Reputation: 2,848

Post » Thu Jan 14, 2016 12:33 pm

Intel GPUs are really weak, I don't know if they will run anything well :P

If you have any issues I'd encourage you to post to the Bugs forum following all the guidelines. It would be strange if the game starts up in NW.js but not Chrome - they're both based on the same Chromium browser engine!
Scirra Founder
B
383
S
224
G
86
Posts: 24,117
Reputation: 190,432

Post » Thu Jan 14, 2016 12:51 pm

@Ashley The game starts up in chrome if I export it to a website, it's just the preview that's instantly gets a red loading bar. It still attempts to load the assets, but stops at 23 %. I met this wall a long time ago. If not for Firefox I would have switched engine back then. I haven't had the time yet to export the game out and upload it to the web yet. Maybe I should test that.
B
27
S
9
Posts: 336
Reputation: 2,848

Post » Thu Jan 14, 2016 12:56 pm

Ashley wrote:Intel GPUs are really weak, I don't know if they will run anything well :P


They run my game really well. Even older ones from many years ago.

With the 0.13 alpha 7, where I found heaps better performance on Intel GPU compared to 0.10.5 and 0.12!

And they are the majority of the market, especially notebooks and low-end PCs that are supposed to handle 2D games well.
B
68
S
24
G
19
Posts: 1,755
Reputation: 17,553

Post » Thu Jan 14, 2016 10:33 pm

@Ashley @Eisenhans So I exported the game to an HTML document and "downloaded" it to chrome. It ran perfect, not a single lagspike, or stutter, even after a long session. I have my proof, it's NW.js!

Only issue was that videos wasn't playing at all in the chrome browser. Might be due to them not loading in properly?

Edit: Also played it in Firefox. Horrendous performance. Constant lagspikes. Preview runs way better here.
B
27
S
9
Posts: 336
Reputation: 2,848

Post » Thu Jan 14, 2016 10:46 pm

Well, if I ever saw good and bad news rolled into one, this is it.
Good that your project is fine after all and boo to NW.js.
B
70
S
27
G
32
Posts: 476
Reputation: 19,573

Next

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 6 guests