What was fixed
The RPCS3 team announced on X that developer Yahfz "fixed the flickering blue squares that appeared during movement" in the game. The fix has already spread beyond the desktop emulator. The ARMSX3 release notes, an Android port of RPCS3 for ARM64 devices, list the same fix as coming from RPCS3 by Yahfz.
The bug has a detailed public record in RPCS3's issue tracker, filed under the North American disc ID BLUS31194 on September 22, 2026. The reporter described large, transparent blue squares flickering around the legs of both the player's and enemy ACs while moving. The reporter tied this to the dynamic light from the mech's boosters. The corruption showed up when moving away from vertical walls or props with boosters on. When you hug a wall, your booster tints the surface blue, and that lighting is what broke as you moved away.
The reporter included a repro recipe:
- Go to Workshop, then AC Test.
- Move left until you fall off the ramp.
- Wall-jump on the side of the ramp with X/Cross.
The reporter also supplied a PS3 capture for comparison and confirmed the bug was old, not a regression. The reporter's setup was a Ryzen 7 7700X, a GTX 1050 Ti on Vulkan, Windows 10 build 19045 and PS3 firmware 4.91. The issue page shows a maintainer closing it as completed on October 2, 2026, through pull request #19669. That is ten days before Notebookcheck's story. I couldn't retrieve the pull request itself, so I can't describe the technical change.
"No known issues" isn't "Playable"
Notebookcheck says the game now has no known issues listed in RPCS3's database. It also says the game is still in the "Ingame" list.
RPCS3's wiki explains the structure. The compatibility list uses five statuses: Playable, Ingame, Intro, Loadable and Nothing. A game's status reflects how far it gets and how well it runs, and a single fixed bug doesn't change that by itself. Entries are also reviewed before they're added to the list. A rating change takes a new user report submitted to the game's forum thread and approved by reviewers, not just a code fix.
Notebookcheck suspects performance is what keeps the game out of "Playable". That is the outlet's guess, not an RPCS3 statement. The game has a long history of other problems. Older reports describe memory-access-violation crashes and users juggling settings like write color buffers and SPU thread limits to get through missions. Those reports are years old, and I can't tell from the evidence which ones still apply. Treat them as background, not as current status.
The 79.4% figure
Notebookcheck says RPCS3 can currently play 79.4% of the PS3 library with no issues and good performance. I couldn't reproduce that exact number. RPCS3's wiki publishes monthly counts per status, and the latest row is September 2026:
| Status | Games (Sep 2026) |
|---|---|
| Playable | 2,809 |
| Ingame | 721 |
| Intro | 31 |
| Loadable | 2 |
| Total | 3,563 |
By my arithmetic, 2,809 of 3,563 is about 78.8%. The gap from 79.4% could come from an October update, a different denominator or a live-site calculation. The direction is clear either way. The playable count rose from 2,693 in July to 2,758 in August and 2,809 in September, while Ingame fell from 805 to 721. That is steady progress, and Verdict Day is one of the remaining Ingame titles.
Notebookcheck's other claims
- "PS3-exclusive": The game was released for both PlayStation 3 and Xbox 360, per Wikipedia. It isn't a PS3 exclusive.
- Hardware: Notebookcheck suggests that a system with a stronger CPU than the Ryzen 5 5600 may already run the game with good performance. That is plausible but untested here. RPCS3's compatibility entries are per game ID, so check yours.
What to do if you want to try it
- Find your exact game ID, such as BLUS31194, and look up its entry in RPCS3's compatibility list.
- Update to a current RPCS3 build, since the fix landed in early October 2026.
- Use the AC Test repro above to see whether the blue squares are gone on your setup.
- If you get a good run, post a report in the game's forum thread. That is how a rating can change.
Bottom line
This is a real, documented bug fix. It removes a distracting visual flaw from a game that long needed work. It also shows how RPCS3 tracks progress. Fixes land in code first, and the "Playable" label follows only after reviewed reports show the game runs well.