Marvel's Wolverine 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

Marvel's Wolverine is early, but moving. On 11 October a tester on Windows got it through its intro videos for the first time, using current main plus several open pull requests. Right after the intros it stops at a draw that uses fast-launch, mesh-style geometry, which nobody had implemented. A maintainer says a first fix for it is welcome, and another game (PPSA02530) stops on the same thing, so it should get attention.

Two earlier stops are now dealt with. The crash a few minutes in, when the game signals a semaphore (a thread lock) with a count of zero, was closed on 10 October with a fix in a pull request. The first frame failing because a pixel shader reads a value the vertex shader never writes was closed on 11 October: the fix makes those reads return zero, as the console does.

A set of fixes from late September is merged and let the game run longer: Windows thread-local storage for the game's C library, a fixed memory reservation the game relies on, and a command buffer fix.

The biggest hurdle for a normal setup is a missing library. The game relies on Sony's libSceNpCppWebApi, which it does not ship in its dump, and AnyPS5 no longer provides a replacement. 147 of the game's 150 unresolved imports come from it. One tester rebuilt an old replacement to try to get past this, but it was missing 129 of the 147 functions and stopped on the next one. Another run got further, so how exactly it was bypassed is not fully explained in the threads.

Some game files are also wrapped in an unusual container (starts 54 14 f5 ee), which has to be unwrapped before the relinker can read it. A merged change now says so clearly instead of showing a vague error.

What is stopping it

• After the intros the game issues a draw with GS_FAST_LAUNCH set (mesh-style geometry). A first step to decode it (#4702) is on main since 14 October, but 131 of the game's vertex programs still fail to compile (an unsupported barrier instruction), so the issue stays open. Thread
• The game needs Sony's libSceNpCppWebApi, which is not in its dump and not provided by AnyPS5. 147 of 150 unresolved imports come from it. Thread
• The dump's files are in a second SELF container format (54 14 f5 ee) that has to be unwrapped before relinking. Thread

How it got here

1. 30 Sep 2026Merged: Windows modules with thread-local storage now get proper setup; the game's C library had been overwriting other memory and crashing new threads. Source
2. 30 Sep 2026Merged: fixed memory reservations are honoured, and an empty command buffer no longer throws. Both were hit by Wolverine's heaps and start-up. Source
3. 7 Oct 2026A user reports the game cannot start because libSceNpCppWebApi is missing from the dump. Source
4. 8 Oct 2026Merged: the relinker now names the second SELF container format the dump uses instead of a vague 'invalid ELF magic' error. Source
5. 9 Oct 2026Measured import coverage: 931 unique imports, 507 implemented, 150 absent, 147 of those from libSceNpCppWebApi. Source
6. 10 Oct 2026A tester finds a crash after a few minutes from a zero-count semaphore signal. With a fork fix, Wolverine gets past it and starts issuing draws. Source
7. 10 Oct 2026First presentation attempt fails because a pixel shader reads a value the vertex shader never exports. Source
8. 11 Oct 2026The fix for shaders reading a value the vertex shader never writes is proposed (reads return zero, as on the console), and the issue is closed. Source
9. 11 Oct 2026Wolverine gets through its intro videos for the first time, on main plus seven pull requests, and stops at a fast-launch geometry draw. Source
10. 14 Oct 2026Merged: a first step to decode fast-launch geometry (one point per subgroup). It does not yet cover the 131 vertex programs that fail on a barrier instruction. Source

Tested hardware