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
This is a pre-release for testing. The panel was rebuilt to the new mockup, and this package carries the first fixes from the tracker. It is published as a normal release so everyone can reach it - if something looks wrong, the log next to the program is what helps.
What is new
The panel was redesigned, section by section, to the approved mockup: numbered sections, the value plate on every slider, the tabbed Settings page, the ACTIONS icons, a tighter vertical rhythm. The Frame Generation row is now one control - off / x2 / x3 / x4 - with no separate switch, so one click on a multiplier turns it on.
The generated rate is shown with the rate it is built on (#109). The line reads FG 178 (60.0) instead of two separate readings: two numbers side by side stated both values but not their relation, and the relation is what the pair means. With Frame Generation running alone the single FG reading is unchanged.
Frame limit now says what it counts (#109) - it caps the SOURCE frames the network processes, and Frame Generation rides on top of them. That is why a 60 cap and a 170 counter can both be true, and nothing on screen used to say it. The row carries a hint saying so, in all twelve languages.
Hints wrap and fit their row. The drop-down rendered a hint as one unclipped line while the slider already wrapped, so a real sentence was cut at the panel edge. Both now share one implementation, and the layout reserves the height the wrapped text needs.
Fixes
The first click on the taskbar button opens the menu again. A click on a not-yet-active button arrives as WM_NCACTIVATE(1), which the guard rejected as a duplicate notification - only the second click worked, by a different route. The previous window's state now separates a real click (its window is still alive) from the fallback activation Windows sends when another window is minimised, so the old "menu opens by itself" behaviour stays fixed while the first click works.
The menu no longer disappears with the captured window (one-window mode). The overlay layer was hidden whenever the source window was minimised, taking the menu with it - the taskbar button then looked dead until the source came back. The picture correctly stops when there is nothing to capture; the panel stays.
The menu in a saved screenshot is placed where it is on screen (#107). In one-window mode the panel was composited at the captured frame's coordinates and landed up to 524 px from where the user sees it.
Clicking Screenshot crashed the program. _Pipeline uses __slots__ and two diagnostic fields were never declared, so the first click raised AttributeError. A test now presses every control on every page (94 actions) against the real pipeline, so an undeclared field fails in the suite instead of on a user's first click.
Tests
The suite covers every test in the repository and runs them as one command. Three tests that had drifted out of the run list are back in it, and the new ones are in place: the first taskbar click, the menu with a minimised source, the screenshot panel position, and every control being pressed on the real state object.
Files
neuralscreen-v1.17.0-full.zip- the program. Unpack and runNeuralScreen.exe; everything needed is inside, including the portable runtime.
Known limits in this build, unchanged from before: the network works up to 2560x1440, the overlay is invisible to external recorders, exclusive-fullscreen games are not covered. See the README section "Limits".