Input Delay on OSX Build

Bugs will be moved here once resolved.

Post » Fri Aug 01, 2014 11:44 pm

Problem Description
Building an OSX node-webkit build of *any* capx game, including the demos, results in a game where ALL input is delayed by a number of seconds.

Attach a Capx
Use any of the included demo/tutorial games that require input (eg. Platformer)

Description of Capx
Any input-driven capx will work...

Steps to Reproduce Bug
  • Step 1: Build Nodewebkit Export of game.
  • Step 2: Bring game to OSX
  • Step 3: Run game & try to control

Observed Result
Input lags massively.

Expected Result
Input does not lag at all.

Affected Browsers
  • Chrome: (NO)
  • FireFox: (NO)
  • Internet Explorer: (NO)

Only Node-Webkit and only on OSX. Windows EXE file is fine.

Operating System and Service Pack
Windows 7 to build, OSX Mavericks to run.

Construct 2 Version ID
Beta 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 6:30 pm

Downgraded project to 173 and the issue is not present when i export, so this is definitely something that was introduced in 174 (i know someone else posted about it re: 174).
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:42 pm

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..

Thanks
nate
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 Aug 04, 2014 9:51 pm

Thanks Nate.
I have the same issue and solved it with your trick.
Big bug though...
B
17
S
1
Posts: 10
Reputation: 695

Post » Tue Aug 05, 2014 4:14 pm

There is not much we can do about this, nothing in C2's engine has anything to do with input delays - it would happen at the browser or OS level. The next build updates to node-webkit 0.10.1 so hopefully that fixes it, but if not, please report the issue to the node-webkit developers.
Scirra Founder
B
395
S
233
G
88
Posts: 24,376
Reputation: 193,842

Post » Tue Aug 05, 2014 4:23 pm

@Ashley, what is the version of node-webkit being used for the 173 release vs the version used for 174/175?

Would you revert back to the older version for the stable build if it doesn't get fixed? You would technically not be able to say that OSX is supported any more if the stable build has a broken version of node-webkit that exports useless OSX builds.

The workaround to copy out the 'old' node-webkit folder works but if its broken beyond use, why even include it to begin with?
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 » Tue Aug 05, 2014 4:26 pm

r174-5 ship node-webkit 0.10.0-rc1, and the next build will ship node-webkit 0.10.1. Hopefully that fixes it. If not contact the node-webkit developers - going back versions is not a long term practical solution since Chrome is always updating and node-webkit is moving forwards with it.
Scirra Founder
B
395
S
233
G
88
Posts: 24,376
Reputation: 193,842

Post » Tue Aug 05, 2014 4:32 pm

@Ashley, Sounds good, thanks. Just trying to save headaches of other peeps building mac versions who may not have found this thread. Ill keep you posted (on this thread?) once i test with the next build.
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 Aug 06, 2014 5:30 pm

@Ashley Unfortunately 176 with node-webkit 0.10.1 doesnt fix the issue. Reverting back to the nwk distributed in 173 is still a workaround (can you confirm if i should not be doing this though -- will other errors occur?)

Also, could you please give me quick guidance on how (where) to report a bug to node-webkit 0.10.1? Thank you so much.
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 Aug 06, 2014 5:36 pm

@Ashley, also - what was the version of node-webkit in 173, so I can properly report a bug. I think i found the right place to report on github.
Made Cosmochoria - www.cosmochoria.com
Currently working on Slayaway Camp - www.slayawaycamp.com
B
27
S
8
G
3
Posts: 384
Reputation: 5,020

Next

Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 5 guests