What was done
BlackLineInteractive replaces Sony system libraries and the Liverpool GPU of the PS4 racer with a custom Metal renderer on Intel Macs, and a Windows backend extends the same work. Bring your own decrypted dump.
Driveclub Native brings the PS4 racer to Intel Macs natively, with a separate Windows backend by qnfn that builds ready-to-play releases. Because the console runs x86-64 code, the game own code executes directly: the projects replace the console system libraries and the AMD Liverpool GPU instead of translating CPU code. The repository states the work is for interoperability, preservation and education, with no game files ever distributed.
How it was done
The macOS runtime loads the game eboot, stubs 922 imported functions across 57 Sony libraries, and parses the PM4 command buffers the game writes itself into a GCN shader IR that is compiled straight to Metal 3 shaders without a SPIR-V step. Pipelines cache on disk and up to three frames run in flight so the CPU rarely waits on the GPU. The Windows backend builds on a native PS4 runtime from the bloodborne_pc project and uses the shadPS4 renderer, with frame generation support. Commits on the macOS side carry Co-Authored-By: Claude trailers, so AI agents helped write the code.
Results
The macOS backend targets Driveclub v1.05 on Metal 3 and has been run on a Radeon Pro 5500M; the Windows release targets v1.28 at up to 4K with FSR 3 frame generation and one-click FSR 4.1.1 built on the player own PC from player-supplied files. Both version checks refuse other dumps, nothing proprietary ships, and render accuracy is measured against the console where the work stands. The port is young: macOS in-repo maintenance and the Windows release are separate efforts checked against the same GPU command stream.