Find the short freezes in a play session and say in which place they happen

Players say the game stutters, but an average speed hides it: most moments run fine and a few freeze for a blink. This entry shows how to find those freezes in a list of frame times, group neighbouring slow frames, and report how much time each one cost and where it happened.

Why this works

Players feel the worst moments, not the average. A typical speed hides short freezes, so measure against what is normal for this game and look for runs of frames far above it, since a single blink and a long stall feel very different.

When not to use it

If the whole game is slow all the time, there is no freeze to find, and the fix is to make the common case lighter. Also measure on the weakest device you care about, because a fast computer will not show these problems.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 37 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Find the short freezes in a play session and say in which place they happen" (read_entry frame-hitch-finder-by-scene) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP