Some scenes take ages to load, but is it the scene or just one bad moment

One slow measurement can point you at the wrong scene and waste a day of fixing. This entry splits the scenes that are always slow from those that stumbled once, using a typical value rather than an average, and tells your AI where to look.

Why this works

One bad moment can come from the device or the connection and says nothing about the scene. Taking the typical value of several tries ignores a single spike, so a scene that is always slow stands apart from one that stumbled once.

When not to use it

Do not trust it when slowness depends on what the player did before, such as a long play that fills memory. Short fresh tests look fine there. Measure after a realistic long session instead.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 22 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 "Some scenes take ages to load, but is it the scene or just one bad moment" (read_entry slow-scene-or-one-time-hiccup) 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