PPSA03671 / Action adventure
Marvel’s Wolverine · PPSA03671 on AnyPS5. Windows: Startup (Locally modified); Linux: Startup (Locally modified). Check the PS5 edition, build, patches and original evidence before testing.
PS5 title ID PPSA03671. Match this ID to your edition, then compare the content version, operating system, build and patches in each report. A matching ID alone does not establish compatibility.
An editorial selection of scoped reports, not a guarantee for the latest build. Read the evidence before choosing your setup.
The opening presentation card and render loop appear at a reported 2–3.5 FPS in two four-minute runs. Local stubs, skipped draws/dispatches and validation changes remain required. No menu, controllable scene or full rendering result is established.
AnyPS5 buildmain d1670009f + local Pad/WebApi stubs + drop-failed work + large SPIR-V validation bypass
Reports behind this summary · Community reportToolchain: GCC 15.3.0. Earlier local builds show a partial 3D scene. This later build fixes several shader refusals but exhausts device memory around 175 seconds; its counter is 0.1–0.17 FPS. Dropping failed work does not prove correct rendering, control or that a larger GPU would solve the allocation failure.
AnyPS5 buildmain e34c47921 + local drop-on-failure patch
Reports behind this summary · Community report
Logan’s action adventure requires visible, controllable scenes beyond logos and partial renders.
This page covers the PS5 release. A PS4 edition, native PC release or console performance mode is not an AnyPS5 test. Confirm the title ID and version before comparing reports.
Official game informationCommunity report · Linux
Toolchain: GCC 15.3.0. Earlier local builds show a partial 3D scene. This later build fixes several shader refusals but exhausts device memory around 175 seconds; its counter is 0.1–0.17 FPS. Dropping failed work does not prove correct rendering, control or that a larger GPU would solve the allocation failure.
The source does not provide an FPS measurement tied to specific hardware.
Toolchain: GCC 15.3.0. Earlier local builds show a partial 3D scene. This later build fixes several shader refusals but exhausts device memory around 175 seconds; its counter is 0.1–0.17 FPS. Dropping failed work does not prove correct rendering, control or that a larger GPU would solve the allocation failure.
Results come from the original reports; this site has not reproduced the tests. The stage shown is the furthest point reported, not a guarantee of stable play. Locally modified results may rely on forks, patches or changes to game files.
Community report · Windows
The opening presentation card and render loop appear at a reported 2–3.5 FPS in two four-minute runs. Local stubs, skipped draws/dispatches and validation changes remain required. No menu, controllable scene or full rendering result is established.
The source does not provide an FPS measurement tied to specific hardware.
The opening presentation card and render loop appear at a reported 2–3.5 FPS in two four-minute runs. Local stubs, skipped draws/dispatches and validation changes remain required. No menu, controllable scene or full rendering result is established.
Results come from the original reports; this site has not reproduced the tests. The stage shown is the furthest point reported, not a guarantee of stable play. Locally modified results may rely on forks, patches or changes to game files.
These versions belong to individual reports, not every edition of the game. An unknown version remains unknown; demos, expansions and other PPSA editions need their own evidence.
Promotional images from the publisher’s game page. These are not screenshots of the game running in AnyPS5. Images are hosted on this site; rights remain with their owners.
Official game informationResults come from the original reports; this site has not reproduced the tests.
Source policy · Read more
Record the PS5 title ID, game version, AnyPS5 commit and operating system. Note any local changes, then test startup, menus, gameplay, audio and saves separately. Attach the first relevant error and a short capture of the same build.
