DCport 0.4.3 (Windows)

DCport 0.4.3

Download: DCport-0.4.3-windows-fsr.zip (FSR 3.1 / FSR 4 / FSR 4.1.1) or DCport-0.4.3-windows.zip (no FSR). Earlier versions update by themselves (bar at the top: Restart to update).

New: ultrawide monitors (21:9 and 32:9)

• SETUP > Aspect ratio (16:9 / 21:9 / 32:9). At 21:9 or 32:9 the game renders its 3D scene at the full wide size (2560x1080 or 3440x1440 for 21:9, 3840x1080 or 5120x1440 for 32:9), not a stretched 16:9 picture. The camera matches the screen, so cars and wheels keep their real shape.
• SETUP > Field of view applies to every camera, cockpit and chase included. The default is 0.65 (the community wide-FOV value, tested on 32:9). 0.50 is the original 16:9 view. Higher shows more at the sides but stretches the edges more.
• The launcher checks your monitor: on an ultrawide screen it tells you which aspect ratio to pick (main page and SETUP).
• The HUD and menus stay in the middle 16:9 area; videos play pillarboxed.
• In windowed mode the window takes the chosen aspect ratio (for example 720p at 32:9 is 2560x720).

Thanks to @marcelofis for the request (#1) and for testing, and for the 0.65625 field-of-view value. Built after rafidwayne's Driveclub_Widescreen and the wide-scene extension in the Driveclub PC wrapper (both GPL-2.0-or-later); FOV fix value by Kravickas.

Good to know

• An ultrawide picture has more pixels than 1080p (3840x1080 is twice as many), so expect fewer FPS than at 16:9. FSR 3.1 or Off is faster than FSR 4.1.1 there.
• At a wide aspect ratio, Render 4K uses 1440 lines. 5120x1440 is wider than FSR 4.1.1 supports, so FSR 3.1 is used there.

You need your own DRIVECLUB dump (v01.28, EU CUSA00003 or US CUSA00093). No game files are included. Not affiliated with Sony Interactive Entertainment.

DCport 0.4.2 (Windows)

DCport 0.4.2

Download: DCport-0.4.2-windows-fsr.zip (FSR 3.1 / FSR 4 / FSR 4.1.1) or DCport-0.4.2-windows.zip (no FSR). Earlier versions update by themselves (bar at the top: Restart to update).

New

• All cars and bikes (PATCHES > Garage, off by default): turns on the game's own unlockAll option.
• Frame-rate patch moved to SETUP > Frame rate (Deltatime or Fixed tick), next to the frame rate it belongs to.

Improved

• Newer runtime, thanks to shadPS4 and bbport: DCport now builds on bbport 1.9.2 by Supermedo (on deadinside28's native runtime) and its contributors, which includes shadPS4's 0.20.1 GPU code. This brings shadPS4's renderer fixes, bbport's memory fixes for 4–8 GB graphics cards and less CPU time per draw (by emurphy04). Their work, not ours: we merged it with the Driveclub changes. Not all of it is tested with Driveclub yet.
• Fewer stutters in races: the texture cache now follows the graphics card's real memory budget. Before, a 12 GB card started throwing textures out at about 5.5 GB and loaded them again mid-race.
• Threading (SETUP) ran without crashes in our tests. It stays Auto (off) by default; turn it On for more FPS, and set it back to Auto if a race ends in a crash.
• Better crash reports: after a "Device lost", the log names what was at the GPU address that faulted. Please send your log (LOG tab) with any crash.
• Shader fix from shadPS4 (#5365).
• The shader cache is rebuilt once: expect short stutters in your first race.

Tip

Render 1080p gives the best FPS. Above 1080p the resolution patches have visual errors DCport cannot fix (for example broken clouds), and FSR 4.1.1 then runs its larger, slower model.

Known issue: dim picture / flickering light

On some runs the picture stays too dark or the light flickers (most visible when night turns to day); it can also go away by itself. If it stays, restart the game, and if it still happens, send your log (LOG tab).

You need your own DRIVECLUB dump (v01.28, EU CUSA00003 or US CUSA00093). No game files are included. Not affiliated with Sony Interactive Entertainment.

DCport 0.4.0 (Windows)

DCport 0.4.0

Download: DCport-0.4.0-windows-fsr.zip (FSR 3.1 / FSR 4 / FSR 4.1.1) or DCport-0.4.0-windows.zip (no FSR). Earlier versions update by themselves (bar at the top: Restart to update).

Fixed

• The mid-race "Device lost" crash is fixed in testing (RX 6750 XT, RX 9070 XT, Intel CPUs: several races, no crash). Game memory that shaders read through GPU pointers was not allocated as GPU-addressable, so the GPU sometimes read an invalid address.
• About 20 more GPU fixes from shadPS4 and GR2fork, rewritten for DCport: index buffers sized correctly for indirect draws, safe copies between depth formats, CPU/GPU synchronisation, stencil and image-view fixes, clamped GPU math (no Inf/NaN pixels), a command-processor crash and hang, a memory leak in long sessions, an event-queue race.
• The shader cache is rebuilt once: expect short stutters in your first race.

New

• SETUP > Render 1440p / 4K is back, using the game's own resolution setting, so the whole picture renders at that size (no more 1080p square).

⚠ Warning: 1440p / 4K

The resolution patches needed above 1080p have visual errors DCport cannot fix, for example broken clouds in the sky (flat blue shards). 1080p is recommended: it looks best and is the most stable.

Known issue: dim picture / flickering light

On some runs the picture stays too dark or the light flickers (most visible when night turns to day). If it happens, restart the game. If it still happens, send your log (LOG tab). We tried to make it happen again on our side but did not succeed, so your log helps.

You need your own DRIVECLUB dump (v01.28, EU CUSA00003 or US CUSA00093). No game files are included. Not affiliated with Sony Interactive Entertainment.

DCport 0.3.7 (Windows)

Two downloads as before: windows-fsr (FSR 3.1, FSR 4, optional FSR 4.1.1) and windows (no FSR). No game files included: you need your own dump of DRIVECLUB 01.28 (EU CUSA00003 or US CUSA00093).

On 0.3.5 or 0.3.6 you don't need to download anything: the launcher finds this update by itself and offers Restart to update. The game files are prepared again on the first PLAY (about a minute).

Fixes

• "Device lost" right after a car loads: fixed in testing. A pass called "Object motion", inherited from the runtime DCport is built on, ran inside the game's own drawing. DRIVECLUB's FSR doesn't use it (it takes its motion from the game itself), and with it on, newer graphics cards lost the GPU right after a car loaded. It's now off. Threaded recording is also off by default; SETUP > Threading > On turns it back on if your PC runs fine with it.
• Intel CPUs (12th gen and later): random startup crash fixed (Fault: read access to 0 at guest offset 0x64db13). On these CPUs an exception saves more data on the stack, over memory the game was still using. When it prepares the game files, the launcher now finds the affected functions in your own copy of the game and makes them safe. Thanks to jony113, who found and tested it. Nothing changes on AMD CPUs.
• Intel Arc graphics: FSR 3.1 is used, because FSR 4 didn't finish starting on Intel's driver.

Also new

• After a "Device lost" crash, the log also shows the GPU address that faulted, where the driver supports it. Please send the log (LOG tab > Copy for bug report) with any crash.

Known issue

The picture can still flicker or change brightness abruptly at times (most visible at night-to-day transitions). We're working on it.

DCport 0.3.6 (Windows)

Two downloads as before: windows-fsr (FSR 3.1, FSR 4, optional FSR 4.1.1) and windows (no FSR). No game files included: you need your own dump of DRIVECLUB 01.28 (EU CUSA00003 or US CUSA00093).

On 0.3.5 you don't need to download anything: the launcher finds this update by itself and offers Restart to update.

Changes

• Render above 1080p is removed. The community resolution patches (1440p, 1800p, 4K) left part of the game's lighting at 1080p: a square appeared in the top left of the picture, and races lost the GPU ("Device lost") with them. The game now always renders at 1080p. On a 1440p or 4K window or screen, the picture is scaled up with FSR 1 and sharpened (FSR edition); in testing that ran without the crashes the patches caused. If you had Render 1440p or 4K set, you're on 1080p automatically.
• SETUP > Check for updates. Checks at any time. The launcher also checks at every start and downloads new versions in the background.
• Update-only game folders are caught. If the chosen folder is the 01.28 update package alone (eboot.bin but no game.chc), the game used to crash at boot. The launcher now says to copy the update's files over your base game (01.00) folder and choose that folder.

Known issue

Some races can still end with "Device lost" after a few minutes on some PCs (0.3.4 does it too). Please send the log (LOG tab > Copy for bug report).

Updating from 0.3.4 or older by hand: extract to a new folder and copy your user folder (saves), dcport.ini and, if you built it, fsr4_411 across.

DCport 0.3.5 (Windows)

Two downloads as before: windows-fsr (FSR 3.1, FSR 4, optional FSR 4.1.1) and windows (no FSR). No game files included: you need your own dump of DRIVECLUB 01.28 (EU CUSA00003 or US CUSA00093).

Fixes

• Intel CPUs work now. DRIVECLUB uses an instruction only AMD CPUs have (SSE4a EXTRQ, 316 places in the game). On Intel the game closed at the first one. On CPUs without it, the launcher now swaps each one for an equivalent pair of instructions when it prepares the game files. Thanks to jony113, who found it and tested it. AMD CPUs are unchanged.
• No more square in the picture. The community resolution patches above 1080p leave part of the game's lighting at 1080p: a square appears in the top left of the picture, with or without FSR, and some races lose the GPU. Render 1080p is the default and recommended; 1440p and 4K stay in SETUP with a warning.
• On a bigger screen (1440p, 4K), the 1080p picture is now scaled up to it with FSR 1 and sharpened (FSR edition).
• The in-game Output resolution, Preset and Live resolution options are gone. They came from the Bloodborne runtime DCport is built on; changing the output resolution mid-race lost the GPU.

Why there is no Quality / Balanced / Performance mode

FSR in DCport is anti-aliasing, not upscaling, and the launcher and the in-game menu now call it that. FSR 3.1, FSR 4 and FSR 4.1.1 replace DRIVECLUB's own anti-aliasing step (native AA). Everything the game draws after that step (bloom, depth of field, the HUD) stays at 1080p. A Quality or Performance mode would render below that size and upscale, and the rest of the frame would then have to run at the higher size too, which DRIVECLUB doesn't do. So FSR gives a cleaner 1080p picture rather than a different resolution.

Frame generation

Removed because it did not work. And caused Crashes

New

• Automatic updates. From this version on, the launcher checks for a new DCport when it starts, downloads it in the background (checked against GitHub's SHA-256) and shows Restart to update. Only the program files are replaced; your saves, settings, controls, profiles, backups and fsr4_411 stay. You install 0.3.5 by hand this once.
• Language: SETUP > Language lists the languages of your copy (EU: 14 languages; US: English, French, Portuguese (Brazil), Spanish (Latin America)).

Known issue

Some races can still end with "Device lost" after a few minutes on some AMD cards; 0.3.4 does it too. Please send the log (LOG tab > Copy for bug report): it lists the GPU markers.

Updating from 0.3.4 or older: extract to a new folder and copy your user folder (saves), dcport.ini and, if you built it, fsr4_411 across.

See windows/README.md (and README.txt in the zip) for how to play, credits and the legal disclaimer.

DCport 0.3.4 (Windows)

Two downloads as before: windows-fsr (FSR 3.1, FSR 4, frame generation, optional FSR 4.1.1) and windows (no upscaler). No game files included: you need your own dump of DRIVECLUB 01.28 (EU CUSA00003 or US CUSA00093).

Fixes

• Freeze mid-race fixed (the picture stops and the sound loops). Two game threads waited for each other on a lock: on PS4 a thread that already holds a read lock may take it again while another thread waits to write; Windows made it wait, so both waited forever.
• Auto exposure keeps updating in busy scenes. The screen could stay too dark after going from bright to dark until you paused, or lights could flicker.

Frame generation: leave it off

It can lose the GPU ("Device lost") a few minutes into some races. It was removed in 0.3.5 because it did not work.

New

• Player name: SETUP > Game > Player name. The default is "Player".
• GPU markers: after a "Device lost" crash, the log lists which GPU step was running (AMD cards). Please include it in crash reports.
• Frame generation "Image only" (game menu, for testing): frames made from the pictures alone, without the game's depth and motion.

Updating: extract to a new folder and copy your user folder (saves), dcport.ini and, if you built it, fsr4_411 across.

See windows/README.md (and README.txt in the zip) for how to play, credits and the legal disclaimer.

DCport 0.3.3 (Windows) — hotfix

Hotfix for 0.3.2. Two downloads as before: windows-fsr (FSR 3.1, FSR 4, frame generation, optional FSR 4.1.1) and windows (no upscaler). No game files included: you need your own dump of DRIVECLUB 01.28 (EU CUSA00003 or US CUSA00093).

Fixes

• SETUP > Threading now shows the choice you click. In 0.3.2 the setting was saved, but the switch kept showing Auto.
• The in-game Motion blur checkbox is gone. It did not change the blur. To turn motion blur off, use PATCHES > "No motion blur or depth of field".

About motion blur at high frame rates

DriveClub's blur covers the movement between two frames, so above 30 FPS it looks weaker (at 120 FPS about a quarter as long). Nothing is broken: 30 FPS shows the original look.

Updating: extract to a new folder and copy your user folder (saves), dcport.ini and, if you built it, fsr4_411 across.

See windows/README.md (and README.txt in the zip) for how to play, credits and the legal disclaimer.

DCport 0.3.2 (Windows) — hotfix

Hotfix for 0.3.1. Two downloads as before: windows-fsr (FSR 3.1, FSR 4, frame generation, optional FSR 4.1.1) and windows (no upscaler). No game files included: you need your own dump of DRIVECLUB 01.28 (EU CUSA00003 or US CUSA00093).

Fixes

• Crash at 4K / high memory use fixed. Seen on an RTX 3080 (10 GB) at 4K within about a minute ("FreeDeferred on an allocation that is not held"): two of DCport's threads used the same list without a lock.
• AMD Radeon RX 6000 mid-race crashes ("Device lost", or an error in amdvlk64.dll): new SETUP > Threading option (Auto / On / Off).
  • Auto (default): off on AMD RX 6000 and older, which run fine without it (tested on an RX 6750 XT: no crashes, smooth 60 FPS); on for other cards (NVIDIA, newer AMD).
  • Please test both: if the game crashes, try Off; if it runs fine, try On for more FPS, and let us know how it goes on your card.

Updating: extract to a new folder and copy your user folder (saves), dcport.ini and, if you built it, fsr4_411 across.

See windows/README.md (and README.txt in the zip) for how to play, credits and the legal disclaimer.

DCport 0.3.1 (Windows) — hotfix

Hotfix for 0.3.0. Two downloads as before: windows-fsr (FSR 3.1, FSR 4, frame generation, optional FSR 4.1.1) and windows (no upscaler). No game files included: you need your own dump of DRIVECLUB 01.28 (EU CUSA00003 or US CUSA00093).

Fixes

• US copies work without the warning. The launcher said "Game CUSA00093 v01.28: patches need 1.28" for the US release. It only accepted the EU title ID; the patches were applied anyway. Both regions now show as ready, and versions show as on the PS4 (01.28).
• Saves across regions: if your region has no save folder yet, the game uses the other region's saves. Nothing is moved or deleted.
• Settings: saving from the in-game menu no longer drops launcher settings from dcport.ini.
• FSR messages: when FSR 4 / 4.1.1 can't run, the game uses FSR 3.1 and the menu says why (e.g. "set it up in the launcher: SETUP, Set up FSR 4.1.1").

Updating from 0.3.0: extract to a new folder and copy your user folder (saves) and dcport.ini across, or extract over 0.3.0.

See windows/README.md (and README.txt in the zip) for how to play, credits and the legal disclaimer.