OverkillLabs3/driveclub-recomp

This is a recompilation project: it runs the PS4 version 1.28 code of DriveClub on Windows by reimplementing the console's system libraries rather than emulating hardware. It is worth a look if you still have game dumps and want a modern-PC path to a last-generation racer.

The problem

You own a PS4 racing game and want to play it on PC with a wheel, a high-resolution display and a stable frame rate, instead of keeping the console around or settling for streaming. Traditional emulation means configuring a separate emulator, juggling firmware, and accepting translation overhead. Here the developer distributes a Windows build that boots the game directly from your own base-game and update folders, so the workflow is: pick two directories in a launcher, choose graphics settings, and play. The change is that the console layer, not the game code, is replaced.

What's different

Because the game's own x86-64 code executes on the CPU, there is no CPU emulation in the loop; the README describes the PS4 system libraries as reimplemented and GPU commands translated to Vulkan, in the spirit of Wine and DXVK. That design is why the project can bolt on PC graphics features: version 0.2.0 swaps the game's anti-aliasing for NVIDIA DLAA or AMD FSR 3.1, and 0.3.0 adds DLSS and FSR upscaling plus HDR10 output. The launcher also exposes frame-rate modes, including an unlocked VRR option that the README says keeps the game at normal speed, and a benchmark that reports average FPS with 1% and 0.1% lows.

That ambition comes with visible seams. The developer's own known-issues list admits some reflections are too bright, fast cars leave a faint anti-aliasing trail because cars lack motion data, and online features do not work at all. The README's performance figure — roughly 60 FPS at 4K in the heaviest scenes — comes from one test machine (RTX 5070 Ti, Ryzen 7 5800X3D) and is a claim, not an independent measurement. It also notes the processor becomes the limit in heavy scenes, so stronger GPUs alone will not fix everything.

Who should try it

This fits a Windows player who already has DriveClub base-game and 1.28 update dumps, owns a wheel or gamepad, and is comfortable pointing a launcher at folders and tuning quality presets. The documented gamepad, keyboard and wheel support, including separate shifters and handbrakes, makes it a reasonable fit for a sim-racing setup. It is a poor fit for anyone without those dumps, since the project supplies no game data, and for anyone who wants online play, which the README says does not work. Players who need a polished, issue-free picture may also be put off by the acknowledged reflection and anti-aliasing artifacts.

Requirements and limitations

First, you must supply your own version 1.28 update folder containing eboot.bin and a base-game folder containing game000.dat; the download alone is not playable. Second, extract the build somewhere writable rather than Program Files. On the hardware side, Vulkan-capable NVIDIA, AMD or Intel graphics are required, with DLSS features limited to GeForce RTX cards while FSR 3.1 works on any card. Expect first-run shader compilation stutter that fades as shaders are cached, and CPU-bound frame drops in dense scenes.

The how-to-play instructions and the releases page are the places to check version notes. The project is GPL-2.0 and explicitly unaffiliated with the game's rights holders, so legal use depends on owning the game.

HotRepo's take

HotRepo first recorded this repository on 2026-10-24, when it was 8 days old, and logged 683 total stars with a #5 position on the cpp NEW-REPOSITORY board on 2026-10-25. That board rank is not an overall Trending position and is not a daily growth figure. With only a two-date sample and no comparable daily-board history, persistence of interest cannot yet be judged. Before investing time, verify that your dumps match the 1.28 update the README targets, since version mismatch is the first thing that would block a working launch.