There is a freeze intermittently after exported.

0 favourites
  • 9 posts
  • Problem Description

    My game will have a freeze (lag? with no response? I am so sorry I don't know how to describe it in English) intermittently after exported.

    I exported my project to Node-webkit and then I find there are some unknown freezes ranging from 1s to 4s. I have sent my game to my friends, but nothing changed. However, when I test it in preview(Node-webkit and chrome), everything is OK.

    I try to exported space blaster to see if there is something wrong in C2 itself, but it goes all right.

    I can't make sure why it has a freeze. I even think that the freeze appears randomly.

    I add displays of CPU usage and FPS. When freezing, both of these two data will also shut down. So, I don't think there are some mistakes during events, maybe.

    I used Fraps record a video









    Attach a Capx ... sp=sharing

    it's my capx ... sp=sharing

    it's the exported game

    Description of Capx

    This is my full game project

    But it's wroted by chinese and japanese,maybe it will hard to understand

    Steps to Reproduce Bug

    • Step 1 Please just play it, and then the freeze will appear, which I think is random.

    Observed Result

    Freeze intermittently.

    I took 30mins to play my game respectively in preview and Node_Webkit. Nothing happened in preview but 14 times freeze in Node_Webkit exported.

    Expected Result

    I hope that freeze won't happen.

    Affected Browsers

      It goes well in the preview of chrome

    Operating System and Service Pack

    windows8.1 update1 x64

    Construct 2 Version ID


  • I tested in preview (using Node-Webkit) and the exported game, and the game didn't freeze in both...

    On exported, I played until I died 3 times and the game was running smoothly...

    My PC configuration:

    • OS: Windows 8 x64
    • Processor: Intel Core i7-3770 3.4GHz
    • RAM: 8 gb
    • Video: AMD Radeon HD 7450

    I couldn't see your code, I don't have chinese/japanese installed on my PC, sorry... ¬¬"

  • There was another thread discussing this recently (can't seem to find it right now). In short it's probably something caused by node-webkit, since it runs smoothly in Chrome and node-webkit is just a standalone version of Chromium with node.js attached. Node-webkit is a few versions behind Chrome now and hasn't been updated for a while - hopefully the next version will be smoother.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • This might help works

    i will be concern about your post persistently

  • Does this still happen in the latest beta r175? It has been updated to a new version of node-webkit.

  • Does this still happen in the latest beta r175? It has been updated to a new version of node-webkit.

    the R175 version of node-webkit lag or freeze more serious while request fullscreen. look forward to solve it.

  • Ashley There is no freeze through r175,but i also find that it lagged in fullscreen. It seems that the newest node-webkit costs more to the video card, so that FPS is low

  • If there is no freeze in r175, then closing as fixed. If the framerate is lower then please check blacklisting (in chrome://gpu) to verify that is not the cause, and post a new issue to the node-webkit developers if you still think there is a problem.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)