Troubleshoot frame rate by reproducing one scene under fixed conditions and logging frame time, not only an average frames-per-second number. Record the game build, device, operating system, resolution, display refresh rate, graphics preset, power mode, temperature, background software, input path, and the exact scene or save point. Then compare the last good build with the first bad build.
Define the symptom precisely
A low average frame rate, periodic hitch, uneven frame pacing, input delay, and screen tearing are different symptoms. Capture a short trace and note when the problem begins: immediately, after loading assets, during effects, after thermal warm-up, or only at a particular display mode. Avoid mixing menus, gameplay, and cutscenes in one average.
Android defines frame pacing as synchronization between a game's logic and rendering loop, the operating system display subsystem, and the display hardware. Its Frame Pacing library is designed to reduce uneven presentation and repeats of late frames (Android Frame Pacing library). This means a game can feel uneven even when an average counter looks acceptable; inspect the distribution and cadence of frame times.
Build a useful change log
List engine or SDK updates, rendering-path changes, new effects, asset changes, shader compilation behavior, physics or AI changes, resolution scaling, frame caps, VSync settings, display modes, driver updates, and power-policy changes. For every row, include the commit or version, old and new setting, owner, reason, test device, and rollback.
Microsoft's Frame Pacing sample demonstrates that CPU work, GPU work, swap-chain buffers, and frame scheduling interact to affect frame rate, latency, and presentation margin (Microsoft Frame Pacing sample). Use a profiler to decide which boundary is late instead of assuming every slowdown is a graphics problem.
Isolate one bottleneck
Repeat the same camera path or scripted action. Lower resolution without changing other settings: a large improvement points toward GPU pressure, while little change suggests checking CPU work, synchronization, asset streaming, or an imposed cap. Disable one newly added effect, system, or overlay at a time. Record median frame time, slow-frame spikes, and whether the symptom moved.
Check display refresh rate and the game's requested presentation rate. On mobile hardware, control temperature and power mode because throttling can make a later run incomparable with a cold start. On PC, record driver and overlay changes. On every platform, keep the test duration and content consistent.
Verify the repair
Re-enable unrelated production settings and rerun the original scenario on the affected hardware plus at least one comparison device. Confirm both the target frame rate and stable pacing through the problem interval. Check input response and visual artifacts, not just the counter. Close the change log with the root cause, exact fix, trace links, hardware coverage, and performance budget. If the fix only lowers quality or hides spikes without explaining them, record it as a tradeoff or workaround rather than a resolved defect.
Sources
- Frame Pacing library — Google
- Frame Pacing Sample — Microsoft Learn, Sept. 14, 2026