Hotfix: Curves and Scanner
- Removed an overly restrictive curve check introduced in 2.1.4. Frequency differences are now recorded in diagnostics to gather evidence for better checks and more reliable results in future updates.
- Corrected a scanner guard that could stop scans on supported RTX 30 and RTX 40 cards when an auxiliary idle point changed. Actual write failures and detected instability still stop the test.
Advanced GPU tuning
- Play's Vix integration was too restrictive. Compatibility now follows the installed Vix loader's support check.
- If a future driver update causes a compatibility issue, use Update Vix tools... to download the latest components again.
- Settings changed now reflects actual edits. Selecting an unchanged value or undoing an edit restores the correct status.
Overlay
- Equal left and right padding in every reading column, including narrow tiles.
- Borderless recommended. Exclusive fullscreen unsupported.
Interface and Stabilizer
- Scanner and Overlay settings now use the same flat gray backgrounds as Advanced GPU Tuning.
More about this update
- Hotfix details and screenshots: https://christianp403-spec.github.io/NV-UV-Play/news.html#updates-215
Game database
- Includes database 2.42 with 739 games.
SmartScreen and Microsoft Defender
- SmartScreen and Defender issues can still affect updates and startup. If SmartScreen blocks the automatic update, download the release manually from GitHub: https://github.com/christianp403-spec/NV-UV-Play/releases
- If Play does not start, check Windows Security > Virus & threat protection > Protection history for quarantined Play EXE or DLL files. After checking the detection and verifying the file belongs to the official Play release, restore it and allow it on the device if needed.
- A report has already been submitted to Microsoft.
Feedback
- Please retry affected profiles and scans after updating. If a problem remains, send a new diagnostic report through Play.
VirusTotal: Report for the signed EXE. 0/67 detections on 21 October 2026. One engine timed out, one failed, and six could not process this file type.
More information: Website (English)
Thank you for your feedback, bug reports, diagnostic data and suggestions!