Skip to content

0.0.3-31-g238c3a3

Choose a tag to compare

@mauri870 mauri870 released this 03 Oct 19:00
· 62 commits to rdna3 since this release
238c3a3

The OptiScaler route works on RDNA3. Games that offer DLSS, FSR or XeSS and go through OptiScaler
showed a green tint with a flickering bottom edge, froze the GPU a second after NR was enabled, or ran NR
with no visible change. The cause was in how the in-place path read the game's images: it bound the wrong
buffers on RDNA3, so the network read and wrote its data in the wrong format and overwrote its own
counters. All three symptoms were that one bug. It is fixed, and a regression test now covers it.
Checked in Mount & Blade II: Bannerlord (no green tint, no freeze; NR before the upscaler takes 16.3 ms at a
1080p render resolution, about 40 fps with FSR 4.1.1 Performance at 4K output).

Better quality at lower model resolution. A network run below the frame's size makes an edit that is
too strong. It is now scaled by a fitted gain. Score against NVIDIA's full-resolution output at 4K:

Model resolution Before Now
75 % 38.4 dB 39.4 dB
50 % 32.9 dB 35.3 dB
37.5 % 30.9 dB 33.8 dB
25 % 29.2 dB 32.7 dB

No change in speed, and nothing changes at 100 %.

Speed (RX 7900 XTX, network only)

1080p 1440p 4K
100 % model resolution 16 ms 27 ms 58 ms

Native 4K at 100 % is about 15 fps whatever the game is. NR before the upscaler (OptiScaler's "Generate model before upscale") makes its cost follow the render resolution.