Ratchet & Clank: Rift Apart on AnyPS5

Screenshots

No screenshot of this game running has been posted in the project's threads yet. Testers who reach a new screen usually post one in the discussion linked on the right.

Where it stands

On Linux, contributor EdouardSence (RX 9070 XT, using an AI assistant for testing) got the game to present its first frames on October 9. The first dumped frames are correct: a splash with Ratchet's face, then the PlayStation Studios logo fading out. After that the image stays black. The game keeps drawing and nothing throws an error. It presented about 33 frames per second for six minutes. The cause of the black screen is not known yet. It could be loading, an intro movie that is not decoded, or a rendering problem.

That result needed about 15 pull requests stacked on main, some still open. On plain main the game does not even load at first (missing mlock/munlock functions). Fixes to get this far include the game's thread-ID layout (it read it straight from the thread object and crashed about 19 s in), a conservative-rasterization setting, depth-clear draws, null pixel programs, and deferring shaders that cannot be prepared at start-up.

Since then, a couple of newer main changes caused new stops: a stack overflow in shader registration on the game's small thread stacks (since fixed), and a memory-map placement change that put the game's heap addresses in the wrong place (fixed by merged #2907). The latest report (main 91b13413, RTX 5080) crashes about 40 s in because the AMM memory range overlaps the memory the game maps (issue #3146, open). Another open issue (#2621) is a pixel shader drawn under a different state than prepared at about 55-64 s. A local test that prepared that variant ran 240 s without a crash, with the intro and the Insomniac logo rendering, then black.

Only Linux is reported. Nothing is said about Windows or macOS.

What is stopping it

• Segfault about 40 s in on main 91b13413: the AMM range reservation overlaps the heap addresses the game maps itself (RTX 5080). Thread
• A registered pixel shader is later drawn with different state (DB_SHADER_CONTROL=0), so the prepared variant is missing and the game stops at about 55-64 s. Thread
• The picture goes black after the logos; cause unknown (loading, undecoded intro movie, or rendering). A color-views-of-several-array-slices limit (#2102) also stops some runs earlier. Thread

How it got here

1. 9 Oct 2026Bring-up thread opened: main fails to load (missing mlock/munlock); a stack of fixes then reaches shader registration and first draws. Source
2. 9 Oct 2026First frames presented on a stack of about 15 PRs: splash with Ratchet's face, PlayStation Studios logo, then black, at about 33 frames per second. Source
3. 10 Oct 2026Thread-ID layout fix merged: the game read it from the first field of the thread object and crashed about 19 s in. Source
4. 10 Oct 2026Conservative-rasterization setting the game writes on its first draws is accepted (merged). Source
5. 10 Oct 2026Shaders that cannot be prepared at start-up are deferred to first use (merged). Source
6. 10 Oct 2026Stack overflow in shader registration on the game's small thread stacks is reported (since #1988); later closed as fixed. Source
7. 10 Oct 2026Fix merged for hinted memory maps placed above the game's 64 GiB reservation. Source
8. 10 Oct 2026New crash about 40 s in, where the AMM range overlaps the game's own memory maps (RTX 5080). Source

Tested hardware