NW.js 0.13.0-alpha7 released

Discussion and feedback on Construct 2

Post » Thu Dec 10, 2015 3:13 am

v0.13.0-alpha8 released~~~
B
38
S
11
G
1
Posts: 80
Reputation: 3,350

Post » Thu Dec 10, 2015 4:37 am

bclikesyou wrote:How exactly do you know the # of assets a project has?


The only way I'm aware of is to export the game, then unzip the package.nw and check how many files there are.
B
152
S
75
G
21
Posts: 1,795
Reputation: 23,285

Post » Thu Dec 10, 2015 11:54 am

Just gonna share what I wrote in a different post here:

the new NW.js finally works with Klang, and oh boy does it work as advertised! Way smoother performance, and areas I felt needed optimizing now runs butter smooth. Don't seem to notice any lagspikes after prolonged play.

HOWEVER... I keep getting the occational 100ms (approx) lagspike consistently. I can only guess this is due to the more aggressive garbage collection? I really love the fact that the game now won't turn into a slideshow after playing for too long, but these lagspikes will ruin the player's sense of rhythm. It's crucial that I find a way around this, or that the garbage collection becomes more flexible.

I'm curious if anyone knows what's usually the biggest offenders with gathering garbage for construct games? Does continiously creating and destroying objects matter for instance? If I know what to look out for I can maybe work around it myself.

-----------------------------

Did some more testing. This time on my laptop. The results were interesting to say the least.
The first thing is that I couldn't get the game to boot choosing the nVidia GPU (630m) even with the latest driver installed. This used to work before on NW 12.

Running the game on the intergrated card worked fine though. However the loading times was greatly increased. in-game videos wouldn't play properly etc. I noticed lagspikes even where I'm 100% certain there ain't any new items loading in. When I played long enough though things started to change. When playing for long enough for the stutter to kick in on NW 12, I now experienced that everything ran smooth, way less lagspikes, and no loading issues. The videos that previously didn't play properly now worked as intended etc.
B
35
S
10
Posts: 390
Reputation: 3,278

Post » Thu Dec 10, 2015 4:20 pm

@alspal Thanks. I'll try that out.
B
45
S
13
G
3
Posts: 276
Reputation: 4,598

Post » Thu Dec 10, 2015 6:20 pm

Silverforce wrote:Great stuff.

I'm happy to report (for my game on Steam) that 0.13.0 alpha 7 is excellent. Pretty much all the issues with performance, jank, memory leak are all gone.

There's also a bonus: It's around 20-25% faster than older NW, since the recent Chromium is improved with better JS engine.

Another huge bonus: Improved WebGL compatibility with Intel GPU. We're talking a game changer here. Before, as many would know, Intel HD3000 or 4000 would lag on C2 NW games which uses some WebGL shader/effects. Now it's butter smooth.

Here's the real kicker: Even HD2000, and Intel Express Chipset 4 graphics (we're talking from 2006), runs it butter smooth. Which is crazy good.

However, not all is rosy. Here's the major fail: MAC export will not function for games with a lot of assets. The red bar loading stuck bug is still there.

As for Linux, I don't know, no experience in it to test.

ps. Looking forward to Greenworks for the new next-gen NW! Just need achievements. :p


That's great news for our game on steam and hopefully will improve peoples game as we had to turn off the shader effects to help lower end PC's.

Will have to have a play with the Mac build of our game and see if the external code we had wrote bypass the red bar of doom issue still!
B
4
S
1
Posts: 12
Reputation: 476

Post » Thu Dec 10, 2015 6:49 pm

Works great in my game as far as I have tested but the only problem I still get is old saves still wont work without renaming and moving.

I was wondering if it's staying with the new destination is there somewhere in the nw.js code I can edit to make it look in the old place and change the name of the save file?
B
12
S
4
G
1
Posts: 137
Reputation: 1,519

Post » Mon Dec 14, 2015 8:17 am

mapmerry wrote:Works great in my game as far as I have tested but the only problem I still get is old saves still wont work without renaming and moving.

I was wondering if it's staying with the new destination is there somewhere in the nw.js code I can edit to make it look in the old place and change the name of the save file?


Is there any update on this, its important if we could get a fix or if anyone has a work around. Our game is live on steam and people already have save files so we cant delete them or pick a new location.

We would like to roll out this update as soon as we can, is there any way to fix this.
B
4
S
1
Posts: 12
Reputation: 476

Previous

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 15 guests