Ran the cheapest confirmation from a991088 on the candidate:
[247.000, 194.000, 49.890] step 0.000
[293.960, 411.810, 115.000] step 232.133
[506.306, 311.614, 116.656] step 234.804
[300.170, 227.480, 128.000] step 222.933
Rejected. A camera between consecutive frames moves a little; this moves ~230 units
per step and is not monotone on any axis. It is per-frame state but not a camera
position. a991088 wrote the prediction down before the measurement, so the
candidate is out rather than reinterpreted.
The more useful consequence: these four savestates are not consecutive frames, so
smoothness cannot filter the 2,005 candidates until consecutive frames exist.
Both cheap confirmations need something the savestates do not provide -- consecutive
frames, or an actual camera perturbation. That moves the camera hunt from offline
to needing a PCSX2 PINE session, the same category as the tfrag morph.
Worth noting the shape of it: the differential produced 2,005 candidates and the
confirmation reduced them to zero in one step, because the confirmation was
written before the measurement was interpreted rather than after.
286 passing with the disc and savestate present, clippy clean.
ReaperOfVeriod
1aa94ee288