mrkeyoor.comAsk

perseval-BLR/DLSS5-NeuralScreentested 02 Oct 2026commit e7dd41d

NeuralScreen review

NeuralScreen is worth considering as a noncommercial Windows experiment if whole-desktop or one-window NVIDIA processing is your goal and the README's hardware limits fit your machine.

  • Install 13 s
  • Build 5 s
49/225passed, run exited non-zero
  • 35 packages
AI Toolsevaluationupdated 25 Oct 2026
+93stars / 7d

NeuralScreen is a Windows desktop overlay for NVIDIA neural rendering and optional frame generation over a whole display or one window. The README documents screenshots, processed recording and Spout2 output. Our recorded Debian run checked repository commands at commit e7dd41d, not Windows rendering quality or GPU compatibility.

Verdict

NeuralScreen is worth considering as a noncommercial Windows experiment if whole-desktop or one-window NVIDIA processing is your goal and the README's hardware limits fit your machine. Our October 2, 2026 run at e7dd41d recorded successful install and build-labelled commands, followed by a pytest command that exited with errors on Debian. It provides no Windows rendering, frame-pacing or installed-executable verification. Check the intended release, GPU support and runtime notices before trying it, then compare real motion and text with frame generation initially off.

We ran it

Lab card: what happened when we ran NeuralScreen
Lab card from our sandbox run
Screenshot of NeuralScreen (youtu.be/TNDkG8KPf5w)
youtu.be/TNDkG8KPf5w
Install✓ · 13s35 packages · 37 MB
Build✓ · 5s
Tests✗ · 19s49 passed · 0 failed · 176 errors of 225 (pytest)
Known vulns0(pip-audit)
Repo380 files~97,905 lines of source · 12.5 MB · 0 CI workflows · tests dir

Answers from our run

Does NeuralScreen build from source?

Dependencies installed in 13 seconds (35 packages), and the build succeeded in 5 seconds. We cloned commit e7dd41d into a clean Debian container with 3 CPUs and no project-specific setup.

Do NeuralScreen's tests pass?

No. The project's own test command finished in 19 seconds and reported 49 passed, 0 failed, 176 collection errors (pytest).

Does NeuralScreen have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use NeuralScreen?

Competitive online players: the README explicitly advises against this use because of anti-cheat risk.

What are the alternatives to NeuralScreen?

Magpie, OptiScaler. NeuralScreen is worth considering as a noncommercial Windows experiment if whole-desktop or one-window NVIDIA processing is your goal and the README's hardware limits fit your machine.

Setup2/5The README documents a portable archive with Python included, but also an unsigned executable and specific Windows, driver and RTX requirements. Our run did not verify Windows setup.
Docs3/5The supplied documentation explains setup, compatibility labels, capture and limitations. Current README details differ from the historical v2.1.9 material, requiring version-specific reading.
Community2/5The supplied public tracker and release discussion show participation, but do not establish adoption, support response times or resolution quality. The rating reflects limited evidence, not a measured community size.
Maturity2/5A v2.1.9 release is documented, but the README labels Windows 10, hybrid and multi-GPU configurations experimental and some RTX paths unverified or failing. No native acceptance run was supplied.

Who it’s for

Windows users considering a personal, noncommercial desktop-rendering experiment on hardware covered by the README's compatibility matrix.
Tinkerers willing to check an unsigned release, inspect diagnostic logs and compare processed output with the original.
Users interested in the documented one-window capture, processed recording or OBS output through Spout2.

Who it’s NOT for

Competitive online players: the README explicitly advises against this use because of anti-cheat risk.
Users requiring Linux or macOS operation; the documented application targets Windows.
RTX 20 or RTX 30 owners expecting frame generation: the README marks that path as a known failure below Ada. RTX 30 neural rendering remains unverified.
Teams requiring commercial deployment or redistribution without reviewing the source license and separate NVIDIA runtime notices.
Users who need independently verified Windows performance or broad GPU compatibility from this review. Our run measured neither.

Setup reality

In our recorded run on October 2, 2026 at 05:47:14.250 UTC, commit e7dd41d797123a538c8a1d69af3d908c0c1c2772 ran in a Debian Bookworm sandbox configured with 3 CPUs and 8 GB of memory. The install step exited successfully in 13 seconds, with 35 dependencies and 37 MB recorded. The build-labelled step exited successfully in 5 seconds, but its stored output tail is empty. These observations do not establish that a Windows executable was compiled, installed or launched.

The test command exited with code 1 after 19 seconds. The stored pytest summary reports 49 passed, 176 errors and 32 passing subtests; the parser records 0 failed assertions. The tail includes AttributeError: module 'ctypes' has no attribute 'windll' and missing WinDLL errors. The record does not reconcile exhaustive unique test coverage or classify every error. It does not prove that NeuralScreen is broken on Windows.

The pip-audit record contains an advisory total of 0 and a packages value of 0. Audit coverage is unknown; this is not evidence that the dependency tree was fully checked or that the software is safe.

For the Windows application, the README documents unpacking the portable release archive and running NeuralScreen.exe; the archive includes Python. It calls for a current NVIDIA driver and compatible RTX hardware. Windows 11 is the main documented platform; Windows 10 is reported working but remains experimental in the limitations section. The README warns that Windows will probably show an unknown-publisher warning. Games need borderless or windowed mode for the overlay.

What this review can establish

NeuralScreen's Windows overlay needs a Windows evaluation. Our October 2, 2026 Debian run can describe repository command outcomes, but it cannot tell you whether the processed image looks better or whether your NVIDIA card works.

The project describes desktop-wide neural rendering, optional frame generation, one-window capture, screenshots, processed recording and Spout2 output for OBS. Those are documented capabilities, not features we exercised in the sandbox. Its claim that games, video and photos come back sharper is also the project's claim; we did not measure image quality.

This review keeps release v2.1.9 and commit e7dd41d as the historical run reference. The supplied current README contains later changes, so its present interface and feature details should not be read as observations from that run.

What our recorded run did

The run began on October 2, 2026 at 05:47:14.250 UTC, using commit e7dd41d797123a538c8a1d69af3d908c0c1c2772. The sandbox configuration specified 3 CPUs, 8 GB of memory and the image ghcr.io/astral-sh/uv:python3.12-bookworm. The install tail identifies a Python 3.12.12 environment.

The checkout metrics recorded 380 files, approximately 97,905 source lines and 12.5 MB. The install step exited 0 in 13 seconds, with 35 dependencies and 37 MB recorded. The build-labelled step exited 0 in 5 seconds. Its stored output tail is empty, so the record does not establish what artifact it produced. Neither successful step proves that NeuralScreen.exe was installed or launched.

The test command exited 1 after 19 seconds. Its output summary reads 49 passed, 176 errors and 32 subtests passed in 13.75 seconds. The command duration and pytest's own reported duration measure different scopes. The parser also records 0 failed assertions, 0 skipped tests and a total of 225. These are recorded summaries, not independently reconciled counts of exhaustive unique coverage; the 32 subtests should not be added to them as separate top-level tests.

The tail includes AttributeError: module 'ctypes' has no attribute 'windll' and errors involving missing WinDLL. These show Windows API access failing in this Debian environment. The supplied tail does not explain every error or show that all 176 errors have one cause. The command did not complete successfully here, but that result does not establish a Windows product failure.

The pip-audit advisory total is 0, with a recorded packages value of 0. The record does not establish audit coverage. It cannot support a claim that all dependencies were checked or that NeuralScreen is safe.

The Windows setup is a separate task

The README documents a portable archive containing Python and the NVIDIA runtime files. Its launch instruction is to unpack the archive and run NeuralScreen.exe. It warns that Windows will probably display an unknown-publisher warning because the program is not signed with a paid certificate.

The documented requirements include an up-to-date NVIDIA driver and compatible RTX hardware. Windows 10 is reported working, while the limitations section still calls it experimental. Hybrid laptops and multi-GPU systems are experimental too; the README warns that a display attached to an integrated GPU may use a slower capture fallback.

For games, use borderless or windowed mode as the README directs. It explicitly advises against competitive online play because an overlay may attract anti-cheat scrutiny. We did not test anti-cheat behavior.

Read compatibility by feature

The supplied README distinguishes local validation, user reports, unverified configurations and known failures. Its matrix marks neural rendering and frame generation as locally validated on an RTX 5070 Ti. RTX 40 support is reported, with unresolved RTX 4060 cases. RTX 30 neural rendering is unverified, and frame generation is a known failure below Ada. RTX 20 is marked as a known failure for both paths.

Those are the project's compatibility labels. Our run did not reproduce them. They are more useful for a trial decision than treating every RTX card as equally supported.

The README also explains a limitation of desktop frame generation: depth is flat and motion is estimated without game-engine cooperation, so UI and text can distort. Begin a Windows evaluation with frame generation off. Use the before-and-after comparison on moving content, small text and dark scenes before judging the result from a frame counter. This is a suggested acceptance check, not a workload we measured.

Licensing affects whether it fits

The README identifies the source license as PolyForm Strict 1.0.0 and describes noncommercial use as free, with permission required for distributing, modifying or copying. It also identifies separate NVIDIA runtime notices restricting the bundled files to research or educational use. NeuralScreen states that it is not affiliated with NVIDIA.

Treat those as separate source and runtime conditions. A company considering deployment or redistribution needs to review the actual terms rather than assume that downloadable source grants ordinary open-source permissions.

When the alternatives fit better

Magpie's README describes a Windows window-upscaling tool with algorithms and filters including Anime4K, FSR and CRT shaders, licensed under GPLv3. Choose it when that kind of window scaling answers your need.

OptiScaler's README describes middleware that intercepts a game's existing upscaler calls and redirects them to another backend. It targets games already supporting DLSS2+, FSR2+ or XeSS and includes frame-generation options. Choose it for that in-game replacement task, subject to its compatibility notes and warning against online games.

How to read the scores

These are editorial evidence ratings on a 1-to-5 scale, not benchmark results. A 1 means the supplied evidence gives little basis to recommend that dimension; 2 means material constraints or verification gaps; 3 means useful documentation or support with unresolved limits; 4 requires strong corroboration; 5 requires unusually complete evidence for the assessed scope. Unknown adoption or compatibility does not earn a high rating.

Setup earns 2 because the documented archive is portable, but hardware restrictions, unsigned distribution and absent Windows verification limit confidence. Documentation earns 3 because setup, compatibility and limitations are explained, while the current README and historical release must be kept separate. Community earns 2 because a public tracker and release discussion are visible, but the supplied extracts do not establish response quality or adoption. Maturity earns 2 because the README still labels several configurations experimental or unverified and our run supplies no native acceptance evidence.

Before trying NeuralScreen, check the selected release's requirements and runtime notices. The next useful evidence is a recorded Windows session on your target GPU, not another interpretation of the Debian error count.

Alternatives

ProjectWhat it isPick it when
MagpieA GPLv3 Windows window-upscaling tool with multiple scaling algorithms and filters.Choose Magpie when you want window scaling with documented algorithms such as Anime4K or FSR, rather than specifically experimenting with NeuralScreen's NVIDIA neural-rendering path.
OptiScalerMiddleware for replacing upscalers in games that already support DLSS2+, FSR2+ or XeSS, with frame-generation options.Choose OptiScaler when your game already has a supported temporal upscaler and you want to change its upscaling backend. Its README also warns against use with online games.

What people are saying

  1. [velocity-scout] perseval-BLR/NeuralScreen
  2. [velocity-scout] perseval-BLR/DLSS5-NeuralScreen

Sources

  1. NeuralScreen repository
  2. NeuralScreen README
  3. NeuralScreen technical notes
  4. NeuralScreen v2.1.9 release
  5. NeuralScreen open issues

More ai tools reviews