The time-based-clock claim rests on two captures that happened to run at
different speeds. Nobody has changed the frame rate on purpose and watched.
--framerate_limit=30 halves Xenia's vblank ceiling. Predictions committed
before the run:
quantity frame-based time-based (my claim)
presents/s ~27 ~27
modal alpha step 17, unchanged 34, DOUBLED
units/s ~30, halved ~60, unchanged
splash dwells ~8.5 / ~7.0 s ~4.2 / ~3.5 s, unchanged
Accept time-based only if the step lands in 30-38 AND the dwell stays
within 10% of 4.2/3.5 s. If the step stays 17 and the dwell doubles, the
claim is refuted, the clock is frame-based, and the port's 60 is unsupported
again.
The control is the present rate itself, read FIRST: a doubled step also
appears if the limiter did nothing, so if presents/s does not fall to ~27
neither prediction is tested. Second control: the eight splash quad rects
must be unchanged, or something other than the frame rate differs between
runs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t
