Preview mode on 60 FPS but Debug mode on 0 FPS

Not favoritedFavorited Favorited 0 favourites
  • 5 posts
From the Asset Store
Set of 60 cursors. All icons are of a high quality. A good choice for RPG game.
  • I’m having a problem in Construct 3 where I simply can’t view the debug properly. Every time I open debug in new projects, it shows 0 FPS. However, if I open my older project, the FPS appears normal in debug mode.

    This issue only happens in debug mode, the preview runs normally. I’ve already tried clearing cookies, restarting my computer, testing on three different browsers, and even using another PC with Windows 11 (mine is Windows 10), but the problem still happens the same way.

    Scirra’s help templates, like “Turret Defense,” run normally at 60 FPS in debug mode. I thought about adding my assets to that template to test it, but as soon as I add my assets and code, the debug drops to 0 FPS.

    I really don’t know what else to do. Could someone help me?

    Tagged:

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I figured it out. Apparently the debug stays at 0 FPS if it doesn’t detect anything moving, like animations, sines, etc. My project for now is just a few squares, and when I press 1 on the keyboard the characters start moving, so that was it.

  • Well now I have a new problem. I added three little squares to move using sine while there’s nothing too heavy going on, to keep it at 60 FPS, and that worked. But in my current game, every time I press 1 it respawns an enemy that already starts moving in a direction. In preview, this enemy respawns normally, but in debug, at the moment it respawns it moves a little and then the debug freezes, dropping back to 0 FPS. Could someone help me?

  • ... Could someone help me?

    If you provide the “*.c3p” file where the problem occurs, we'll have a chance to identify the issue.

  • I'd add that if nothing on-screen changes, Construct does not redraw the screen (as to do so is a waste of resources). This is why the frames per second (FPS) can drop to 0 when nothing much is happening. However the ticks per second (TPS) should still be running at the display refresh rate (typically 60). Some example measurements might be:

    • FPS 60, TPS 60: normal rendering with visual changes every frame
    • FPS 0, TPS 60: engine is still running but no visual changes
    • FPS 0, TPS 0: engine has stopped running entirely (usually due to being suspended)
Jump to:
Active Users
There are 0 visitors browsing this topic (0 users and 0 guests)