Previewing or exporting to nw.js makes the game run at 30fps

0 favourites
  • 8 posts
From the Asset Store
Full game Construct 2 and Construct 3 to post on Google Play
  • Why is the game running at 30 fps when i use nw.js? It doesn't seem to be lagging or anything. It just seems to be capped at 30 fps. It's a simple game so far, so there's no reason for it to be lagging or anything. When i preview in firefox or chrome, the game runs at 60 fps perfectly. Also I think it's a new problem, since I only noticed it because the scrolling has become much less smooth. I remember when I used to preview in nw.js all the time, the scrolling would be smooth.

  • What version of C2 and NWjs are you using?

    Have you got an example we can test?

    I have always found that previewing using NWjs is generally better than browser previews, with a rock steady 60 FPS.

  • nw.js: 0-12-0

    construct 2: 204.2

    What would I need to post from the nw.js export to show you an example?

    Also, again, I'm 90% sure this is a new problem. I tried reinstalling the nw.js version that i have, but that did nothing. I'm gonna try updating it.

    Edit: I think I had the latest version posted on scirra, so reinstalling it again did nothing. Also, it's not lag or anything. It just seems like it's capped at 30.

  • I've tried other games and templates and the problem persists in those too ( shoulda tried from the beginning I know..). So the problem is definitely in nw.js or construct 2.

  • First thing I would do is update to the latest stable release - r212.2.

    The version you are using is a bit long in the tooth, and bugs could have been fixed since then.

    As an example, I loaded the Space Blaster demo in C2, set preview to NWjs, added a text object to the UI layer and set it to display FPS, and it showed a steady 60 FPS .

  • I've uninstalled then reinstalled the updated version 212.2. Still the same.

    I feel like there's some setting somewhere somehow that's changed. It's been a week or two since I last worked on the game, and I think it was working fine then.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • What GPU?

    When where drivers for GPU updated?

    Have you somehow configured the GPU to lock at 30 FPS, e.g. in Nvidia Control Panel, you have an option to set VSync to Adaptive - half refresh rate, which would be 30 FPS for most users.

  • You are right! Thank you! I figured out what happened now. I have my TV connected to my computer also, but it was disabled in the display settings. Then I wanted to watch something on the TV so I duplicated the display on both the monitor and TV, which forced the TV's settings on Windows, cause I remember I had to change the resolution back when I turned off the TV. It must've also forced the TV's 30 hertz setting on Windows too. It's still kind of weird that when i previewed the game on firefox and chrome, both the "fps" variable and the debugger showed that the fps is 60. I just disabled the TV in the Windows resolution control panel. I didn't change the settings in the NVIDIA control panel, so maybe nw.js was just following the TV's refresh rate, but the browsers weren't. Anyway, thanks a lot.

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