v0.6.0 - MGPU Bridge, Lower Latency and Stable Frame Generation 2x
Release v0.6.0 of the Neural-coprocessor MGPU Bridge, a ReShade add-on that runs DLSS Neural Rendering on a second GPU while the first renders the game.
New in 0.6.0
Improved camera responsiveness and even frame pacing. The camera responds much faster, and frames are shown more evenly across all hardware even at lower framerates. Help the most on 60 Hz displays and games like Elden ring that natively locks its frame rate to 60 FPS.
Improved stability for DLSS Frame Generation. Performance, frame pacing and image stability in motion are significantly improved. Thanks to everyone who uploaded logs. If you still see stutter or flicker, please report it. Turn it on in the panel: DLSS Frame Generation 2x, or set FrameGen=4 in mgpu.ini. The game does not need to support DLSS: Tested it in Skyrim (DirectX 11) and Resident Evil 4 (it has no DLSS). Turn off the game’s own frame generation first.
Dynamic mode keeps frame generation from going over your display's maximum refresh rate. It also helps in games with 30 fps cutscenes. It is off by default. Leave it off on G-Sync or FreeSync displays.
Workaround for the path tracing flicker. Path tracing and Ray Reconstruction add flicker to the neural output. For now, the only workaround is two passes, with the second pass on NVIDIA's full network at native resolution. The Path Tracing button sets this for you. If the flicker does not bother you, or you need the speed of one pass, you can still use one pass until this known issue is fixed.
Experimental frame generation modes. FSR Frame Generation, in the panel. 3x and 4x, only in mgpu.ini: they add much more delay than 2x.
Improved one-button presets. The preset buttons in the panel now give the best result across the games tested for 0.6.0.
VSync is off by default, for lower latency. If you see tearing and your display has no G-Sync or FreeSync, turn on VSync in the panel and restart the game.
Launcher. The same settings and names as the panel.
Upgrading
From 0.5.x: replace the add-on and take the new mgpu.ini. The defaults changed. The launcher's Copy files does it for you and keeps your Dcomp settings.
From 0.4.x: replace the files and take the new mgpu.ini. The launcher's Copy files does it for you and keeps your Dcomp settings. Use nvngx_dlssnr.dll 310.9.16 or newer: older versions run the big network on every pass.
From 0.3.x: replace the files and take the new mgpu.ini. The launcher's Copy files does it for you and keeps your Dcomp settings.
From 0.2.4 or older: replace the files and take the new mgpu.ini. It sets DX11=1 and DcompOverlay=1, and adds DcompMultiDisplay.
From 0.1.0: move nvngx_dlssnr.dll into an mgpu folder beside the add-on, and delete the copy next to the game's exe.
What's in the zip
| file | what it is |
|---|---|
nvngx.dll_mgpu_bridge.addon64
| the add-on |
mgpu.ini
| its settings |
gpu1.ini
| empty ReShade preset for the bridge runtime |
ReShade2.ini
| config for the bridge's own ReShade runtime |
reshade-shaders\Shaders\mgpu_depth_tap.fx
| keeps ReShade's depth bound; required |
README.txt
| install steps and known limitations |
LICENSE
| MIT |
Where it goes
Everything goes in the folder with the game's exe:
Game.exe
dxgi.dll (ReShade, add-on build)
ReShade.ini
ReShadePreset.ini
nvngx.dll_mgpu_bridge.addon64
mgpu.ini
gpu1.ini
ReShade2.ini
mgpu\nvngx_dlssnr.dll (not in this download)
reshade-shaders\Shaders\mgpu_depth_tap.fx
The mgpu folder is the one step you do by hand.
Do not rename the add-on.
Nothing from NVIDIA is included in this download, and none of it may be.
What you need
- Hardware: two RTX 50-series GPUs. One monitor, on the DLSS 5 GPU; the GPU that renders the game is headless. A contributor reported 40-series working.
- ReShade: 6.8.0 or newer, installed with add-on support.
- Game API: DirectX 12 or DirectX 11. Vulkan does nothing.
- Other add-ons: none alongside it.
Before you run it
Do not change the resolution, the DLSS mode or the DLSS preset while the bridge runs. Change them, then restart the game.
Run the launcher's install check first.
The bridge can take a while to arm, and that is normal.
Low FPS? The GPU that runs DLSS 5, or your PCIe bandwidth, may be too low for 3440x1440 or 3840x2160. Try one of these:
- Render the game on the weaker GPU.
- Use Best Performance in the panel.
- Turn on Native upscaling.
- Lower the resolution.
Turn off the game's frame generation. It still flickers, and some games crash at start with it on. Use the bridge's frame generation instead.
Titles this build was run on
| Title | API |
|---|---|
| Cyberpunk 2077 | DirectX 12 |
| Resident Evil 4 | DirectX 12 |
| Rise of the Tomb Raider | DirectX 12 |
| The Blood of Dawnwalker | DirectX 12 |
| DragonSword Awakening | DirectX 12 |
| Skyrim Special Edition | DirectX 11 |
Status
Research code, not a finished product. It creates a second D3D12 device and allocates cross-adapter shared heaps.
SmartScreen and antivirus may flag the unsigned DLL and the launcher. I do not pay for a certificate; you can build both from source.
Provenance
Built by this Actions run.
mgpu_bridge_0.6.0.zip SHA-256: 43ab24c62aea5fc62a525a78cdb285d630951c57a93b647ddcca94c7dbc8494a
mgpu_bridge_launcher_0.6.0.zip SHA-256: de3c7d59d295caaec8250627b31c103c68fafc41bb30a4b26ec239ee3b8a37ab
To check a download, run this in PowerShell in the folder with the zip:
Get-FileHash .\mgpu_bridge_0.6.0.zip -Algorithm SHA256
Get-FileHash .\mgpu_bridge_launcher_0.6.0.zip -Algorithm SHA256
Compare the result with the digest above.