Agni's Forum Posts

  • Yes, you double click the exe and nothing shows up for some time (the task instantly appears in task manager at around 26MB and uses around 12% of my CPU and when the window shows up, a second process starts with the same name that is around 350MB and all the CPU time goes to 0% on the smallerprocess and is hovering at 1% for the larger process).

    It used to be a few seconds long and has progressively gotten slower as the game has grown.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hmm okay, already using a loader layout (I thought the percentages were going up almost instantly from 0% to 100% since it's loading locally but maybe that's what's causing the slow window appearance). Thanks a lot for looking into this Ashley!

  • Wondering what is actually happening between when you double click the .exe file generated by Node Webkit export and when the window shows up on screen. This feels like it is taking longer and longer as my game grows (30+ seconds where the app is active on task manager before the window shows up). I'm wondering if there's anyway for me to optimize this! Thanks in advance for any help.

  • I wanted to second that I'm also having this error. AJAX requests don't appear to fire on layout restart. Saving it to another file as a workaround for now until fixed (also still on r141 given all the bugs/performance issues with latest releases, possible it was fixed in a later release).

  • Happy birthday! :D

  • Yep same problem, exported exe does not run at all for me. I see it in task manager but at a fraction of the normal memory usage.

    With preview mode, still having issues even after the 'OR' block fix as well (certain instance variables reading as zero for some reason when its worked fine before). Don't have time to troubleshoot more at the moment, reverting to R141 which has been most stable for me.

  • Bump to the top with another performance question.. hard for me to test these things personally because my computers still function okay with the game.

    Has anyone else seen a spike in RAM usage with the new Construct version when exporting to node webkit?

    Also for collision detection, does checking distance before the collision detection help or does that add even more computational strain? (e.g., 50 bullets flying around.. turn off collision for things that are: distance(bullet.x,bullet.y,player.x,player.y)>200?

  • Sent you a PM but this appears to be a reasonable fix:

    scirra.com/forum/plugincb-hash-md5-sha1-and-sha256_topic43824.html

  • andreyin Wondering if you have found anything similar for webstorage protection? Just enough so you can't edit with notepad++ would be nice since that seems a bit silly. Searching through forums I saw some crc32 stuff with Construct Classic but not sure how to use that with C2.

  • I went into file options and checked 'compress files' and it worked after that! With default settings it extracted the file as .enigma1 (which I could then extract again to see everything)

  • Haha, okay so this doesn't seem to work very well. I can just rename the boxed exe file to zip and then unzip it to see all the files.

  • Wow, thank so much for the quick response. This looks pretty cool, will test. :)

  • Curious about this as well - noticed I can see everything including base txt files that are being AJAX'd into the game simply by unzipping the package.nw file. If I recall, previous versions had the package grouped into the exe which I assume made it harder to just unzip? Is there a way to enable this?

  • Did anyone else see their memory usage bloat with node webkit's exe after moving from r141 to r142? I've reverted to a previous build since the memory usage increase was persistent and significant across the few computers I tested on.

  • Ashley Yikes.. so going from v141 to v142 the node webkit .exe takes roughly double the amount of memory in task manager (from 200mb to 400mb). Do you know why that might be? I don't think anything else changed although now I've saved over my file like an idiot and am not sure if I can revert to the previous Construct version..

    Debugger memory usage appears to be the same (50-60mb in images). The new profiler tool is really awesome btw! Wish I could see what draw calls are occuring because it takes up nearly 20% CPU when nothing on the screen is moving.. that seems wrong right? I have bad code that is telling the game to redraw something it doesn't need to draw?

    Thanks so much for your help. ^^