AnyPS5's 100% GPU coverage figure counts instructions its shader decoder recognizes

A PS5 shader goes through several stages in AnyPS5 before anything reaches the screen. PS5 games target Sony's proprietary AGC graphics interface and ship AMD RDNA-specific shader instructions ^[4]. AnyPS5 reimplements the graphics behavior, translates the RDNA shader programs into SPIR-V and executes them through Vulkan ^[4].

The 100% figure covers the first of those stages. On the tracker, "implemented" means the shader decoder recognizes an instruction ^[2]. Recognition tells the translator which instruction it has. According to Tom's Hardware, it does not necessarily mean the instruction is translated to SPIR-V, behaves correctly in every situation, or renders properly inside a game's shaders ^[2]. Tom's Hardware called this "a fairly important asterisk" ^[9].

Both tracker percentages are fractions of lists the project defines. The 1,166 instructions are its tracked RDNA 1 and RDNA 2 set ^[1]. The library figure is 2,578 of the 3,044 functions currently declared in the codebase ^[15]. That leaves 466 declared functions unimplemented ^[17]. Tom's Hardware notes that 3,044 is not every function in the PS5 firmware, and that an implemented function is not guaranteed to behave as it does on the console ^[16].

The libSceHttp entry shows the distance between a percentage and behavior. The tracker lists the library at 95%, yet the technical-debt document states that no HTTP request reaches the network in the current implementation ^[10]. For a game that talks to a server, that 95% does nothing. We think a project that publishes a debt document contradicting its own dashboard is doing something right ^[10].

The porting design is careful engineering. AnyPS5 keeps and adapts the game's existing machine code ^[3], so the CPU side can generally run directly on a compatible x86-64 host ^[5]. A --to-intel option converts supported AMD-only instructions for Intel processors ^[5]. The open work sits in the GPU and library layers. Graphics state, texture formats, synchronization, memory management, audio and other system services all have to work before a whole game runs ^[8].

The compatibility list moves on a different scale. Developers are bringing up more demanding games, including Ghost of Yotei. The experimental reports on those games still document substantial rendering, stability and performance problems ^[7].

Getting that far takes setup. The documented workflow starts from an already-extracted game ELF, its modules and resources, and a built set of host-side compatibility libraries ^[11]. AnyPS5 is not a disc-ripping or decryption tool ^[11]. On Windows, a title may request up to 13,824 MB of direct memory, and the full allocation is charged against the system commit limit immediately ^[12].