From 1f30595b8a61fc956e555dd1138bf2c4ccc84eaa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Rydg=C3=A5rd?= Date: Mon, 12 Oct 2026 03:56:43 +0200 Subject: [PATCH] Docs: Mention --frame-stats for checking a game after a state load Co-Authored-By: Claude Opus 5.5 --- docs/debugging.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/debugging.md b/docs/debugging.md index 53742585fc..21a664d25c 100644 --- a/docs/debugging.md +++ b/docs/debugging.md @@ -220,6 +220,10 @@ To smoke-test a CPU or GPU change on real games, run the old and the new binary run to run, so a different screenshot means different behaviour. God of War: Chains of Olympus isn't: its menu animation follows wall-clock time, so even the same binary lands on different frames. +To check that a game keeps running after `--state=` loads, pass `--frame-stats`: at the end of the run it prints +the flips in each emulated second since the load. A stuck or crashed game shows as zeros or a short list, and a +steady game as a flat 30 or 60. The state's load result is printed too, and a failed load exits 1. + For audio, `--dump-audio=FILE.wav` records the mixed output (before the game volume setting) for the whole run. An audio glitch you can hear usually shows in the waveform: a click is a jump between neighbouring samples, and a repeated or dropped mixer block is two identical 64-sample runs in a row.