[r160.2] No effects on NodeWebkit

Bugs will be moved here once resolved.

Post » Thu Feb 06, 2014 5:33 pm

Link to .capx file (required! If link is blocked remove the http and www parts):
https://www.dropbox.com/s/4606n91a7t5ebqt/nodewebkitnoeffects.capx

Steps to reproduce:
1. Put any sprite on layout
2. Put effects on it (I've put tint, swirl, sphere at least)
3. Run with Preview browser: Node-Webkit

Observed result:
No effects were applied.

Expected result:
Effects to be applied. In 160 it was working.
WebGL is on, on project settings.

Browsers affected:
Chrome: no
Firefox: no
Node-Webkit: yes

Operating system & service pack:
Windows 7 Ultimate

Construct 2 version:
[r160.2]wguilhermino2014-02-06 17:34:46
B
13
S
3
Posts: 9
Reputation: 1,083

Post » Thu Feb 06, 2014 5:43 pm

Just tested on my PC, works fine here.
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,709

Post » Thu Feb 06, 2014 6:13 pm

I've tried the exported nw on OSX Mountain Lion, worked.
Also, I've removed 160.2, installed 160 again, copied node webkit folder from exporters/html5, installed 160.2 again and replaced the newer webkit folder with the older, then worked. Installed 160.2 again to update node webkit, not working again. No clue of what cause this here.
B
13
S
3
Posts: 9
Reputation: 1,083

Post » Thu Feb 06, 2014 6:23 pm

Can't reproduce, works here - my best guess is you're just getting the canvas2d renderer instead of WebGL, perhaps because Chromium 32 has a newer driver blacklist. Check your graphics card drivers are up to date.
Scirra Founder
B
403
S
238
G
89
Posts: 24,654
Reputation: 196,145

Post » Thu Feb 06, 2014 6:45 pm

How do you get to about:flags in node webkit?
Image ImageImage
B
172
S
50
G
183
Posts: 8,443
Reputation: 115,605

Post » Sat May 24, 2014 5:37 pm

I'm having the exact same issue w/ a new machine I've put together specifically to demo my C2 game. WebGL works fine everywhere outside of node-webkit. The card is an EVGA-branded nVidia GTX 750 Ti, and performs quite well outside of nw preview/export.

I'm sure it's not really a bug with C2, but some kind of workaround would be great.

*EDIT: Dropping d3dcompiler_43.dll into the same directory as nw.exe in the /exports folder seems to solve the issue during preview, at least temporarily.

Relevant GitHub post: http://github.com/rogerwang/node-webkit/issues/185
B
89
S
47
G
25
Posts: 535
Reputation: 21,827

Post » Tue May 27, 2014 10:45 pm

Is there some way to easily output (ie to a text object) that the game is using WebGL or not? I know it appears in the debugger - just curious if we can use that in our own debug strings for customer testing... Im having the same issue with some people reporting WebGL related issues (low FPS / no effects) on the Steam downloaded NodeWebkit version, while things work perfectly in Chrome / Firefox.
Made Cosmochoria - www.cosmochoria.com
Currently working on Slayaway Camp - www.slayawaycamp.com
B
27
S
8
G
3
Posts: 384
Reputation: 5,020

Post » Wed May 28, 2014 9:07 pm

@80bit - yes, look through the system expressions, renderer returns canvas2d or webgl. BTW please don't reply to closed bug reports, generally posts here will be ignored.
Scirra Founder
B
403
S
238
G
89
Posts: 24,654
Reputation: 196,145

Post » Wed May 28, 2014 9:21 pm

Yikes, it just came up in a search, i didnt realize where it was posted. thx
Made Cosmochoria - www.cosmochoria.com
Currently working on Slayaway Camp - www.slayawaycamp.com
B
27
S
8
G
3
Posts: 384
Reputation: 5,020


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 4 guests