NW.js problems

0 favourites
  • 9 posts
  • Hi,

    Well, to make it short, I've been using C2 for a while now and I love it, but one thing that seems to be recurrent is the often poor performances of NW for desktop games.

    The last two months I've been having several issues with performance or like presently , the debugger not working.

    Would there be any other solution instead of relying on NW which seems to be simply unreliable.


  • Could you specify what kind of problems? Im currently in the process of making a game with the intention of publishing as NWjs once final.

    I would be interested to know what kind of trouble you are getting if possible.

  • maybe you using bugged plugin or behavior ?

  • Actually just using platform, AJAX, and FSM. I have at times drops of frame rate. They happen fast but still happen.

    Also, right now, its impossible for me to run the debugger. Trued with a new project and had the same issue. I think NW has been giving a lot of issues for the past year or so and its often slow down the process of creating a game.

  • What version of C2 and NW.js are you using?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • the latest versions. r219 and NW.js 0.13.7 alpha

  • Is there any news on this? So far I still problems with the debugger in NW.js. Is there any other way we do not depend on NW for desktop games?

    So far, I've been slowly doing a transition to Game Maker because of issues like this.

  • NW.js is based on the same Chromium browser engine Chrome uses, so in theory should work identically. Does the Chrome browser have the same problems?

    If a feature isn't working for you, like the debugger, please file a bug report following all the guidelines so it can be investigated.

  • Ashley, thanks for your time.

    Some users already filed a completed report with the same issues I'm having with the debugger. Strangely, this does not happen if I switch to Chrome.

    But in Chrome, the debugger slows down until unplayable in just a few seconds of use.

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