RPCS3 Fix Stops Crashes in Six PS3 Ratchet & Clank Games, but Performance Remains In-Game

"Crash-free" is not "playable," and the gap between the two matters for anyone planning a weekend of PS3 emulation on a Windows box.

What actually changed​

The fix is in RPCS3's emulation of the RSX, the PS3's graphics processor. FIFO means first-in, first-out. The RSX consumes a queue of graphics commands, and the "GET" pointer tracks how far the processor has read into that queue. If the emulator's GET value is wrong at the wrong moment, the command stream can desynchronize. That is general background, not a detail from the announcement.

RPCS3's history with this subsystem helps explain why such a fix is plausible. An older elad335 pull request on GitHub added a log prefix showing the current FIFO GET register. It also fixed FIFO stack recovery, and it targeted games that hit "RSX: FIFO error: possible desync event" errors. A separate 2022 change made RPCS3 suggest raising the RSX FIFO Accuracy setting after a crash. FIFO behavior has been a recurring source of stability problems in the project.

Two limits on the evidence:

• The announcement gives no commit, build number or benchmark data.
• One outlet, GameGPU, described a related stability update in broader terms and said a new build is on the project's site. That is secondary reporting, and I could not tie it to a specific build.

TweakTown says the emulator "can now read game instructions in the correct order." That is a simplification, not a technical explanation confirmed by RPCS3.

Crash-free is not the same as playable​

TweakTown notes that most of the six entries are still labeled "In-Game" on RPCS3's compatibility list. The project describes that tier as games that can't be finished, have serious glitches, or have insufficient performance.

Overclock3D adds a useful detail. The RPCS3 team says a game reaches "Playable" only when its performance matches PS3 levels on RPCS3's recommended specifications. Overclock3D reads this to mean that, with a sufficiently powerful PC, users can already get playable performance, while games stay at "Ingame" until the recommended hardware gets there. Notebookcheck likewise reports that the games aren't classed as "Playable" because of insufficient performance.

So the "In-Game" label here may reflect speed on reference hardware more than a pile of visible bugs. Nobody has published a per-game breakdown, so I won't guess which problem affects which title.

One more detail​

According to a post on X from the AGTP account, RPCS3 said the Ratchet & Clank HD collection never had this crash problem. That account also says only the games built on Insomniac's own PS3 engines did. This is a social-media relay of the team's replies, so treat it as lead-level information. It would explain why the list covers the later standalone releases.

How to check your own copy​

RPCS3's wiki explains that compatibility is tracked per Game ID, batched by media, and not per game title. The disc and digital versions of the same game have separate entries on the list. Regional IDs also need separate reports.

1. Find the Game ID of the edition you own: disc, PSN download, or regional release.
2. Search the RPCS3 compatibility list for that ID and read its status.
3. Open the linked forum thread for recent user reports on hardware and settings.
4. Update to a current RPCS3 build before testing. I couldn't verify which build first contained this fix.

If you still get crashes, RPCS3 has previously suggested raising the RSX FIFO Accuracy setting. I couldn't confirm that doing so is needed or helpful for these six titles after the new fix.

Hardware expectations​

Neither source gives a recommended CPU or GPU, game-specific settings or benchmarks for these games. TweakTown's advice that you'll need a "beefy" PC is broad and unquantified. Treat performance as unknown until you test your own setup. Older forum reports for Tools of Destruction exist, but they come from earlier builds and different hardware. They shouldn't be taken as current performance data.

The bigger picture​

The milestone fits a strong year for the project. According to Overclock3D, the "Playable" count has risen from 2,558 in January 2026 to 2,809, and RPCS3 rates more than 99% of PS3 games as "Ingame" or "Playable." RPCS3's wiki table shows the September 2026 figures: 2,809 Playable, 721 Ingame, 31 Intro and 2 Loadable, out of 3,563 entries.

The takeaway: a project-wide stability fix is real progress, and it gives these six games a better shot at a full "Playable" rating. Until the compatibility entry for your Game ID changes, expect to tune settings and possibly accept uneven frame rates.