I see that Node Webkit is still giving trouble. I plan to release my game February next year.
I sincerely hope that this problem is fully taken care of before then.
Development of my game is going well - except for Node Webkit - and since I plan to make a Windows PC game for STEAM, Node WebKit NEEDS to work.
I shudder to think that all these months of development would be in vain - just because of Node Webkit
i feel your pain i have been developing a game for 1 year.... everything was going great...until this came along...
i was planing on starting my indeigogo and now i need to wait :/
my future depens on this game ... :/ please we need this fixed.
I think the breakdown people are having (myself included) is that we don't know how to run a URL in what sounds like a standalone version of Node-WebKit... It sounds like that's what *you* need out of the process (is to test in NodeWebkit as a standalone URL / HtMl5 game uploaded to a server.. And again testing in Chrome 35.. Is it possible to direct us to or provide instructions on how we would run our game in Node-WebKit as a URL?
For other C2ers: this is what we need to help rogerwang:
1) export your game to HTML5 build
2) upload said game to your server / Dropbox etc
3) run the game in Nodewebkit as per Rogers instructions (I'll update this post if I can compile from external sources)
4) does game freeze when running in Nodewebkit?
5) does it run well in chrome 35 (link for chrome 35 above)?
If it breaks it Nodewebkit but runs well in chrome 35 report back here with the URL of your game and roger can look into it.
Thanks guys.. Roger if you can give me explanation on running in Nodewebkit as per above ill do my best to help.
Export for html5 , upload to server | dropbox
run C:\Program Files\Construct 2\exporters\html5\node-webkit\win32\nw.exe
Go to the url in address bar
tx dude! Noncentz705
You can download the latest Node-WebKit from here:
Just scroll down to "Downloads" and download v0.10.3 for your platform (Windows, Mac OS etc). Unzip and run the program, and paste the following URL in the address bar:
Watch the slider for some minutes to see if a freeze occurs (give it some time, maybe a few refreshes). I tried again with the latest version for Windows. On first try I waited 2 minutes then got a 5+ second freeze. Can someone else try the same thing and post the result?
In Chrome v37 or preview Node-WebKit from within Construct 2 I get no freezes.
I haven't managed to find Chrome 35 unfortunately. The link you posted does not seem to work any longer I'm afraid (it just redirects to the official download page for the latest Chrome version)
i tried installing chrome 35, but i didn't work, how im suposed to do it?? i need to uninstall the chrome im using now first and then install 35 version??
i will do my best to give roger some data.
please people, lets get this fixed.
SirSpunky i runned the test using your instructions.
and it frozed after 1 minute for 10 seconds and after 1 minute more it froze again for 2 seconds...
rogerwang is this what you were asking for roger?
This is frustrating to admit, but after hours of testing myself i dont seem to have an issue.. yet testers have expressed that they HAVE seen the issue. Could it be hardware related? I will be trying to setup some kind of "Broken CAPX" that shows the issue so I can have the testers run it to see if it hangs for them. Or has anyone prepared a CAPX of a simple file that *definitely* freezes for them? If so, could you share?
That's interesting. Are you running Windows 8.1 as well?
I used the simple capx from Giganten. It uses a sine behaviour for movement, which causes freezing for me after some minutes (not in preview Node-WebKit but full export):
https://www.dropbox.com/sh/iyia6jc30cv3 ... .capx?dl=1
I'm still curious what difference there is between Node-WebKit previews and full exports, as there's obviously some important change that's causing the freezes to appear in the exported version only.
SirSpunky - Not having any issues in Windows 7 actually. The reports I am getting from testers are running in Windows XP.
I made a new version for diagnostic. If you hit the freeze issue. Please download this, run the executable, navigate to 'chrome://gpu' and post the result here. And also please do the same in Chrome browser and post the result if your game works well in Chrome.
Develop games in your browser. Powerful, performant & highly capable.
You can overwrite the version of node-webkit C2 uses by pasting the node-webkit files over the ones at <install path>\exporters\html5\node-webkit.
rogerwang - my best theory is since it doesn't happen in Chrome that the blocking is happening in node.js. However I can't explain why the threaded compositing option would affect it.
I tested on Mac OSX and on Windows 7 (Running in Parallels) and basically tried:
Opening the test file (http://3030.ca/freeze) in your recently provided nodewebkit 0.10.3 and right next to it, opened the same URL in chrome 36 (i cant find chrome 35 -- is that important? if so I'll look harder). Here are the results of each test:
Windows 7 64bit (via Parallels)
Chrome 36: Freeze? No -- Diagnostics http://pastebin.com/2s4PyU30
NodeWebkit 0.10.3: Freeze? Yes -- Diagnostics http://pastebin.com/yiVPuj57
Mac OSX 10.9.4
Chrome 36: Freeze? No -- Diagnostics http://pastebin.com/iDYSvZMR
NodeWebkit 0.10.3: Freeze? No -- Diagnostics http://img.80bit.com/Cursor_and_New_pro ... xi_net.png (couldnt copy paste)
Let me know if you want screenshot style ones for the other ones too - also if you need the whole thing or just a section...
Thanks for taking the time to look into this.
Here's my log from NW v0.10.3 win32 from your last post, which gives me freezes:
https://dl.dropboxusercontent.com/u/242 ... gpu_nw.htm
Here's the log from my Chrome v37 installation, where I don't get freezes:
https://dl.dropboxusercontent.com/u/242 ... chrome.htm
I'm running Windows 8.1 64-bit.