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

Two defaults changed, and a day of fixes - three of them cases where the
program looked broken and never said why.

Different out of the box

Boost is on. It shipped off because it had only been measured on still
frames, and that caution outlived its reason: on a 5070 Ti at 4K it is
45.7 → 72.6 frames for a picture indistinguishable at 1:1 - the
network's result is composed onto your native frame, so text and edges keep
full resolution. The switch is still there to compare.
Every profile's Local tone is half a point lower. That slider lifts
shadows and flattens contrast, and it was doing more of it than the picture
wanted, most of all on dark scenes.

The overlay invisible, the effect firing for a second at a time (#61).
Something else in the worker's process printed into its stdout, which
carries the binary protocol - four bytes of a log line, and every handshake
after it timed out while the worker's own log said OK to each one. The
protocol now has a private handle: anyone else's printing goes to the log.
A black screen at 10-bit colour depth (#58). Switching the output to
10bpc makes the capture hand back one FP16 frame, and the code read "HDR"
off that format alone - putting the whole picture on the scRGB path with
HDR compatibility switched off. Reproduced here by switching the depth by
hand, fixed, and verified the same way. A fresh start at 10bpc was always
fine; the transition was not.
Alerts appeared inside the captured window. They belong at the top of
the screen in either mode, and now they are there.
"The window cannot be captured" repeating every half second when a
window collapsed below the size that can be processed.
A flipped display is turned back over (#47). 180° only; 90 and 270 swap
the width and height and still say so in the log.
The Spout bridge built its device on the default card rather than the
one the worker runs on - a cross-GPU copy every frame for anyone using
NS_GPU.
A recording had a hole where a window resize was: the frame that asked
for pixels inside the capture's dry spell came back empty.

A window resize reconfigures the worker instead of replacing it:
1.845 s → 0.112 s, and no veil, because nothing dies. Every fullscreen
toggle in a captured window was costing the longer one.
Boost gets the deferred fence wait too - one wait per frame instead of
three, in the mode where frames are cheapest and most numerous.
The settings page lost two holes of padding at the bottom.

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