DriveClub Recomp Wiki / Troubleshooting
DriveClub Recomp troubleshooting
Symptoms matched to the fixes in the release notes, the known issues of the current release, and the reports still open on the tracker.
- 20 fixes
- 13 open reports
- Updated for v0.4.2
Most problems reported on the tracker have been fixed in a later release, so the first step is always to update to v0.4.2 and the newest graphics driver. The table maps symptoms to the release notes and README for each one.
Common errors and fixes
| Symptom | Cause and fix |
|---|---|
| “Windows protected your PC” (SmartScreen) | The launcher is unsigned. Check the SHA-256 on the download page, then More info → Run anyway. |
The game closes at once with exception 0xc000001d | The processor lacks AVX, BMI1, LZCNT or MOVBE. Since 0.2.2 the launcher names what is missing; the CPU cannot run the port. |
| “The update folder must be DriveClub version 1.28” | The update folder is another version or not the update. Choose the folder with the 1.28 eboot.bin; a single-folder 1.28 dump goes in the base field with the update field empty (0.2.0+). |
Launcher names a file such as game961.dat as cut short | Your base dump is incomplete; an incomplete copy used to read forever on a black screen (#48). Replace the dump with a complete one. |
| Crash right after Play, or a few minutes in | Enlarge the Windows page file: since 0.4.2 the log warns when Windows has almost no commit left (#327, #345). Lower the output resolution on 8 GB cards at 4K. |
| Black screen or “device lost” on AMD / Intel | Update to the newest release and driver. Many fixes landed in 0.2.4–0.3.1. If it remains, press Save a bug report and attach bug-report.zip to an issue. |
| Black screen on a laptop | Fixed in 0.4.0 (#284): the launcher and runtime pick the right graphics chip on laptops with two. |
| Game freezes at start | With “Show pedal inputs” on, fixed in 0.4.2 (#333, #346). Overlay programs (Steam, Epic, Discord, OBS) are kept out of the game by default since 0.2.5; keep it that way. |
| Infinite loading after a race or when leaving to the menu | Fixed in 0.3.0 (replay folder listing). Update. |
| Freeze when a career event starts | Fixed in 0.2.4 (lock fix). Update. |
| Stutter in the first minutes | Shaders are being built and cached; it improves on later runs. Some updates rebuild the cache once. |
| Car runs slow or behaves wrongly at high FPS | Stay under about 120 FPS: use Unlocked (VRR) with a frame cap, or cap the driver. |
| Shimmering or smeared cars with DLSS | Fixed in 0.4.2 (#361) and 0.3.2 (#211). Avoid the “Disable motion blur and depth of field” patch with FSR/DLSS: they do not work together. |
| Ghosting with FSR 4.1 on Radeon | Known (#340, #348). Try fsr4_invert_jitter=1 and fsr4_auto_exposure=0 in data\user\driveclub.ini, or use FSR 3.1/4. |
| Car flashes white/black after switching cameras | Fixed in 0.4.2 (#362, reported in #347). |
| Rain or reflections look too bright, or rain on glass stops | Some reflections are too bright (known). Static (faster) reflections stop rain on glass from updating; use Live. |
| Collision penalties, teleporting cars | Turn off the “No reset-to-track timer” and “Disable track barriers” patches; the launcher warns they can cause this (#182, #256). |
| Missing Chinese, Japanese or Korean characters | Fixed in 0.4.2 with a fallback font (#360). |
| Quiet audio on TV, headphones or laptop speakers | Fixed in 0.2.4: 7.1 is downmixed to stereo with a limiter. |
| Launcher does not open or has no text under Wine/Proton | DriveClub.exe opens the classic launcher there; since 0.3.2 it draws text with another font when Segoe UI is missing. |
Known issues in v0.4.2
- Some reflections are too bright, for example rain drops on the side window and car paint on the stage select screen.
- With anti-aliasing, fast cars can leave a faint trail.
- Static (faster) reflections stop reflections and rain on the glass from updating.
- The processor is the limit: heavy scenes with many cars, trees and rain drop frames first on slower CPUs.
- Online play is private (home network or VPN, same version for everyone); a public lobby is being tested on the project’s Discord.
- Mostly tested on NVIDIA. Some AMD and Intel players still report colour glitches or device-lost crashes.
- Above 120 FPS the game can have issues.
Open reports on the tracker
Issues open on github.com/OverkillLabs3/driveclub-recomp/issues among the 30 most recent on November 8, 2026 (92 open issues and pull requests in total). If yours matches, add your log there instead of opening a new one.
| Issue | Title | Opened |
|---|---|---|
| #375 | missing textures and models/objects | November 8, 2026 |
| #374 | Enabling DLSS causes a drop in FPS | November 8, 2026 |
| #365 | Possible regression: Rival "ghosts" get stuck almost at the start during time trial events | November 8, 2026 |
| #364 | Z fighting on certain elements of rear window in many supercars with two-thread enabled | November 8, 2026 |
| #359 | crashes after i press play | November 6, 2026 |
| #357 | DLSS Rendering issues | November 6, 2026 |
| #356 | Telemetry Not Saving | November 5, 2026 |
| #351 | Unlock DLC option missing from Linux launcher | November 4, 2026 |
| #350 | "log wheel prx was no found in a game folder " | November 4, 2026 |
| #349 | Logitech rev LEDs: the game already sends them, `logi_byte_call` drops the value (+ SDL lg4ff on Windows for G27 FFB) | November 3, 2026 |
| #348 | Ghosting with FSR 4.1 | November 3, 2026 |
| #347 | Rendering Issue | November 3, 2026 |
| #346 | The game freezes on boot when 'Show pedal input' option is enabled. | November 3, 2026 |
How to report a problem well
- Update to the newest release and try once more.
- Press Save a bug report (General tab) to make
bug-report.zip: logs, crash dumps and settings, no game files. - Open a new issue with the form at
github.com/OverkillLabs3/driveclub-recomp/issuesand attach the ZIP. - Say what you were doing (menu, loading, which event and car) and your GPU and driver.
Never attach game files, and do not ask for them on the tracker.
Frequently asked questions
What do I attach to a DriveClub Recomp bug report?
Press Save a bug report on the launcher’s General tab: it makes bug-report.zip next to DriveClub.exe with the logs, the newest crash dumps and your settings, and no game files. Drag it into a new issue on GitHub and say what you were doing (menu, loading, which event and car).
Where are the DriveClub Recomp logs?
In the logs folder next to DriveClub.exe: one driveclub_
How do I reset the shader cache?
Close the game and delete data\user\cache. The next start builds it again, with stutter for a few minutes. In 0.3.0 this cured crashes that started on the second launch on AMD cards.
The launcher refuses my PC but I think it can run the game. What now?
Turn on Skip the hardware check in the launcher. It skips the processor and Vulkan 1.3 checks; if the CPU really lacks an instruction, the game will still stop with exception 0xc000001d.
How do I restore my saves?
General tab → SAVES → Restore the latest backup. The launcher backs up saves at every start and keeps the last ten. Four save profiles keep separate careers.