perseval-BLR/DLSS5-NeuralScreen v1.8.1 on GitHub

Fixes and speed. No new features. If you are on 1.8.0, update.

Fixed

The screen flickered on every cursor move (#58). 1.8.0 put a
SetColorSpace1 into the ordinary present path - a call this program had
never made. It runs only with HDR compatibility on now; with the switch off
the present path is what 1.7.x had. Reported on an ASUS ROG STRIX G16 with
an external monitor.
The processed picture could sit behind a focused fullscreen game while
the HUD stayed on top. The picture is raised first, the HUD last. Thanks to
@tzachbon (#52).
Dead links in TECHNICAL.md / TECHNICAL.ru.md and the HDR links in
both READMEs, which were broken in every unpacked copy.

Moving a slider no longer rebuilds the neural feature. Every step used
to drain the GPU, release the feature and build it again - 113-148 ms of
frozen picture. The parameters were always applied per frame; only the
sizes need a feature. Measured at 0 ms.
A mode switch is half as long: 1.845 s -> 0.972 s. A rebuild was paying
the 120-frame cold-start warm-up, which exists for the launch on a cold
card, not for a pipeline that has been running.
One fence wait per frame instead of three. Upload, evaluate and present
go on one queue in order; the frame now ends on the presentation fence
alone. 2.1-3.4% throughput, p95 acquisition-to-present 9.80 -> 9.64 ms.
Thanks to @tzachbon (#59).
A window resize of a pixel or two no longer rebuilds anything. Two
numbers describe one window and they disagree by a border on Windows 10.

Every long switch shows a full-screen veil with an animated mark
instead of a spinner, and it no longer slides off the desktop on a
window-mode switch.
NS_PHASE=1 reports where the frame goes - submit, CPU wait, GPU time
and queue gap per stage. On a 5070 Ti over moving video: the network is
8.9 ms of GPU, everything else we own is 0.13 ms together.

Num2 menu · Num1 NR on/off · Num3 screenshot · Num0 record · Num4/Num6 resolution · Num5 one window · Ctrl+Alt+Q quit