<3 anytime

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

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

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

thanks a lot - doesnt fix the issue, unfort. but this is good info.. thank you again.

maybe a corrupted sound? try re-importing them a small batch at a time (4-5 at a time) and keep exporting to see if Node-Webkit breaks in a certain batch, then you can narrow down the culprit.

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

lol newt

can you pass your capx?

I am receiving feedback on this as well. I can run game in browser overnight no prob. Running it as nodewebkit build will lead to an eventual crash. Its frustrating because i cant run profiler tools / debugger on nodewebkit export which is the only place the problem is happening on. Looking at debugger in the browser/preview doesnt help because it never crashes there.

Yo, lemo - can you tell me how you did that? I want to try and see if it fixes another issue im having with my nodewebkit build not working properly on OSX..

Thanks man.

I am now getting this after updating to 175