mirror of
https://github.com/RetroPortingToolKit/psxrecomp
synced 2026-10-27 02:32:02 -04:00
Matthew Stanley
8a2f01d79d
Set memory.c main-RAM load wait-state to 4, the Beetle-oracle-accurate value (ruler #2 load loop == Beetle exactly at 4; the old 6 was DuckStation's). This is the faithful value and we keep it. ⚠ ISSUE THIS COMMIT CAUSES (and why we proceed): load=4 DETERMINISTICALLY wedges Tomba 2's BIOS-shell boot — pc=0/exception at shell pc 0xBFC2CE64 (epc 0x80000048), reproducible at identical total_checks across restarts. The faster-but-accurate load makes the CPU outrun a shell loop's timing assumption, exposing a real downstream bug (incomplete device/loop timing). Per CLAUDE.md Rule -1 (faithful core, no masking with a wrong cost) we LAND the accurate value and root-cause the real wedge, rather than revert to 6 to hide it. Until the wedge is fixed Tomba 2 won't reach the FMV on THIS branch (wt/tomba2-load-accuracy); ruler #2 (its own boot disc, no shell loop) is unaffected and still validates the cost model. Branch wt/tomba2-load-accuracy forks from wt/tomba2-cycle-audit (which keeps the booting value 6). Next: root-cause 0xBFC2CE64. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>