Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

DLSS 5 Is Running Inside PCSX2 Now, and Emulation Was Never the Plan

2026-08-31 · News and analysis

Two days after we wrote that the leaked DLSS 5 library needed an RTX 50 card and had nothing to do with retro gaming, someone got it running in a PlayStation 2 emulator.

That is the actual news. Not that it looks good, because the jury is very much out on that. The news is that a neural rendering model NVIDIA built for modern game engines is now being pointed at Manhunt running in PCSX2, and it does something.

This is the part of the DLSS 5 story that finally touches the kind of games this site cares about. Here is what happened, what it actually does to a PS2 game, and why we still think you should leave it alone for now.

How Emulation Got Into Scope At All

When we first covered the leak, the reason it could not touch emulators seemed structural.

DLSS 5's neural rendering layer is an add on. It works by hooking a game's existing DLSS calls and doing extra work inside them. A game that never shipped DLSS never makes those calls, so the add on has nothing to attach to and sits idle. No emulator ships DLSS. Case closed.

Then the community routed around it. A project called DLSS5-Feeder stopped waiting for the game to make the call and started making the call itself, assembling the inputs DLSS expects out of what ReShade already has access to. We break down how that trick actually works separately, because it is the single most important development in this whole story.

The practical result is that the requirement stopped being "a game with DLSS support" and became "anything ReShade can hook with a usable depth buffer." Emulators qualify. PCSX2 renders through Direct3D and Vulkan like anything else.

What It Actually Does To A PS2 Game

This is where the enthusiasm should cool off.

PS2 games are low polygon models wearing low resolution textures, built for a display roughly 640 pixels across. Neural rendering was trained to re infer photorealistic lighting and materials. Pointing the second thing at the first thing does not produce a remaster. It produces a guess.

What testers are reporting is broadly what happened when the same library got pointed at Skyrim, only more so. Character faces get smoothed and reshaped into something more conventionally detailed than the source ever contained. Lighting gets reinterpreted. The overall image drifts toward a photographic look that a 2003 PS2 game was never aiming for.

In Manhunt specifically, that is a strange thing to do on purpose. The game's grain, murk and low fidelity are not limitations the developers were apologising for. They are the entire mood.

The Motion Vector Problem Is Worse Here

There is a technical reason emulation is a harder case than a modern PC game, and it is worth understanding because it will not be fixed by a better mod.

DLSS needs to know how things moved between frames. Modern engines hand it real motion vectors, because the engine already tracks that data for its own purposes. DLSS5-Feeder does not have those. It estimates them from the finished image using optical flow, which is a reasonable approximation of the truth and not the truth.

An emulator makes that estimate harder. You are guessing at motion in a frame that was itself produced by hardware emulation at a resolution the model has never seen much of, often with dithering and blending artifacts the PS2 relied on. Errors in the motion estimate become smearing, ghosting and instability during camera movement.

So the still screenshots look more impressive than the game does in motion. That gap is not a bug in one build. It is the method.

What About The Emulators People Actually Use

The obvious follow up question is whether this reaches Dolphin, RPCS3, PPSSPP and the rest.

Technically, mostly yes. The requirement is a ReShade compatible rendering path and a depth buffer, which most desktop emulators have. There is nothing PCSX2 specific about the approach.

Practically, no one should be planning around it. Every one of these emulators already has a mature, supported, free way to improve image quality that does not involve leaked code, and in most cases it produces a better result. We cover what those options are and how they compare in a separate guide, because that is the genuinely useful version of this conversation.

The short version is that raising an emulator's internal resolution renders the game's real geometry at higher precision. Nothing is invented. That is a fundamentally different operation from asking a model to imagine what a face should look like, and for 3D console games it is the one that actually works.

Does This Affect Handheld Gaming?

Still no, and for the same reason as before.

DLSS is NVIDIA only. Every PC gaming handheld on the market runs AMD graphics or, in the MSI Claw's case, Intel. There is no NVIDIA GPU Windows handheld to run any of this on. The Steam Deck, the ROG Xbox Ally X20, the Legion Go and the Legion C700 are all out, permanently, on hardware grounds.

What did change is the desktop side. The RTX 50 requirement has collapsed, and DLSS 5 now runs on RTX 20, 30 and 40 series cards with real caveats. If you emulate on a desktop with an older RTX card, you are no longer excluded on hardware grounds. You are only excluded on judgement grounds.

For handheld owners, the upscaling conversation remains FSR and XeSS, which we cover in our guide to what those actually give you.

Why We Are Still Not Linking Anything

Same position as the rest of this cluster, and it has not softened.

The library at the centre of all this is unreleased NVIDIA code that escaped inside an NBA 2K27 early access build by mistake. It was never licensed for distribution. We will explain what the projects do and name them, because that is reporting. We will not link the DLL, link a package that bundles it, or write install steps.

If that sounds overcautious, note that this is the same rule we apply to ROMs and leaked game code elsewhere on the site. A thing being easy to find is not a reason for us to be the ones handing it over.

The official DLSS 5 release is due in Fall 2026. At that point this becomes a supported feature with a legitimate download, and we will cover it properly.

Our Honest Read

This is a genuinely interesting technical achievement and a bad idea for your game library.

Getting a neural rendering model to work inside an emulator it was never designed for, using synthesised inputs, is impressive engineering. The people doing it are having fun and should keep going.

But the case for actually playing this way is thin. You would be running leaked, unfinished code, at a heavy frame rate cost, feeding it estimated motion data, to make a PS2 game look like something its artists did not choose. Meanwhile the emulator's own settings menu contains a better answer that costs nothing and breaks nothing.

The wider argument about whether AI generated detail belongs in old games at all is one we made at length here, and this development does not change it. It just moves it closer to home.

Frequently Asked Questions

Does DLSS 5 work in PCSX2?

Yes, in the sense that people have got the leaked neural rendering library running inside it, with Manhunt the demonstrated example. It requires ReShade and a community project that synthesises the inputs DLSS expects. It is not a PCSX2 feature, it is not supported, and it is not in any official build.

Can I use DLSS 5 with Dolphin or RPCS3?

Technically the same approach should work, since it needs a ReShade compatible rendering path and a usable depth buffer rather than anything emulator specific. We have not seen verified demonstrations for those emulators, and we would not recommend it regardless. Internal resolution scaling gives 3D console games a better result with no downsides.

Does DLSS 5 make PS2 games look better?

It makes them look different, and more photorealistic. Whether that is better depends on what you want. PS2 art was made for low resolution displays with deliberate use of murk and grain, and pushing it toward photorealism works against that. In motion, estimated motion vectors also cause smearing and ghosting that still screenshots do not show.

Why does DLSS 5 look worse in motion in emulators?

Because it is not getting real motion vectors. Modern game engines hand DLSS accurate per pixel motion data. In an emulator the mod estimates it from the finished frame using optical flow, and errors in that estimate show up as ghosting and instability whenever the camera moves.

Is this better than raising internal resolution in an emulator?

No, for 3D games. Internal resolution scaling renders the game's original geometry at higher precision, so the extra detail was always in the game data and nothing is invented. Neural rendering generates detail that never existed in the source. For PS1, PS2, GameCube and later 3D systems, internal resolution is the correct tool.

Can my Steam Deck do this?

No. The Steam Deck uses AMD graphics and DLSS is NVIDIA only. The same applies to the ROG Xbox Ally X20, the Legion Go, the Legion C700 and every Anbernic, Retroid and Miyoo device. There is no NVIDIA GPU Windows handheld.

Should I try this?

We would not. It relies on leaked NVIDIA code, costs a large chunk of your frame rate, produces unstable results in motion, and competes with a free supported option built into the emulator you already use. The official DLSS 5 release arrives in Fall 2026 and is worth waiting for.