What's changed
This release is Linux only; the Windows preview stays at 0.0.3.
- Changed: in games the network now runs very close to its speed in the offline benchmark, and for a while
after a game starts NR costs even less than the offline benchmark. DXVK and vkd3d-proton create the
game's Vulkan device with a robustness setting that made the network slower in games; the network's
shaders no longer use it. The picture is unchanged. - Added: int4 mixed, an optional second network that is faster than the default one (table below). Part
of its computation runs in int4, a lower precision than the original network uses, so its picture differs
somewhat from the default network's. The installer asks whether to add it (or pass--int4/--no-int4);
with it, the Steam launch options it prints have two more entries (VK_ADD_LAYER_PATH,
VK_INSTANCE_LAYERS) that int4 mixed needs, so copy the whole line. Ctrl+F11 in game switches between
int4 mixed and the default network. Settings:[Int4Mixed]indlssnr-amd.ini.
With int4 mixed, NR takes much longer to take effect when a game starts. Until then the picture goes
without NR; this does not mean int4 mixed is not working.
The int4 tables (linux/data/int4/) come from this project's own calibration on 1,112 game frames
and darkened copies of some of them. int4 mixed is the network these tables define; another
calibration would give a different network. - Added: several options for how the result is enlarged when Model resolution is below 100% on the ReShade
routes (Enlargement on the add-on page,Transfer/ClassicScalerindlssnr-amd.ini). - Added:
dlssnr-amd.iniis written at install on every route, with every setting and its description.
[Log]turns the log off or keeps the previous one. - Added: the add-on page and
dlssnr-amd.logshow NR's cost split into the network and the route's own work. - Changed: OptiScaler-NR 0.8.91 is bundled (was 0.8.4). The installer sets
[DlssNr] WhitePointSource=1
(the white point from the game's exposure, as 0.8.4 did by default). - Changed: less overhead on the ReShade routes below 100% Model resolution. The picture is unchanged.
- Fixed: DirectX 10 games on the
reshaderoute. - Fixed: 32-bit games at 4K use less memory while the network is built, and NR retries if memory runs out.
- Fixed: bright saturated scRGB (HDR) colours keep their hue.
Offline benchmark, GPU time of the network per frame on an RX 9070 XT:
| 1080p | 1440p | 4K | |
|---|---|---|---|
| Linux | 5.60 ms | 9.70 ms | 21.89 ms |
| Linux, int4 mixed | 4.99 ms | 8.69 ms | 19.64 ms |
In games NR is faster than the offline benchmark while the GPU is still cool: int4 mixed at 1080p in
Dying Light: The Beast started at about 4.8 ms and settled at about 5.1 ms once the GPU was warm.
The time on OptiScaler's DLSS Neural Rendering page is higher than the one in dlssnr-amd.log: the page
times OptiScaler's whole DLSS-NR work, its own passes before and after the network included, and the log
times only this project's part. In our measurement OptiScaler's own passes took 0.12 ms at 1080p and
0.53 ms at 4K.
RX 7000 (RDNA3)
Linux users with an RX 7000 series card may want to try mauri870's
DLSSNR-RDNA3.
Downloads
- Linux, 64-bit games:
DLSSNR-AMD-Vulkan-Linux-0.0.4-x86_64.tar.gz - Linux, 32-bit games:
DLSSNR-AMD-Vulkan-Linux-0.0.4-i686.tar.gz
Full Changelog: v0.0.3...v0.0.4