`nvngx_dlssnr.dll` is a spectacularly dull name for the 158MB file that has opened DLSS 5 ahead of schedule. Renan Maniero, a developer associated with RenoDX, found it inside NBA 2K27 early access on August 26, and one day later the community had it altering character models in Control. NVIDIA had previously controlled every comparison. Now there is a real file, a menu packed with sliders and people forcing it into games never prepared for DLSS 5, but also bugs and far too much enthusiasm for treating a preliminary build as a finished product.
The DLL nobody expected
A DLL is a package of instructions that other Windows software can load. This one is named `nvngx_dlssnr.dll`, where the last two letters stand for Neural Rendering, and NBA 2K27 shipped version 310.8.0.0, according to Tom's Hardware's investigation.
Dropping the file beside a game does not create an official DLSS 5 integration. RenoDX had to feed the model colour, depth and motion data for every frame so it could understand the scene and preserve stable elements. The result already works on Control's characters, with controls for style, intensity, tone and structure.
NVIDIA calls it a “real-time neural rendering model designed to transform traditional rasterized graphics.” It is like a photocopier redrawing a face after printing the page, while the artist still decides where and how strongly it acts.
This is not simply another version of familiar upscaling. DLSS, FSR and PSSR usually rebuild a higher-resolution image or generate frames to improve fluidity. Neural Rendering receives a composed scene and changes how skin, hair, fabric or lighting appears. Performance still matters, but the tool can also alter art direction.
From RTX 50 to RTX 40
The DLL discovered in NBA 2K27 initially worked only on Blackwell, the architecture behind RTX 50 cards. The model relies on FP8 calculations that RTX 40 hardware can also perform, but the package contained CUDA code compiled specifically for the newer generation. The older key could operate the lock; NVIDIA had changed how it was inserted.
A modder known as Uncle Burrito found those binaries, replaced the incompatible sections and made the technology run on Ada Lovelace. Tom's Hardware verified the patch on an RTX 4080, while other developers are preparing RenoDX variants.
That proves a technical route exists. It does not commit NVIDIA to official RTX 40 support. A community patch can tolerate manual installation, errors and narrow combinations, but a driver for millions of systems cannot require users to diagnose a failed CUDA binary. RTX 30 hardware faces a larger obstacle because Ampere lacks native FP8 support.
Why 35 FPS is not a verdict
The most repeated result comes from an RTX 5070 Ti at 4K. Control fell from 71 FPS to 35 with Neural Rendering enabled. Losing just over half the frame rate sounds damning until you notice that the tester did not publish the internal resolution, DLSS 5 style or applied intensity.
Judging the finished technology from this run would be like reviewing a game from a build somebody left in a folder. The file may be old, incomplete or tuned for NBA 2K27, while RenoDX is asking it to interpret another engine's materials and characters. I think the remarkable part here is that it works at all, not that it runs at a low frame rate.
The tests do reveal something March's announcement did not: DLSS 5 can operate as post-processing over existing games, and masks, tone and intensity radically change the output. Developer judgement may matter as much as the model. Our guide to input lag and frame rates explains why one counter never captures the whole experience.
NVIDIA schedules the official launch for autumn 2026. Only then can we measure final drivers, supported games and a confirmed GPU list. For now, 35 FPS describes this DLL—not DLSS 5 as a finished product.
The conversation starts here
Sign in with a supporter account to comment. Sign in
Nobody has commented yet. Want to go first?