No, NVIDIA Did Not Just Bring Multi Frame Generation to Every RTX Card

2026-09-04 · News and analysis

There is a claim doing the rounds that NVIDIA's Multi Frame Generation, the feature that multiplies your frame rate by up to six times, has arrived on every RTX card going back to the 20 series.

It has not. NVIDIA has not announced it, has not shipped it, and has given no indication it plans to.

What has actually happened is more interesting than the version being shared, and it ends somewhere useful for handheld owners. So here is the correction, and then the part worth your time.

What NVIDIA Actually Ships

Frame generation and upscaling are two different features, and the confusion comes from treating them as one thing.

Upscaling reaches almost everything. DLSS 4.5 Super Resolution runs on RTX 20, 30, 40 and 50 cards. The second generation transformer model uses roughly five times the compute of the original, and NVIDIA notes that RTX 20 and 30 cards lack native FP8 support, so the newer models cost those GPUs more performance. Owners of older cards are often better off staying on the DLSS 4.0 model. But the feature is there.

Frame generation does not. Here is the actual support table:

NVIDIA released Multi Frame Generation 6X and Dynamic Multi Frame Generation on 31 March 2026, alongside DLSS 4.5 and Game Ready Driver 595.97 WHQL. Both are RTX 50 exclusive. The RTX 40 series stayed capped at 4X. The RTX 20 and 30 series have never had any official NVIDIA frame generation at all, which is a five year old restriction, not a new one.

Dynamic MFG is the genuinely new idea in that release. Instead of locking you to a fixed multiplier, it watches the gap between what your GPU is producing and what your display can show, then shifts the multiplier up and down in real time. NVIDIA describes it as an automatic transmission for your GPU. It is also RTX 50 only.

Where the "All RTX Cards" Story Comes From

The story is real. It is just not NVIDIA's.

Two community projects are behind it. DLSS Enabler 4.5.0.0, an open source tool by Artur Graniszewski, with a companion one-click installer called DLSS Enabler Manager by NODIX-TECH. And nvidia_mfg_bridge, a separate mod aimed specifically at RTX 20 and 30 owners.

Both descend from the same original idea, a project called dlssg-to-fsr3. The trick is straightforward once you see it. A game that supports DLSS Frame Generation makes calls to NVIDIA's frame generation library. These tools intercept those calls and quietly redirect them to AMD FSR 3 frame generation instead, which runs on essentially any modern GPU. The game thinks it is talking to NVIDIA. It is not.

On RTX 40 cards there is a middle path called Hybrid MFG, where NVIDIA's own frame generation still produces the middle frame and FSR 3 fills in the extras. That keeps some of the native quality while getting past the 4X ceiling.

So when someone says MFG now runs on a 3060, what they mean is that a mod is generating frames using AMD technology on an NVIDIA card, inside a game that was asking for something else. It works. It is not the same product.

The Numbers, and What They Actually Cost

One tester ran DLSS Enabler on an RTX 4070 Ti Super in Backrooms: Escape Together. The results look extraordinary:

351 frames per second sounds like a different GPU. Now do the division. At 6x, five out of every six frames are generated. So 351 displayed frames implies roughly 58 frames actually rendered.

Read that against the baseline. Without frame generation the card was rendering 96 real frames. With 6x running, it is rendering around 58. Generating frames is not free, and the work of producing them ate roughly a third of the card's real output.

You are looking at a game that displays like 351 fps and responds like something under 60. Latency went up, not down, which is the honest tell. Frame generation has never made a game feel faster. It makes a game look smoother.

That is a fine trade if you already had a comfortable frame rate and you want motion clarity on a high refresh display. It is a bad trade if you were hoping to rescue a game that runs badly, because the input lag you were already suffering stays exactly where it was.

The Anti-Cheat Problem

This is the part that gets left out of the enthusiastic posts.

These tools work by DLL injection. They put code inside the game process and intercept its calls. That is, mechanically, exactly what a cheat does, and it is precisely the behaviour that VAC, Easy Anti-Cheat and BattlEye exist to detect.

Anti-cheat systems do not evaluate intent. They see modified files and injected code in a protected process, and they act.

So the rule is simple. Do not put any of this near a game with anti-cheat and an online component. Single player, offline, and you are risking stability. Multiplayer, and you are risking the account.

What This Means for Handhelds

Here is where it lands for anyone reading this on a retro or PC handheld.

No handheld has an NVIDIA GPU. Not the Steam Deck, not the ROG Ally, not the Legion Go, and not a single Anbernic, Retroid or AYN device. They run AMD, Intel or ARM silicon. Every RTX exclusive feature is, for a handheld, a story about somebody else's hardware.

But frame generation itself is very much a handheld topic, because handhelds are exactly the devices that struggle to hit a comfortable frame rate. Three routes actually apply.

GeForce NOW Ultimate. The only way a Steam Deck or ROG Ally displays genuine NVIDIA frame generation is by not doing the rendering. GeForce NOW Ultimate streams from RTX 5080 class systems, which means DLSS 4.5 with frame generation, and now DLSS 5, arrive as a video feed. We covered the full picture in DLSS 5 is coming to handhelds, just not the way you think. Your handheld does no work. It also does nothing offline.

AMD FSR 3 frame generation and AFMF. This is the native path. It runs locally, it is free, it is built for the hardware in your device, and it is what the mods above are secretly using anyway. If you want frame generation on a Steam Deck or an Ally, start here. Our FSR and XeSS guide covers the settings.

Lossless Scaling. A $6.99 Windows utility on Steam that applies its own frame generation, LSFG, to any windowed or borderless application. Any game, any emulator, any GPU vendor. On Steam Deck and other SteamOS devices the Decky LSFG-VK plugin has been in the Decky Plugin Store since late 2025, though the upscaling menu is not exposed on Linux the way it is on Windows handhelds.

Lossless Scaling is the most flexible option and the most expensive in latency. In fixed 2x mode it adds roughly 1.5 to 2.5 frames of delay, which is about 25 to 42 ms at a 60 fps base. LSFG 3 cut the penalty by around 24 percent compared to LSFG 2, but it remains the highest latency frame generation method available. It works from the finished image on screen, with no access to the game's internals, so it is always guessing more than a native implementation would.

Why Frame Generation and Emulation Fight Each Other

There is an obvious thought here: if frame generation multiplies frame rate, could it rescue a struggling emulator?

Almost never, and it is worth understanding why.

Frame generation multiplies, it does not create headroom. If PS2 emulation is limping at 25 fps, interpolating to 100 fps gives you a game that looks smooth and responds like it is running at 25. Every input still waits on a real rendered frame. You have made the symptom prettier and left the disease alone.

The base frame rate needs to be decent already. Every frame generation technology works best above 60 fps and degrades badly below 40. Emulators that need help are almost always below 40. The technology is least useful exactly where it is most wanted.

Retro games are the worst case for added latency. A 2D platformer or a fighting game has input windows measured in a couple of frames. Adding 30 ms of delay to something built around frame perfect timing changes how the game plays, not just how it looks.

No emulator ships engine integrated frame generation. Native implementations get motion vectors from the game engine, describing exactly how the scene moved. An emulator has no engine to ask. So every route is an external interpolator working backwards from the finished image, guessing at motion. That is why Lossless Scaling is the only realistic option here and also why it is the highest latency one.

The honest use case for frame generation in emulation is narrow. A 3D game already running comfortably at 60 on a 120 Hz handheld screen, where you want the extra motion clarity and do not care about a few milliseconds. That is a real scenario. It is just not the one people are hoping for.

Should You Bother?

If you own an RTX 50 card: you already have all of this officially. Use MFG 6X or Dynamic MFG through the NVIDIA app. There is no reason to touch a mod.

If you own an RTX 40 card: you have official 4X. Going to 6X through a mod gets you a modest visual gain, a real anti-cheat risk, and a drop in genuine rendered frames. Hard to recommend.

If you own an RTX 20 or 30 card: the mods are the only route, and they are running AMD FSR 3 under the hood. If that appeals, you can get the same technology more safely by using FSR frame generation directly where a game offers it.

If you game on a handheld: ignore the RTX story entirely. Use FSR frame generation where a game supports it, look at Lossless Scaling for everything else, and treat GeForce NOW as the route to the NVIDIA features rather than waiting for hardware that is never coming.

If you emulate: put the effort into settings, resolution scale and a stronger device before you reach for frame generation. It fixes a problem you probably do not have.

Frequently Asked Questions

Does Multi Frame Generation work on RTX 20, 30 and 40 cards?

Not officially. NVIDIA's MFG 6X and Dynamic MFG are RTX 50 exclusive. RTX 40 cards are capped at 4X, and RTX 20 and 30 cards have never had official NVIDIA frame generation of any kind. Community mods can enable higher multipliers, but they do it by redirecting the calls to AMD FSR 3.

What is the difference between DLSS 4.5 Super Resolution and Multi Frame Generation?

Super Resolution renders the game at a lower resolution and reconstructs it larger, and it works on RTX 20 through 50. Multi Frame Generation inserts entirely new frames between rendered ones, and the newest modes are RTX 50 only. They are separate features that are often enabled together.

Is using DLSS Enabler or nvidia_mfg_bridge safe?

Not in any game with anti-cheat. Both work through DLL injection, which is the same mechanism cheats use, and VAC, Easy Anti-Cheat and BattlEye are built to detect it. In offline single player games the risk is instability rather than a ban.

Can the Steam Deck use Multi Frame Generation?

Not NVIDIA's version, because the Steam Deck uses AMD graphics. It can use AMD FSR 3 frame generation natively, Lossless Scaling through the Decky LSFG-VK plugin, or NVIDIA frame generation remotely through GeForce NOW Ultimate.

Does frame generation make games feel more responsive?

No. It adds latency rather than removing it. In the RTX 4070 Ti Super test above, latency rose from 33.4 ms to 37.5 ms when 6x was enabled. Frame generation improves how motion looks, not how the game responds.

Will frame generation fix a slow emulator?

Generally no. It multiplies whatever frame rate you already have, so an emulator running at 25 fps will look smoother but still respond like 25 fps. It also works poorly below about 40 fps, which is exactly where struggling emulators sit.

Is Lossless Scaling worth buying for a handheld?

It is useful if you play games or emulators that have no native frame generation and you already have a reasonable base frame rate. It is the most flexible option and the highest latency one, so it suits slower paced games far better than anything timing sensitive.

Related Reading

• FSR and XeSS on Handhelds: What You Actually Get
• DLSS 5 Is Coming to Handhelds, Just Not the Way You Think
• DLSS 5 Launches September 3 With Exactly One Game
• DLSS 5 Now Runs on RTX 20, 30 and 40 Cards
• The DLSS 5 Mod Risks Nobody Is Putting in the Headline
• Emulator AI Upscaling Options
• AI Upscaling vs Preservation