Devil May Cry 5 Special Edition (PPSA01442)

[JustUseAI]

Existing thread

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

Title

Devil May Cry 5 Special Edition (PPSA01442)

Content version tested

01.002.000

AnyPS5 commit

main 6239cef plus local changes (described below; not yet a pull request)

System tested

Windows 10 22H2 (19045), RTX 4070 SUPER (NVIDIA 616.92), self-built with WinLibs GCC 15.2

Furthest point

In game

What is shown

Boots through the network dialog and title screen to Continue, loads the save and reaches gameplay (Mission 2 area and the prologue). The deferred-lit scene renders correctly, including the console's ray-traced reflections pass (BVH traversal via image_bvh64_intersect_ray). Frame rate in game is about 0.05-0.3 FPS, so it is not playable. Missing: parts of Nero's face and the Overture arm (tessellated draws that are skipped, see blocker). Audio and input were not evaluated.

Current blocker

1. Performance (sub-1 FPS in game).
2. Unsupported tessellation configurations: about 10 programs are not prepared ("not affine" / "not preparing a registered tessellation"); run with APS5_SKIP_UNSUPPORTED_TESS=1, so those draws are missing.
3. Local change still needed for correct lighting (without it near surfaces are unlit): depth decompress-to-copy. The title decompresses depth with DB_RENDER_CONTROL bit 0x40 (DEPTH_COMPRESS_DISABLE), no depth tests and Z_READ_BASE != Z_WRITE_BASE; the lighting pass then samples the Z_WRITE copy. The local fix records the copy (write address -> read address, same size) in State.cpp DecodeState and resolves textures bound at the copy address to the live depth surface in GuestTextureResource. Planned as a pull request once it is generalised (it currently uses the live depth surface instead of a snapshot).

How it was run

APS5_THREAD_PRIORITY=off
APS5_SKIP_UNSUPPORTED_TESS=1
APS5_DISPATCH_CACHE_ENTRIES=65536
APS5_BDA_TABLE_CACHE_ENTRIES=64
APS5_ADDRESS_COPY_MAX_MIB=1024        (without it: FATAL, an address-based build copies 488 MiB past the 64 MiB limit)
APS5_DISPATCH_CACHE_BYTES=1073741824

First boot builds a large shader cache (~68 GB here) and loading into gameplay took about 15 minutes.

[EagleBearerYS]

@JustUseAI, thanks for the detailed report. Could you post the whole FATAL: an address-based build copies ... past 64 MiB (APS5_ADDRESS_COPY_MAX_MIB); the largest: ... line from a run without APS5_ADDRESS_COPY_MAX_MIB? After "the largest:" it lists up to eight ranges, each with its reason: outside the write-watched arena, image mirror refused, unreadable pages or mirrors disabled by APS5_NO_LEASE_MIRROR. The reasons show where the copies come from, and so which fix applies.

[JustUseAI]

Here's the full line from a run without APS5_ADDRESS_COPY_MAX_MIB set (default 64 MiB limit):

FATAL: an address-based build copies 488 MiB of 1 registered ranges, past 64 MiB (APS5_ADDRESS_COPY_MAX_MIB); the largest: 0x24ec00000+0x1e848000 (488.3 MiB committed, outside the write-watched arena)

So it's a single ~488 MiB range, and the reason is outside the write-watched arena. It's followed by abort() (SIGABRT) with libSceAgcDriver.prx+0x7ce65c and nvoglv64.dll+0xf7c823 among the stack return candidates. With APS5_ADDRESS_COPY_MAX_MIB=1024 the game boots and runs.

[EagleBearerYS]

@JustUseAI, thanks, that helps. When a single 488 MiB range is copied as "outside the write-watched arena", a heap's host import was refused and no mirror could be made for it. Two questions, so we can tell which refusal this was:

1. Which main commit was that run on, and does current main still stop there without APS5_ADDRESS_COPY_MAX_MIB?
2. Before the FATAL, does the log have a [gpu] host import budget: ... refused so far, last 0x... line, or a [gpu] host import of 0x24ec00000+0x1e848000 failed at ... line?

If it's the first (the import budget), we have a fix for that case on a branch: a build retries the import with eviction before it would copy past the cap. Resident Evil Village (PPSA01556) stopped the same way on a 768 MiB heap in our runs. Once the branch is on current main, we can point you to it if you'd like to try it.

[JustUseAI]

No problem, and I’m okay, I just made this since I’m trying to reverse engineer the console ray tracing so I can port it to pc, I posted this since I got the ps5 version working and may as well post my findings.