OverkillLabs3/driveclub-recomp

DriveClub for PS4 (version 1.28), running natively on Windows.

The source code is in this repository and the build is on the Releases page.

The game's own anti-aliasing is replaced by a modern one, chosen in the launcher:

• NVIDIA DLAA (GeForce RTX) for the sharpest, steadiest picture: thin lines, wires, fences and foliage stay clean.
• AMD FSR 3.1 on any graphics card, with no special hardware and nothing extra to install.

Both work at the native resolution and use the game's own camera motion. In the game the overlay shows what is active, F9 switches the new anti-aliasing off and on to compare, and F10 switches between FSR and DLSS on RTX cards.

1. Download the latest driveclub-recomp-<version>-win64.zip from the Releases page and extract it anywhere you can write to (not Program Files).
2. Have your own game dumps ready:
   • the version 1.28 update folder (it contains eboot.bin)
   • the base game folder (it contains game000.dat)
3. 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.

• 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
• 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)
• 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 mods folder for loose-file mods: files in it replace the game's own files of the same path

Any gamepad works. Keyboard, mouse and gamepad can be used at the same time.

F7 turns mouse look on or off. F9 and F10 are the anti-aliasing keys above. The bindings are in data\user\input_config\default.ini and can be changed there.

The window that opens when you start DriveClub.exe has every setting. Press Play to save them; they are kept for later starts.

Performance preset: Handheld, Low, Medium, High or Ultra pick the render and output sizes for your PC. You can still change each size afterwards.

Frame rate: 30, 60 (deltatime), 60 with a fixed tick, or Unlocked. Unlocked has no frame cap and the game keeps its normal speed.

Resolution: output from 720p to 8K, render size from 720p to 8K, and ultrawide sizes with a field-of-view fix. Sizes above 1080p use more memory; the needed memory patch is added for you.

Mirror and reflection updates: Live (default) draws the small scene of mirrors, rain and reflections every frame. Static (faster) draws it once and keeps that picture, which is much faster but stops reflections and rain on the glass from updating. The Handheld preset uses it.

Anti-aliasing: Game keeps the original. FSR 3.1 works on any graphics card, DLAA (RTX) needs a GeForce RTX card; if it is not available the launcher falls back to FSR. Do not turn on the community patch "Disable motion blur and depth of field" with it: they do not work together and the game keeps its own anti-aliasing then.

Anisotropic filtering: keeps textures on roads and terrain sharp at a shallow angle. Automatic is 16x (4x on integrated graphics); you can also choose Off, 2x, 4x, 8x or 16x.

Unlock DLC content: off by default. Unlocks the add-on cars, bikes, tours and livery decals. The launcher reads the vehicle list, the tour list and the livery list from your own game archive and builds changed copies that the game uses. Your game folders are not modified.

Gameplay: player name, borderless fullscreen, FPS counter, motion blur and depth of field off, no reset-to-track timer, no track barriers, and photo mode options.

Skip the hardware check: the launcher checks that your processor and graphics card can run the game (a processor with AVX, BMI1, LZCNT and MOVBE, and Vulkan 1.3). If it ever refuses hardware that works, turn this on to start anyway.

• Some reflections are too bright, for example rain drops on the side window and the paint on cars on the stage select screen.
• Anti-aliasing: fast cars can leave a faint trail, because cars have no motion data of their own yet.
• Static (faster) stops reflections and rain on the glass from updating.
• The processor is the limit. Heavy scenes (many cars, trees and rain) drop frames first on slower CPUs.
• First play builds shaders: short stutters in the first minutes until they are cached. This gets better on later runs.
• Online features do not work.
• Tested on an NVIDIA graphics card only. AMD and Intel are untested; reports from AMD and Intel players are welcome.

• You must supply your own, legally obtained dump of the game. No game files are included.
• Tested with: DriveClub, title ID CUSA00093, version 1.28. The European release (CUSA00003) version 1.28 is accepted too and has been played less. Other versions and repacked dumps have not been tested and may not work.
• SmartScreen may warn (More info, then Run anyway). Verify with the checksum.
• Requires Windows 10/11 64-bit, a processor from Intel Haswell (2013) or AMD Excavator or Ryzen onward, and a graphics card with a Vulkan 1.3 driver. About 40 GB of free space is needed for the game dumps.

See BUILDING.md.

Open an issue and fill in the form. Attach the log files: without them an issue usually cannot be solved. In the folder next to DriveClub.exe, open logs and drag these into the issue:

• the newest driveclub_<date>_<time>.log (one per start: take the one from the run that went wrong). It starts with your Windows, processor, graphics card, driver and launcher choices, and has a status line every 30 seconds, so nothing else is needed from you.
• launcher.log: what the launcher saw. It exists even when the game never started, for example when the launcher shows an error.
• any crash_*.dmp: a small file written when the game crashes.

Also say what you were doing when it happened (menu, loading, which event and car).

The community patches for DriveClub are by Kravickas, TonySSS, ZipperedRain, kalaposfos, squidbus, illusion and u/Charlie_Muggins.

Also used: SDL3 and FFmpeg.

GNU General Public License version 2 or later (LICENSE). Parts of the code derive from other GPL projects and keep their original notices in the source files. Third-party components keep their own licenses (THIRD_PARTY_NOTICES.txt).

DriveClub is a trademark and copyright of its respective owners; this project is not affiliated with or endorsed by them.