Nvidia has unveiled DLSS 5, built around a headline feature called 3D-guided neural rendering. Its positioning is a clear break from earlier versions: the DLSS 4 lineup centered on super resolution, frame generation, and ray reconstruction, all aimed at squeezing out more frames at the same visual quality. DLSS 5 goes the other way, spending spare compute headroom on sharper lighting and materials instead. The launch title is NBA 2K27, arriving alongside the game at 9 p.m. Pacific time on September 3, with a matching Game Ready driver released the same day.
Technically, Nvidia breaks the feature down into three pieces. First is deterministic output: the model doesn't invent detail out of thin air. It takes the frame the game engine has already rendered as its base anchor, reads the objects, materials, and light sources in the scene, and adds detail on top of that foundation. Second is temporal stability: a strict single-frame-in, single-frame-out structure, with cross-frame consistency handled by motion vectors the engine already provides. Third is real-time execution — the model has been compressed enough to run the entire 3D render pipeline on a single GeForce RTX 50-series GPU.
The effects Nvidia calls out are concentrated in a handful of areas that have long been difficult: subsurface scattering in skin, light transmission through hair, and stronger contact shadows. These are either too costly for traditional rasterization and current ray tracing to compute properly, or they end up as hand-baked approximations from art teams.
The frame-rate table, and its limits
Nvidia published a table of measured results from NBA 2K27:
| Resolution | RTX 5090 | RTX 5080 | RTX 5070 Ti | RTX 5070 |
|---|---|---|---|---|
| 4K | 370 FPS | — | — | — |
| 1440p | 590 FPS | 410 FPS | 350 FPS | 260 FPS |
Support covers desktop and laptop GeForce RTX 50-series GPUs, plus GeForce NOW Ultimate subscribers streaming from cloud RTX 5080 instances. The cutoff here is drawn more sharply than it was for DLSS 4 — RTX 40-series cards and older are left out entirely this time, a direct consequence of how much tensor compute the model demands.
A basketball game is a carefully chosen showcase: indoor lighting that stays fixed, a stable camera distance, and a frame dominated by skin and jersey materials — exactly the conditions where DLSS 5 performs best. Whether it holds up equally well in open-world scenes with day-night cycles, large-scale weather shifts, or distant vegetation is a question this single launch title can't answer.
Dials left for artists to turn
On the developer side, Nvidia's integration is more open than expected. There's more than one AI model to choose from, both structural strength and tonal strength can be dialed in, and there are two tiers of masking: a semantic auto-mask that applies by object category in the scene, and an engine-level mask precise enough to target a single asset. Integration runs through NVIDIA Streamline, or directly via an Unreal Engine 5 plugin.
The existence of these controls shows Nvidia understands exactly what art teams are most afraid of. The easiest reason to reject neural rendering outright is that it overrides creative intent — the model might think a patch of skin should be brighter, while the artist wants it left dark. Handing over an asset-by-asset kill switch does far more to reassure teams than any amount of marketing-page language promising to "preserve the artist's vision."
Looking at the product line as a whole, DLSS has, by its fifth generation, largely exhausted the "performance" theme it built its name on: super resolution cuts down render resolution, frame generation cuts down rendered frame counts, and both paths are running into diminishing returns. Turning AI toward visual quality instead is a natural next step — but the trade-off is that a feature everyone once benefited from becomes a selling point exclusive to new cards. By rough count, the RTX 50-series requirement alone shuts out the large majority of players still running 30- and 40-series cards.
Sources: NVIDIA GeForce official technical pages, CocoLoop; the frame-rate table, supported hardware range, developer integration methods, and masking granularity have all been checked against officially published material.