An unfinished build of Nvidia's DLSS 5 leaked by accident, and the people who got hold of it pointed it at old games. A widely shared clip of Halo: Combat Evolved, the 2001 original, looks like it went through fourteen rounds of compression: blotchy colour somewhere near cheap HDR, faces given an unsettling hyperreal level of detail. The performance numbers came with it. One tester's frame rate in Final Fantasy VII Rebirth halved; another's in GTA V fell from 90 to 29. Nvidia has not shipped DLSS 5 yet, and in that Halo example the settings were turned all the way up.
DLSS 5 uses AI to rework game graphics wholesale. Players had a sense of where that would end before anything leaked, because Nvidia's own demonstration clips looked odd, sat badly against the art direction of the games they were applied to, and carried the familiar AI sheen. The nickname arrived quickly: slop tracing, built off Nvidia's own ray tracing branding. The criticism got loud enough that Nvidia put Jensen Huang on the defence of a consumer graphics feature, at a point when the chief executive spends most of his public time on AI and comparatively little on games.
That is the part worth pausing on. A CEO who is selling the largest infrastructure buildout in the industry does not personally argue about how Halo looks unless the company has decided the problem is reputational rather than technical.
The leak itself is contaminated evidence, and Nvidia knows it. The code is unfinished, it was obtained illegally, and many of the examples circulating were built to push the feature into absurdity on purpose. Every artifact in them has an available excuse, and so does the frame rate, since nobody optimises a build nobody meant to release.
50% frame rate drop in Final Fantasy VII Rebirth, 90 to 29 frames per second in GTA V.
What the excuse does not cover is the complaint the tester made about the feature working correctly. Even at its best, he said, DLSS 5 strips out the original characteristics of the image and leaves the game incredibly bland. That is not a bug report. It is a description of what the technique does when it succeeds, and it matches the Cloud Strife example that spread alongside the Halo clip: the Final Fantasy character came back only distantly recognisable, less himself than someone in costume wearing far too much makeup, prettied up to the point of being overly prettied up.
The more telling signal is not in the leak at all. When Nvidia announced DLSS in March, Huang called it a GPT moment for graphics. As the criticism refused to die down, he said he does not like AI slop either, while insisting DLSS 5 works differently. Nobody retreats from a slogan that good over material they can dismiss as stolen and unfinished. The walk-back is the company conceding that the demos it made itself did not land.
Notably absent from anything Nvidia has said is the thing the tester's complaint actually turns on: whether the flattening is a tuning problem that a finished build fixes, or the output of the approach working as designed. There is no ship date, no statement of what the default settings will be, and no acknowledgment that the maximum setting people are mocking is a setting Nvidia chose to include.
Nvidia will release something better than what escaped. It will be measured against what escaped regardless, by an audience that had already named the feature before the first frame leaked, and the company cannot rebut the comparison without treating stolen code as a fair test of its own product.