A hotfix. If you are on 1.7.0, update - it leaks video memory every time you move a slider.
The card filled up
Every slider step asks the worker to reconfigure, and it answers by releasing the neural feature and creating a new one. The release went to the NGX core while the feature had been created by nvngx_dlssnr.dll - a different implementation, handed a handle it never issued. Nothing was freed.
| video memory after 30 rebuilds | |
|---|---|
| 1.7.0 | +12.6 GB, about 420 MB each |
| 1.7.1 | +1 MB |
On a 16 GB card that is half a minute of sliding, and it took everything else on the card down with it - which is why the crash was never limited to this program (#48).
The worker now also reports its own video memory after every feature build, so a leak of this kind shows in NeuralScreen.log as a number that climbs instead of as "it crashed after a while".
The network and the capture could run on different cards
NS_GPU (the "gpu" key in the config) is a DXGI adapter index, and the neural side always treated it as a wish: an index that is not a usable NVIDIA card falls back to the first one that is. The capture took the same number literally.
On a hybrid laptop adapter 0 is the integrated GPU - and that is the shipped default - so the network ran on the NVIDIA card while the capture was created on the iGPU. The frame cannot cross adapters, so nothing appeared and nothing said why. The reporter found the workaround himself: set "gpu" to 1 (#34). Both now land on the card the network settled on, whatever the config says.
A second monitor could stay blank until you switched away and back
One auto-reset event served every GPU wait in the worker, and a completion registration is not cancelled when a wait returns - so a wait could be woken by somebody else's completion. That was reported as a failure, and the next wait then inherited the next stale signal: the pipeline stayed exactly one step behind and could not recover on its own. In one user's log that was 2766 consecutive timeouts, ending only when a monitor switch tore the pipeline down and rebuilt it (#33).
Also fixed
- A hand-edited config could no longer take the program down silently. Values are validated at load and refused with a message naming the field - the root, the profile, the sizes, the four parameters. Numeric strings and nulls still load, so existing configs are unaffected. Thanks to @tzachbon (#43).
- A crash now brings its traceback to the log. One user's entire account of a failure was
<built-in function get> returned a result with an exception set- which names the messenger, not the cause (#41). - HDR is reported once per session, asked of the display actually being captured. The network is trained on SDR; on an HDR desktop the result reads as "too bright, and the sliders do nothing".
- A card that could not run the neural pass is marked in the picker rather than offered as a second identical-looking line. DXGI reports some cards twice. The mark is dropped the moment that card does work (#33).
- The monitor picker says the picture is not a window you drag - it is a layer over the whole chosen monitor, and the picker is the control people were looking for (#35, #33).
- The desktop rotation is read and logged. Not handled yet: a rotated desktop is duplicated unrotated, so flipped means upside down. The log now says what Windows reports, which is what a fix has to key off (#47).
- Autostart writes a Windows startup entry - the README said nothing was written outside the folder. Thanks to @tzachbon (#44).
The guide
The README is 200 lines down to 158: what belongs in TECHNICAL.md went there, and the four screenshots are one section near the top instead of three. It also describes Boost now, which 1.7.0 added and the guide never mentioned, and states what turned out to be the commonest cause of "it does not start" that is not a bug here: the latest NVIDIA driver and an up-to-date Windows.
Files
neuralscreen-v1.7.1-full.zip- everything inside, unpack and runREADME.md/README.ru.md- the guideTECHNICAL.md/TECHNICAL.ru.md- how it works
Controls
Num2 menu · Num1 NR on/off · Num3 screenshot · Num0 record · Num4/Num6 resolution · Num5 one window · Ctrl+Alt+Q quit