Node webkit performance.

Get help using Construct 2

Post » Wed Nov 19, 2014 10:20 pm

Hi guys,

Im working on a project and I just updated to the newest Beta. When I tested in Node Webkit before the update I was getting a solid 60fps, but after the update its hovering around 30-40fps. Ive changed nothing in the game what so ever. Any idea what could be causing this?

Thanks, Adam
B
36
S
5
Posts: 156
Reputation: 3,310

Post » Thu Nov 20, 2014 7:43 pm

Still Cannot Figure this out. My drivers are all up to date.. I have the latest Node Webkit... Wish I knew what the problem is.
B
36
S
5
Posts: 156
Reputation: 3,310

Post » Thu Nov 20, 2014 10:08 pm

Node Webkit might have caused it, actually. They have a nasty habit of blacklisting older hardware for WebGL so they don't have to bother with legacy support. Try making a text object and set it's text to "renderer" every tick. (Without the quotes, it's a system expression.) Or you could run it in debug mode and check the renderer from there, but that won't work if you want to test the exported version too.
If it says Canvas2D instead of WebGL it's probably Node Webkit's blacklist. C2 has a way of ignoring the blacklist that might be broken in the beta so you may need to wait for a full release.
B
35
S
9
G
4
Posts: 201
Reputation: 5,170

Post » Thu Nov 20, 2014 10:56 pm

Revert back to r187 if you can - the newer version of nw is broken (because it's based on chrome 38).
A big fan of JavaScript.
B
74
S
20
G
71
Posts: 2,228
Reputation: 44,888

Post » Fri Nov 21, 2014 12:17 am

Ahr Ech wrote:Node Webkit might have caused it, actually. They have a nasty habit of blacklisting older hardware for WebGL so they don't have to bother with legacy support. Try making a text object and set it's text to "renderer" every tick. (Without the quotes, it's a system expression.) Or you could run it in debug mode and check the renderer from there, but that won't work if you want to test the exported version too.
If it says Canvas2D instead of WebGL it's probably Node Webkit's blacklist. C2 has a way of ignoring the blacklist that might be broken in the beta so you may need to wait for a full release.


Hey, thanks. I tried that, but it says webgl so I think its working. But thanks again.
B
36
S
5
Posts: 156
Reputation: 3,310

Post » Fri Nov 21, 2014 12:18 am

Colludium wrote:Revert back to r187 if you can - the newer version of nw is broken (because it's based on chrome 38).


Yeah, I guess Im going to try that. Hopefully I can open the project haha. Thanks for the help!
B
36
S
5
Posts: 156
Reputation: 3,310

Post » Fri Nov 21, 2014 12:51 am

Remember that nodewebkit is seperate now so you just need to get the old NW installer. Someone posted it in the juttering thread in general.
B
149
S
75
G
20
Posts: 1,791
Reputation: 22,695

Post » Fri Nov 21, 2014 1:40 am

You might find this useful as well if you revert to r187. Until Ashley updates the nw loader, you can download a copy of the old version in this thread at the bottom of the page.
A big fan of JavaScript.
B
74
S
20
G
71
Posts: 2,228
Reputation: 44,888

Post » Fri Nov 21, 2014 1:48 am

alspal wrote:Remember that nodewebkit is seperate now so you just need to get the old NW installer. Someone posted it in the juttering thread in general.


Yup! That was the issue, I guess the new version runs poorly. Thanks so much for the help!
B
36
S
5
Posts: 156
Reputation: 3,310

Post » Fri Nov 21, 2014 1:50 am

Colludium wrote:You might find this useful as well if you revert to r187. Until Ashley updates the nw loader, you can download a copy of the old version in this thread at the bottom of the page.


Thanks man! I just went back to 186.2 and it works perfectly again! I might go ahead and move up to 179 and try the old version to see if that works too. Thanks a ton!
B
36
S
5
Posts: 156
Reputation: 3,310

Next

Return to How do I....?

Who is online

Users browsing this forum: No registered users and 53 guests