Metal Gear & Metal Gear 2: Solid Snake (PPSA14408)

[JJenkx]

Tested Metal Gear & Metal Gear 2: Solid Snake (PPSA14408) 01.500.000 natively on Linux 7.2.9 / Ryzen 9 7950X / Radeon RX 6650 XT, RADV Mesa 26.2.4. Short bring-up check.

Result

On plain main eb73c168bb and 61d0fa5b3c, the Unity launcher (eboot.bin) runs at a steady 59.94 FPS through:

• the Terms of Use prompt (Confirm, then Agree),
• the main menu (Game Selection / Master Book / Screenplay Book / Options / Legal and Privacy) and the Master Book spoiler prompt.

Choosing a game from Game Selection starts the game executable with sceSystemServiceLoadExec (/app0/PS/eboot.bin -mgst mg1 -region eu -lan en ...). That executable creates its Vulkan device, then stops on its first depth-copy draw:

AGC graphics: DB_RENDER_CONTROL depth copy, resummarize or decompress is unsupported (register 0x0 = 0x00000084)

This is the same stop as #6304 (DEPTH_COPY with COPY_CENTROID). #5499 implements DB depth copies but conflicts with current main. Its own relinker predates --module-dir . handling beside --executable, so this layout could not be relinked and tested with it.

Setup

The launcher starts a second executable, and mg1.prx/mg2.prx sit in the package root:

relinker --registry --rpath <build>/core/libs/libs --module-dir Media/Modules --module-dir Media/Plugins --module-dir . --executable PS/eboot.bin eboot.elf app.elf

Unwrap PS/eboot.bin into the input tree first. The menu reads the D-pad: the cursor moves once no dialog is open.

AI-assisted testing and report: yes, Claude Code.

[JJenkx]

Retest with the rebased #5499 (milescoviello:rebase/5499-db-depth-copy at 95ca794b31), as promised above. Linux 7.2.9 / Ryzen 9 7950X / Radeon RX 6650 XT, RADV Mesa 26.2.4.

Pins

• Base: eea640a5bf, the merge base of that branch with main.
• Candidate: 95ca794b31 (20e49f00d9 by codingreapermaps plus 95ca794b31 by milescoviello).
• Both are clean Release builds from separate worktrees, with separate runtimes and fresh saves.

Conversion, the same as above. Run with the build's own relinker, from the runtime directory, with PS/eboot.bin unwrapped into the input tree:

relinker --registry --rpath <build>/core/libs/libs --module-dir Media/Modules --module-dir Media/Plugins --module-dir . --executable PS/eboot.bin eboot.elf app.elf

Scene: the same scripted input in both runs. Cross is held for 800 ms every 8 s from 62 s to 110 s. That walks a fresh save from the title through the main menu, Game Selection > Metal Gear, Language Selection (English) and Start Menu > START GAME. The screenshots of both runs show the same screens up to the launch. Both launchers then call ExitAndStartNewProject -mgst mg1 -region eu -lan en ..., and MG1 starts.

Result

• Base eea640a5bf: aborts at 97.7 s with AGC graphics: DB_RENDER_CONTROL depth copy, resummarize or decompress is unsupported (register 0x0 = 0x00000084). This is the stop reported above.
• feat(agc): run DB depth copies into a single-sample R32 float target #5499 95ca794b31: gets past that check, but aborts at the same point (97.0 s) with AGC graphics: DB depth copy from a depth plane no draw rendered. That message comes from the branch's CopyDepthSample (Graphics/src/DepthSurface.cpp:2211): the copy's source depth address has no depth surface that a draw rendered on the host. Nothing renders the depth plane before MG1's first depth copy, at least nothing the driver tracks as a depth surface.
• The launcher runs at 59.94 FPS on both until the second executable starts. No other driver failure is logged before the stop.

So the rebased #5499 does not get MG1 to its first frame yet. The next missing case is a depth copy whose source plane was only cleared or written outside a draw. I haven't checked which of the two it is here; that needs the source plane's last writer, such as an HTILE clear or a compute or CPU write. No validation-layer run and no frame-rate comparison were done for this, because both builds stop before MG1 renders.

AI-assisted testing and report: yes, Claude Code.