Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Diagnose this hitch in [PC game]. Reproduction: [route and action]. Hardware and build: [details]. Graphics and display settings: [details]. The hitch occurs [on first use, periodically, or under load].
Measure frame-time behavior and correlate the pause with simulation, rendering, asset loading, shader preparation, or another observed operation. Preserve cold-cache or first-use conditions when they matter. Use a small discriminating experiment to test the strongest explanation.
Apply a focused fix, replay the same scenario, and check that visual readability and game rules remain correct. Report the evidence, before-and-after measurements, configuration tested, and any uncertainty that affects the conclusion.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Godot — profiling frame, script, physics, and audio time
- Godot — reducing shader pipeline compilation stutter
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original diagnostic template with supported frame-time and shader/pipeline preparation concepts. No hitch cause or improvement is asserted before measurements.