Danwood's Forum Posts

  • In my game ctrl is used to sneak and W to walk forward. You can guess the result

  • Problem Description

    Pressing Ctrl+W closes the game.

    Attach a Capx

    No need

    Description of Capx

    No need

    Steps to Reproduce Bug

    Press Ctrl+W

    Observed Result

    Game closes

    Expected Result

    Game shouldn't close

    Affected Browsers

    • NW.js v0.13.0 alpha 7: (YES) Operating System and Service Pack Windows 7 Ultimate SP1 Construct 2 Version ID 218

  • Great stuff Ashley

    Our game, which is a massive open world, runs better with NW 0.13, and alpha7 is a pinnacle.

  • I don't know about AJAX as i dont use it, but 0.13 is a performance improvements for me, alpha 5 & 6 still had issue, but 7 so far is good. If you still have performance problem the cause may be difficult to isolate, maybe it's your system? Do you have a laptop with integrated graphics? do yo uuse your graphics card for nw.exe?

  • — which version of NW were you using prior of 0.13 alpha?

  • —

    Great work there! Good choice not going for Early Access, as most players who check the game in early stage usually do not come back even if the final version is much better. My game is still far from final version and I'm now in a strange situation where I'm limiting the marketing as much as possible to gather players when the full version is available

    But nevertheless, having a community during the alpha helped me so much with feedback, bug hunting, ideas and critique!

    Guess you had a group of testers during the alpha phase, didn't you? It is really mandatory!

    Congratulation for the imminent release, fingers crossed!

  • You're probably using NW 0.12 which stil has the awful jank issues. I recommend updating to r218 beta, download NW 0.13 alpha 7 http://dl.nwjs.io/live-build/12-01-2015 ... 3.0-alpha7 ( last two files, respectively for 32 and 64) and place in the respective 32/64 folders on the NW.js installation for C2 you have in your program files.

    Newer NW.js fixes the jank for me and reduces CPU usage by ~20%. My game is massively large and it's running well on my mid/low end system. Some users still have issues though, as html5/C2 isn't the perfect combo for large games, but nowadays systems should handle them anyway, especially considering Html5 is an evolving technology.

  • Did it fix by removing all the build in the depot and starting fresh?

    Yes, lol

  • Shouldn't you wait til the next stable update of C2 to update your game?

    It's not a C2 problem, and apparently not even NW. It's an issue with my Steam repository, and i thing i might have fixed it with my last attempt.

  • No way, can't find an option for it, maybe i should try removing all the current builds from the depot and try again?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I'll try that! Hope not to mess anything :S

  • I got a serious issue here with Steam:

    Tonight i needed to update the game. The game runs on the newer NW.js 0.13 a7, which has a file "nw.dll", which is essential to run the game. It is a fairly big file, 66mb for the 32bit version, 87 for the 64bit one.

    The problem is, whenever i upload the game on Steam, it doesn't show on the builds list, preventing me from updating the branch. I've tested and figured out is the nw.dll file that causes the issue, as if i remove it from the files list, it uploads everything normally.

    I can't even revert back to the previous version of NW.js, as the new game update relies on the new NW.js.

    Is there anything i can do? I'm missing a deadline here and dont want to disappoint the users!

    UPDATE: fixed by removing all old builds before uploading the new one, as it makes a checksum and the old files probably corrupted it.

  • With NW improved on memory management and working vsync, C2 is good even for bigger games. I just hope the situation remains good and improves. We do not want major chromium bugs to neuter C2 for months on end ever again. That's the biggest risk with C2, hoping that Google doesn't accidentally break your games.

    +1

    This update is a real blessing for us Silver

  • Apparently, NW 0.13 alpha 7 fixed the issue for me

    http://dl.nwjs.io/live-build/11-26-2015 ... .0-alpha7/

  • Danwood

    Make custom ones. Never have those weird issues again.

    -_______________-