a40a0b7b01
The 16.16 reading of +0x04 rested on twelve bundles at 30.0. They are not twelve witnesses: they are TWO bundles - pghud_range_main_em/emeff and pghud_range_nose_em/emeff, both dur 30 - repeated across six language PAKs. A 30-frame flash is equally consistent with 0.5 s at 60 and 1 s at 30, so the observation that "30.0 bundles are shorter" says almost nothing. Worse for the clean fixed-point reading: the four bundles at 0x3C0001 would be 60.0000152 fps, which nobody authors. They are py_ranking_jump/py_ranking_next dialogs, all dur 60. So the better reading is <rate:16>.<flag:16> - a rate-like number in the high half and a small low field that is 0 on 2843 bundles and 1 on four, meaning unknown. Also stated: nothing in this container can settle it by timing, because the emulator runs on software Vulkan far from real time - a stopwatch would measure lavapipe rather than the game. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE