DriveClub Recomp
DriveClub for PS4 (version 1.28), running natively on Windows and Linux.
The source code is in this repository and the build is on the Releases page.
Planned for the next major release
- DLSS/FSR Frame Generation, DLSS up to 4X, FSR up to 2X
- Public online lobby (being tested on our Discord first)
- Further performance and stability improvements
How to play
- Download the latest
driveclub-recomp-<version>-win64.zip from the Releases page and extract it anywhere you can write to (not Program Files).
- Have your own game dumps ready:
- the version 1.28 update folder (it contains
eboot.bin)
- the base game folder (it contains
game000.dat)
- Double-click
DriveClub.exe, press Browse next to each folder, check the settings and press Play.
Nothing to install. Your own files are never modified or copied, and the folders you chose are remembered.
Logs are in the logs folder.
Linux (x86_64)
The AppImage is built by the AppImage workflow, or locally with
bash packaging/appimage/build-appimage.sh <version> (see BUILDING.md).
It uses the same game dumps and keeps its settings, prepared image, saves and logs in a
data/ folder beside the AppImage whenever that folder is writable (otherwise in
~/.local/share/driveclub-recomp). Running the AppImage opens the native Linux launcher, with
the same game folders, display, driving and patch settings as the Windows launcher. Press
PLAY there and the recomp prepares and starts; --play starts it headlessly with the saved
settings. Use DATA FOLDER > Change... in the launcher to select another folder or move the
existing data. Put update/ and base/ next to the AppImage, use --setup UPDATE BASE once,
or set DRIVECLUB_UPDATE_DIR and DRIVECLUB_BASE_DIR. The choice is stored in data-path
beside the AppImage; DRIVECLUB_DATA_DIR overrides it, and a portable marker selects data/
when no folder has been chosen.
Highlights
- The game's own x86-64 code runs directly on your CPU, with no CPU emulation. The PS4 system libraries are reimplemented and the GPU commands are translated to Vulkan, similar to Wine and DXVK
- Playable from the menus through races, photo mode and saves, with trophies and multiplayer: private sessions with friends, and a public lobby that is being tested on our Discord
- About 60 FPS at 4K in the heaviest scenes on our test PC (RTX 5070 Ti, Ryzen 7 5800X3D), higher in lighter ones, with an unlocked frame rate option in the launcher that keeps the game at its normal speed
- Runs on NVIDIA, AMD and Intel graphics through Vulkan, with Resizable BAR used automatically where the driver allows it
- Keyboard racing layout and any gamepad (Xbox, PlayStation, Switch Pro, 8BitDo)
- Steering wheels with force feedback from the car's tyre physics, pedals with clutch, an H-pattern shifter and a USB handbrake
- DLC content (add-on cars, bikes, tours and livery decals) can be unlocked from the launcher, built from your own game files. Cars you earn by playing still unlock through normal progression
- A launcher window that resizes from every edge and corner and stays sharp at any display scale
- A modkit (
dcmod), in the modkit branch, with a Mods page in the launcher: change tables, cars, tracks, textures, shaders, sound and Lua scripts, or write graphics filters on the HDR picture. See Modkit and Making mods
Modkit: mod the game
DriveClub Recomp has dcmod, a modkit for the game's own files. It is in the modkit branch and is not part of the downloads yet: build it from that branch. The branch has the documentation (docs/modding), ready-made examples and a Blender add-on. A mod is a folder with a mod.json, replacement files and small patches. Patches are applied to your own copy of the game data, so a mod contains none of the game's data, and several mods can change the same file as long as they change different things. The Mods page of the launcher imports, orders, switches on and off, and sets up mods.
- Tables, text and settings: vehicle and track tables, language files, camera files, graphics settings and XML data.
- Cars and tracks: give a car another car's model, make a car under a new name with its own model files and physics row, or copy a track under a new name. Export car and track models to glTF, edit them in Blender and import them back.
- Textures, shaders and sound: convert textures to and from DDS and PNG, dump the game's shaders and replace them, replace a sound with your own WAV or music and choose what an event plays.
- Lua scripts: run your own scripts in the game with live car data (speed, gears, tyre forces, position), the cars of the race, the camera and the sun, your own HUD, panels with buttons and sliders over the game, the time of day and the weather, and settings that stay between runs.
- Graphics mods: write a shader that runs on the finished picture or on the linear HDR picture before the game's own tone mapping, with the scene depth, motion and the sun available. No filter is installed by default, so the game looks as it always did until you add one. Example filters (a sky with clouds, volumetric fog, ambient occlusion, light shafts, a wet road, tone mapping, bloom, colour grading) are in the
modkit branch under tools/modkit/examples.
- Plugins and agents: native DLL plugins can hook the game's code (opt-in), and
dcmod mcp lets an AI agent browse the game files and make mods.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
