Biped (PPSA24589)

[THEMANnt]

Existing thread

• I searched this category for the title ID and no thread exists for this title on any platform.

Title

Biped (PPSA24589)

Content version tested

01.000.002

AnyPS5 commit

Unmodified main at f894ba69d30055259a56907563f438379d1275a3, built locally. No PRs or local code changes applied.

System tested

• Windows 11 Pro 25H2, build 26200.9711
• AMD Ryzen 7 7800X3D; 32 GB RAM
• NVIDIA GeForce RTX 5070 Ti, 16 GB VRAM; driver 616.92
• MinGW-w64 GCC 15.2, Release build

Furthest point

In game

What is shown

The title screen, menus and Solo Biped Training are reachable. Leg rotation, walking, skating, collecting items and object-interaction sections were reached. Controller/keyboard input works, and checkpoint saving indicators appear. Save reload has not been verified.

The initial leg-training section ran at approximately 25 FPS, with later training sections around 40–58 FPS. Earlier manual gameplay was reported at 26–50 FPS. These are observations from different sections, not a comparison of the same scene.

Gameplay audio was reported as good; cutscene audio was reported as bugged. The precise audio symptom has not yet been isolated.

The latest recorded session aborted after 703.97 seconds total runtime (11 minutes 44 seconds, including startup, menus and gameplay). It did not reach the recording's 15-minute limit. The exact action at this final stop was not independently captured. This is reachable gameplay with stability blockers, not a full compatibility result.

Current blocker

The captured failure is:

[gpu] driver failure: AGC graphics: storage texture has no committed guest pages
[videoout] presentation failed: AGC graphics: storage texture has no committed guest pages
terminate called after throwing an instance of 'std::runtime_error'
  what():  AGC graphics: storage texture has no committed guest pages
FATAL: abort() (SIGABRT) on thread 6580

Windows process exit code: 0xC0000409. The memory watchdog did not terminate the run; minimum recorded available physical RAM was 6.43 GiB, above its 5 GiB threshold. Available commit stayed above its 8 GiB threshold as well.

An earlier recorded session also stopped with this exact graphics error when returning to the main menu. A separate manual retest was reported to crash after approximately five minutes of gameplay; no guest log was captured for that separate retest.

Related: #9275 documents the same storage-image refusal in other titles. It is documentation only, not a fix, and does not establish Biped's underlying cause. No Biped-specific issue or fix PR was found in the search, and no workaround or local code patch was used. Root cause remains unresolved.

How it was run

The executable and all eight bundled modules were converted with the main-build relinker, including both Unity module directories:

relinker.exe --windows --windows-diagnostics --registry --no-patches --module-dir Media/Modules --module-dir Media/Plugins inputs/eboot.elf runtime/biped.exe

Ran biped.exe with the original assets under app0 and the same main build's system libraries under libs. Original sce_sys/param.json retained without overrides.

Selected Continue → SOLO → Biped Training and progressed through training. The recording initially included controller-file inputs and local controls; after I took over, gameplay was manual. APS5_PAD_INPUT_FILE enabled the initial diagnostic controller commands, and APS5_VIDEOOUT_TELEMETRY_DIR recorded FPS and pad events. Full stdout/stderr and available-memory samples were captured locally. No shader-dump, draw-skipping or title-specific compatibility flags were enabled.

AI-assisted: yes (Codex); execution results were collected locally and gameplay/audio observations were supplied by me.

[EagleBearerYS]

@THEMANnt, storage texture has no committed guest pages is also what #9406 (JJenkx, open) fixes for Wobbly Life (PPSA29413): a depth plane a draw wrote is stored later, after the title has unmapped its memory. Could you try Biped (PPSA24589) with #9406 on top of current main? If the stop goes away in a run of the same length, a note on #9406 would help it get reviewed. If it stays, the lines just before it would show which storage image it is.

[THEMANnt]

@EagleBearerYS Retested on Windows on 2026-10-22: #9406 resolves the reproduced pause/menu stop in this run.

• Main 7e2ba73e4c8c26b5d632b0d2f46166ffc1b8a29d: opening the pause menu with Esc hit storage texture has no committed guest pages and SIGABRT at about 170 s. The watchdog subsequently terminated the failing process at 172.08 s for low available RAM.
• PR head 1855089a95e9ab865a4b50d952c6e72044e3f9c4 merged onto the same main: pause/resume and returning to the main menu worked. The session reached its planned 15-minute limit without another graphics failure; gameplay after resuming remained responsive. This includes startup and time idle in menus, not 15 minutes of continuous gameplay.
• The new depth-plane check was exercised: depth plane 0x268950000+0x1000000 was unmapped with GPU results pending; they are dropped.
• The same three focused AGC tests passed on both trees with the required Vulkan/validation environment, zero VUID matches and no missing-layer warning, on the RTX 5070 Ti.

Main-menu music is still absent; gameplay music works. Cutscene audio was not rechecked, and save reload/full-game stability remains unverified.

Full paired test report on #9406. Same source assets and starting save, isolated runtime libraries, no game-specific changes. Windows 11 Pro build 26200, Ryzen 7 7800X3D, 32 GB RAM, RTX 5070 Ti 16 GB / NVIDIA 616.92, GCC 15.2 Release.

AI-assisted: yes (Codex prepared builds/logging and checked results; I controlled and visually tested the game).