Solo dev's Zig-based PS5PCEM boots PS5 titles on Windows via Vulkan

A new experimental PS5 emulator called PS5PCEM, written in Zig, gets several titles to gameplay by translating RDNA2 shaders to Vulkan on Windows.

AI-drafted from 2 sources. This story was written with AI from the outside reporting listed under Sources, and checked by automated tools before it went up. The originals have the full detail.

A solo developer has published PS5PCEM, an experimental PlayStation 5 emulator and “interoperability research” project written in the Zig programming language, and a first prototype already gets several commercial titles as far as playable gameplay on Windows. The project, credited to Artur Strazewicz, appeared on GitHub and was picked up by a thread on r/emulation.

PlayStation 5 emulation has lagged well behind other consoles because of the sheer complexity of Sony's custom silicon: an AMD RDNA2 graphics core wired into a bespoke command interface called AGC, wrapped in encrypted firmware and signed executables. Cracking that open on a PC means faking or reimplementing the parts of the operating system a game expects to talk to, then translating GPU instructions written for RDNA2 hardware into something a Windows graphics driver understands.

What PS5PCEM actually does

According to the project's GitHub page, PS5PCEM runs PS5 guest code natively on x86-64 Windows machines, handling ELF and SELF loading (the PS5's executable formats), relocation, module linking, thread-local storage, and what it calls firmware “HLE”, short for high-level emulation, where the console's system calls are reimplemented in software rather than run as original code. On the graphics side, it describes a “stateful AGC command-stream” engine and a “growing RDNA2-to-SPIR-V shader pipeline”, SPIR-V being the intermediate format Vulkan uses for shaders. That pipeline feeds a Vulkan renderer with resident render targets, texture detiling, depth and stencil support, and multisample anti-aliasing.

The prototype also ships a native Windows launcher with a game library view, local cover art pulled from each title's own icon file, per-title save data, DualSense and DualShock controller detection, and a Vulkan capability check that names the graphics device it finds before a game is started. The current build, labelled 0.3.1-beta.1, needs Windows 10 2004 or newer and a Vulkan 1.2-capable driver. It is unsigned, so Windows may flag it with a SmartScreen warning.

What actually runs, and how well

The GitHub page lists a handful of titles reaching gameplay: Cat Quest III, Jets 'n' Guns 2, Asterix & Obelix: Slap Them All!, The Precinct, and Dreaming Sarah are all shown with the game running rather than just a menu. Ghost of Yōtei gets further than most in one sense, its intro video decodes and plays, but a loaded 3D scene is logged at 0.6 frames per second, which the project itself flags as “not playable yet”. REANIMAL reaches an animated title menu with, by the developer's own admission, incomplete option labels. None of this is being claimed as finished emulation; the project's own status page is the source for all of it, and it stresses that compatibility, performance, graphics, audio and stability “vary by title and hardware”.

Why this matters, and what is still murky

For preservation-minded readers, another independent route into PS5 hardware is worth tracking regardless of how far it gets, because software emulation projects for current-generation consoles are rare and PS5 has had essentially none with public code so far. The project is licensed under GPLv3 and its author states plainly that it ships no games, firmware, system libraries or keys, and that users need a decrypted title they are “legally entitled to use”, language that leaves the actual mechanics of obtaining such a file unaddressed. It is also, right now, a one-person, five-star repository with a single contributor, so how far it scales, how it handles anti-piracy protections in real PS5 titles, and whether the RDNA2 shader translation holds up outside these early demos are all open questions the compatibility list and the developer's own documentation will need to answer over time.

Sources

Image: GitHub