Hollow Knight: Voidheart Edition (PPSA34971)

[ryyReid]

Existing thread

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

Title

Hollow Knight: Voidheart Edition (PPSA34971)

Content version tested

01.000.002

AnyPS5 commit

main 30f9612, nothing on top; the executable has since been rebuilt on feddf7f4c and not yet played. The only thing outside main is the input: the title's eboot.bin and eleven *.prx are decrypted SELF containers, so they were unwrapped with tools/unwrap_self.py, open as #5588.

System tested

Windows 11 Pro (10.0.26200), Ryzen 5 5500, RTX 3070 (driver 32.0.16.1062), 32 GiB RAM, NVMe SSD, WinLibs GCC 15.2.0 r7, Release build.

Furthest point

In game

What is shown

Runnable and playable. 60 FPS in game and 120 FPS in the menus (window counter). The title boots, gets through the logos and the menu, and plays; the window presents a 1920x1080 guest surface, and the shader disk cache warms across runs (114 hits, 30 misses, 30 writes over two runs). A save slot was written, _sd\savedata1\user1.dat (49,390 bytes), so it got far enough to save.

Not tested: audio, stick input, and whether APS5_STORE_AT_FLIP=1 changes anything.

Relinked and tested with Claude Code (AI); the runs are on my machine and the result was checked in the window.

Current blocker

None for playability. Two notes.

The storage-image hazard is live here, every frame, on two addresses:

[gpu] storage image 0x23dd70000: guest memory changed while GPU results were pending; keeping the CPU's blocks
[gpu] storage image 0x2417d0000: guest memory changed while GPU results were pending; keeping the CPU's blocks
...
[gpu] storage image 0x2417d0000+0x870000: memory no longer registered; 1 pending ranges dropped

That is the same shape as the Silksong threads describe (#1970, APS5_STORE_AT_FLIP=1), on the same engine. Nothing visibly wrong was noticed in game, and the switch has not been tried here yet.

The run needed one tool that is not merged, the container unwrap (#5588), because the relinker reads a plain ELF and skips SELF with a warning. Everything else is stock main.

One warning worth recording, from the same family as the missing static shader ABI register 201 stop Silksong lists (#1836): here it is handled and deferred instead of fatal.

[Shaders/ShaderRegistry.cpp:644 operator()] Shader 0x21ac6ce00 could not be prepared at
registration (its program address is not in the shader registers); preparing it when it is used

How it was run

python tools/unwrap_self.py <dump>/eboot.bin source/eboot.elf
python tools/unwrap_self.py <dump>/sce_module/<name>.prx source/sce_module/<name>.prx
python tools/unwrap_self.py <dump>/Media/Modules/<name>.prx source/Media/Modules/<name>.prx
python tools/unwrap_self.py <dump>/Media/Plugins/<name>.prx source/Media/Plugins/<name>.prx
relinker --windows --windows-gui --registry \
  --module-dir Media/Modules --module-dir Media/Plugins \
  source/eboot.elf out/HollowKnight.exe

Then libs/ from build/core/libs/libs with the three MinGW DLLs beside the executable, and app0/ holding the title's Media and sce_sys, with the eleven *.guest.prx where the relinker puts them (app0/sce_module, app0/Media/Modules, app0/Media/Plugins).

Beyond the usage guide the title needed no APS5_*/ANYPS5_* variable and no anyps5-fonts/ — it opens no system font set. Unlike Silksong, Il2cppUserAssemblies.prx.guest.prx does not have to be renamed. Buttons were sent through APS5_PAD_INPUT_FILE with tools/pad_input.py.

Related threads

Hollow Knight: Silksong (PPSA12544), the same engine and studio: #726 (Windows, AMD), #1996 (Windows, NVIDIA), #1519 (Linux). The --module-dir handling of the Unity plugins in Media/Plugins (#846) and the shader-register stop (#1836) those threads list are both on main, so this title does not need them on top.