[Solved] Timer slowing down

[TrinityNeo]

I have used timers so many times in my game, but never faced this issue. It runs with perfect speed in the start but continue to slow down as the time passes.

I am not sure if this issue has anything to do with TimeFormatter extension. If yes, can anyone suggest how to show time in HH:MM:SS format and save/load it in global variables>

[Bubble]

Hi TrinityNeo, there might be something in your game causing it to use a lot of resources which will affect how well the timer is counting. When I had a similar problem this advice was helpful.

Timers are affected by processor speed?

Effects can take a toll too. You can also run it through the debugger, and use the analyser to get an idea of where most of the processing is taking place. The analyser will also break it down to event groups, so using a few of these helps narrow it down when indentifying the bottle necks.

Also, some good info here

Timers not counting at the same speed on different systems

To clarify, Timers are just timedelta between frames added to a single number (the timer name). They have always been impacted by game slowdown below minimum framerate, so if your game drops below your minimum framerate on one system (mobile) but doesn’t on another (pc), the system that didn’t drop framerate will have the more accurate timer (and therefore increase “faster” than the other). I don’t believe they should be impacted if you don’t drop below the minimum framerate though.

[TrinityNeo]

Thanks for the inputs. I checked the debugger, but did not found any issues that might be impacting the performance of the game. I noticed one issue due to missing font which I fixed, but there is no significant improvement in the timer performance.

In addition to the above, I also.

1. Converted few group of events into functions. Most of them are non-repeatable events and therefore I don’t know it will impact the performance.
2. Tested the application in both preview and build. The timer issue remains same in both desktop app and mobile app.

Are there more accurate ways to replace timer to remain consistent across different systems?

[Bubble]

Here is some more info from the second link above. I haven’t tried it, but it might be helpful to you.

Timers not counting at the same speed on different systems

The only thing I can think of to have it be more accurate would be using Time() expressions with a datestamp instead, since that’ll use real-world time. You could compare a “Starter time” at the beginning of the scene (Storing Time(“timestamp”) as soon as the scene starts as a scene variable) against “Current time” (Time(“timestamp”)) to get a real world timer, I suppose?

[TrinityNeo]

Thank you! That was indeed useful. To be on the safer side, I switched to Time() expression with datestamp instead of scene timer.