Notice. Not affiliated with NVIDIA; NVIDIA, DLSS and the NVIDIA logo are NVIDIA Corporation's trademarks. The bundled NVIDIA runtimes are NVIDIA's property, included unmodified as received, research/educational use only, no warranty, use at your own risk.
Warning
NeuralScreen requires the latest NVIDIA driver. Operation with older drivers or unsupported/non-standard configurations is not guaranteed.
Important
Radeon testers wanted. The AMD build lives in a separate repository, NeuralScreen-AMD, and it has not run on a real Radeon yet. Start from native/AMD.md there, and if it does not come up, attach the diagnostic package (Settings -> Program -> Create diagnostic package).
A patch on the v2.1 line from a full audit: every open tracker report and a pass over the whole code. 78 fixes, each with a regression test that fails on v2.1.9. The full list is in CHANGELOG.md; the ones you are most likely to notice are below.
From the tracker
- HDR no longer loses a fifth of the frame rate (#149). The HDR path skipped the early reply and the deferred tail, so it waited on three fences instead of one. Measured on an HDR display: the client's wait went from 4.50 ms to 0.61 ms.
- No "jelly" on a still picture with NVOFA motion (#141). Optical flow ran on frames with no new content and returned up to 22 px of motion on a still window. Such frames now get zero motion.
- No black strip on a captured window on Windows 10 (#140), and a screenshot no longer carries the menu.
- A slow NVIDIA start is no longer read as a missing handshake (#148), and one late acknowledgement no longer delays every later NR toggle by 15 s.
- A driver too old for the neural renderer is named as the reason (#145) instead of a bare "failed".
- An RTSS frame limit inside NeuralScreen is named in the log (#143).
NS_GPU_PRIORITY=high(#142) - an opt-in GPU scheduling priority for the worker, off by default, for machines where a foreground game starves it.
Capture and presentation
- A UAC prompt, the lock screen or Ctrl+Alt+Del no longer restarts the picture. The capture source is kept and reopened with a growing pause; before, three such events turned NR off.
- With Windows HDR on and HDR compatibility off, whites are white again (about 250 of 255 instead of 187).
- A GPU recording of a still picture is smooth again - since v2.1.7 it got about ten frames a second.
- The motion map covers the whole picture at every resolution - at 1366x768 it had dead columns and rows at the right and bottom.
- In window mode the picture keeps up with a window dragged without redrawing, and comes back after a display mode change.
- A crash inside the Frame Generation runtime is caught and FG is switched off for the session, and a failed FG start is undone completely.
Program
- The window keeps answering while the worker starts or restarts, and a worker that fails to start turns NR off instead of closing the program.
- CPU recordings play at real speed, the sound after a quiet stretch is in sync, and the sound follows a change of the default playback device.
- The converter keeps the pixel aspect ratio, PNG transparency and WebP quality.
- Keys typed while the menu is closed are no longer replayed into it; plain letters and arrows are refused as global hotkeys.
- The support bundle carries fewer personal details (converted file names, window titles) and more of the session.
- The release archive no longer ships a pip launcher with the build machine's path.
Tests
Suite: 279 pass, 1 fail, 7 skipped, GUI end-to-end cycle green (v2.1.9: 224 / 6 / 6). The one failure was a timing flaw in a new test, not in the program: on a still desktop its fault came too late for its fixed window; fixed, 3 of 3 green. HDR tests were run on an HDR display.