Mega Input delay bug on mac OS (NODE WEBKIT)

Bugs will be moved here once resolved.

Post » Tue Jul 01, 2014 4:39 pm

Problem Description

Export the project of your choice (a demo project for instance) with node webkit.
Open it on mac os. Enjoy the mega lag.

PS: i've used BatChMod (chmod command automation) because i had permissions problems. But i'm sure it's not a problem of Chmod command.

Attach a Capx
Just export what you want that uses player inputs.

Description of Capx
Player input is delayed about 3-4 seconds.

Steps to Reproduce Bug
    Said in the description

Observed Result
Lag when you input something.

Expected Result
No lag when you input something.

Affected Browsers
    It's node webkit on mac os.

Operating System and Service Pack
Mac Os 10.9.3

Construct 2 Version ID
Beta 174
B
13
S
4
G
1
Posts: 241
Reputation: 1,724

Post » Fri Jul 04, 2014 6:44 am

i have no lag on export to nodewebkit for OSX. keyboard, mouse and gamepad entry operates as expected.
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 » Mon Jul 07, 2014 2:50 pm

Closing as most likely not a C2 bug, there must be something in the OS or node-webkit causing the issue.
Scirra Founder
B
399
S
236
G
89
Posts: 24,543
Reputation: 195,430

Post » Wed Jul 23, 2014 5:03 pm

I've noticed this same issue when exporting to nodewebkit (it's fine when running game from browser). Mac OS X 10.9.4
But yeah... may be just a nodewebkit issue that we'll have to wait for a webkit update or something?
B
63
S
12
G
6
Posts: 456
Reputation: 8,985

Post » Fri Aug 01, 2014 7:45 pm

I am now getting this after updating to 175
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 » Sat Aug 02, 2014 7:44 pm

@vagaev

Was nervous about continuing dev after downgrading the project file itself -- was worried id introduce other bugs inherently by forcing the downgrade.

Instead I tried just replacing the exporters/html/nodewebkit folder in 175 with the one from 173 and it works without issue now. So im back to using 175 on my 175 project, but the nodewebkit exporter from 173 and it's all good.

Also confirms the issue lies within the nodewebkit exporter and not construct 2 itself, if that helps any..
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