Mortal Kombat 11 (PPSA01619)

[Gooshy]

Existing thread

• I searched this category for PPSA01619 and "Mortal Kombat"; no thread exists.

Title

Mortal Kombat 11 (PPSA01619)

Content version tested

01.000.004 (sce_sys/param.json).

AnyPS5 commit

main 88795ed44 with local changes (listed under Current blocker), last run on 2026-10-27. The stops below are still in the code on main b28bb7721.

System tested

Bazzite (Fedora 44, kernel 7.2.11), AMD Radeon RX 9060 XT, RADV Mesa 26.2.4, GCC 16, Release.

Furthest point

In game.

What is shown

With the changes below, fights run and render correctly at 1080p: a player fight (Scorpion against a CPU Sub-Zero on Special Forces Desert Command) runs at about 19 to 21 FPS over several runs. Queue worker 0 is about 98% busy, and the GPU takes about 29 ms per present, so the speed is CPU-bound on draw submission. Menus, character select and the attract-mode fights also run. Audio plays and the pad works.

Current blocker

On main:

1. The first fight stops with a line polygon mode wider or narrower than one pixel: the title draws lines with PA_SU_LINE_CNTL = 0x10 (two pixels). Fixed by feat(agc): draw line polygon modes at the PA_SU_LINE_CNTL width #9489.
2. Character select stops presenting with color export format 4 into an unsigned integer target is unsupported, which has been thrown since fix(libSceAgcDriver): export raw 32-bit values into UINT color targets as integers #9789. The screen freezes, which looks like a dead pad. I keep these exports on the float path locally as a workaround; it is not a correct fix, and I haven't opened a PR for it.
3. Some attract-mode fights stop with atomic image descriptor uses an unsupported format 11: a compute pass reduces 16-bit texels with ImageAtomicUMin32. I run it locally through an R32_UINT twin of the 16_UINT surface; the PR waits for my open PR limit.

Other local changes:

• Cull distances from tessellation evaluation shaders: now on main through fix(agc): accept cull distances from tessellation evaluation shaders #13492.
• Importing direct memory that spans several backings through one udmabuf list. I haven't checked whether main's run-list import (d5b768f02 and the commits before it) makes this unnecessary.
• Performance changes only, which the title doesn't need to run.

How it was run

relinker --registry src/eboot.elf app.elf
APS5_PIPELINED_DRAWS=32 APS5_PIPELINE_DISPATCH=1 ./app.elf

src/ holds the title's eboot.elf and sce_module/; the built libraries are copied to libs/ next to app.elf. The two variables only change speed (about +1.5 FPS in fights).

AI-assisted testing and report: yes.