mirror of
https://github.com/ARMSX2/ARMSX3.git
synced 2026-08-24 16:58:52 -07:00
jpolo1224
4a7ef6f4c8
Ours was false against upstream's true, so the curated push wrote false over the node on every boot and every install ran with an accuracy fixup disabled that RPCS3 ships on. Games that depend on it get NaNs through vector maths, which shows up as geometry behaving impossibly rather than as any kind of error. The disagreement was not free either. The node feeds ppu_settings::fixup_vnan, which is part of the compiled PPU object filename, so flipping it renames every object and the next boot recompiles all of them. A device here carries both variants, 76 modules under one key and 58 under the other, from one flip. Audited the other two settings in that key: Accurate Cache Line Stores and Use Accurate DFMA both already match upstream. This was the only one adrift. All three now say that changing them rebuilds compiled PPU code, which is the part that had no way of being known from the screen.