A neon-green gaming PC setup illustrates graphics settings, smooth high frame rates, and clearer gameplay.
If you have spent any time tweaking modern PC games on Windows, you already know that "faster" in GPU marketing usually comes with an asterisk large enough to block out the sun. NVIDIA's latest DLSS Frame Generation Performance Mode—known in the NVIDIA App as Preset C (and referred to as Model C in the app's 11.0.9.565 release notes)—is no exception. On paper, NVIDIA promises up to 35% faster Frame Generation on a GeForce RTX 5060, and independent testing confirms real frame-rate gains, especially when pushing high Multi Frame Generation multipliers on RTX 50-series hardware. Yet if you expected Preset C to magically cure the slightly rubbery input feel of generated frames, hold your horses: the speed boost comes by trimming visual polish rather than rewriting the laws of latency.

For GeForce RTX 40-series, RTX 50-series, and RTX Spark laptop owners trying to squeeze maximum smoothness out of demanding ray-traced titles, Preset C represents an intriguing new knob to turn. Whether you should actually turn it depends on your GPU generation, your tolerance for HUD shimmer, and—most importantly—how many real frames your graphics card is rendering before AI steps in to paint the rest.

A neon-green gaming PC setup illustrates graphics settings, smooth high frame rates, and clearer gameplay. How Preset C Squeezes Out Extra Frames​

To understand why Preset C behaves the way it does, it helps to peek under the hood of how DLSS Frame Generation actually constructs interpolated frames. NVIDIA's pipeline relies on two separate AI models working in tandem:

  • Model One (Motion Vectors and Depth): This model ingests data straight from the game engine—specifically motion vectors and depth buffers—to map how 3D geometry and objects move between two natively rendered frames.
  • Model Two (Optical Flow): This second model handles optical flow estimation to track pixels that game engines do not always describe cleanly in motion vectors, most notably 2D user-interface elements, subtitles, and complex ray-traced effects.

With Preset C, NVIDIA leaves the first model intact and replaces that second optical-flow AI model with what the company calls a "faster and lighter algorithm." Because it takes less GPU compute and memory bandwidth to run each generated frame through a lighter optical-flow pass, the graphics card spends less time generating synthetic frames and more time feeding your display.

That architectural shortcut applies across standard 2X Frame Generation, Multi Frame Generation (4X and 6X), and Dynamic Multi Frame Generation. It also explains why the gains scale so unevenly across different hardware setups. If you are generating just one fake frame for every real frame (2X), the optical-flow pass only runs once per rendered frame—leaving very little overhead to shave off. Crank Multi Frame Generation up to 4X or 6X on an RTX 50-series card, however, and you are suddenly running that optical-flow calculation three to five times per rendered frame. Shaving a fraction of a millisecond off each pass adds up fast.

  • Section takeaway: Preset C does not accelerate your game engine directly; it reduces the GPU overhead of the optical-flow model used to build interpolated frames, meaning the biggest payoffs happen when your GPU is generating multiple synthetic frames per real frame.

Benchmarking the Gains: Marketing Claims vs. Real-World Tests​

NVIDIA's headline claim—up to 35% faster on a GeForce RTX 5060—sounds dramatic until you look at how that number behaves across different cards and multipliers. In NVIDIA's own RTX 5060 6X Multi Frame Generation demonstration in Cyberpunk 2077, reported by OC3D, total displayed output rose from 255 FPS to 348 FPS. NVIDIA's chart lists the underlying frame-generation-off rate at 83 FPS: the gain comes from each generated frame costing less at 6X, not from the base render rate climbing. The 42.5 FPS and 58 FPS figures are simply the displayed totals divided by six, not measured base frame rates.

Independent testing shows a far more nuanced picture depending on what GPU you have in your PCIe slot:

Hardware & Game ScenarioMultiplierPreset C vs. Preset B GainSource Attribution
GeForce RTX 4090 (general 2X test)2X~5% (100 FPS to 105 FPS)XDA Developers (Hamlin Rozario)
GeForce RTX 5080 (Crimson Desert, 4K DLSS 4.5 Perf + RR)2X~5%Digital Foundry
GeForce RTX 5080 (Crimson Desert, 4K DLSS 4.5 Perf + RR)4X~9.5% to 10%Digital Foundry
GeForce RTX 5080 (Crimson Desert, 4K DLSS 4.5 Perf + RR)6X~18% to 20% (~250 to ~300 FPS)Digital Foundry
GeForce RTX 5060 (NVIDIA official 6X showcase)6X~36% (255 FPS to 348 FPS)NVIDIA via OC3D

Notice the pattern? In XDA Developers' testing on an RTX 4090—which is limited to 2X Frame Generation—switching from Preset B to Preset C nudged a 100 FPS baseline to just 105 FPS. That 5% bump is barely a rounding error in day-to-day gameplay. By contrast, Digital Foundry's RTX 5080 testing in Crimson Desert demonstrated why Preset C exists: while 2X stayed around 5%, 4X jumped roughly 9.5% to 10%, and 6X surged close to 18–20%, taking output from around 250 FPS on Preset B to just under 300 FPS on Preset C.

What about input latency? Across both XDA Developers' hands-on impressions and public latency checks—such as a 1440p 2X RTX 5070 test cited in NVIDIA Profile Inspector documentation showing 49 ms on Preset B versus 47 ms on Preset C—the responsiveness improvement at 2X is negligible. Even at 4X and 6X, where freeing up base frame rate trims a bit more delay, generated frames still do not make a game feel as snappy as running natively at those triple-digit frame rates. From an industry-architecture standpoint, that makes complete sense: input polling and simulation updates are still anchored to your base rendered frame rate, not the interpolated frames inserted between them.

  • Section takeaway: On RTX 40-series GPUs capped at 2X Frame Generation, Preset C delivers roughly a 5% FPS nudge with virtually unchanged responsiveness; its real speed advantage belongs to RTX 50-series cards running 4X or 6X Multi Frame Generation.

The Catch: What You Give Up in Image Quality​

NVIDIA openly describes Preset C as a Performance Mode with "minor trade-offs in image quality" rather than a straight replacement for Preset B. That distinction matters because Preset B—introduced alongside UI Recomposition in DLSS SDK 310.6.0—was specifically tuned to keep 2D interfaces and text crisp while frames were being synthesized around them.

When Preset C swaps out the heavier optical-flow AI model for a lighter algorithm, the cracks appear right where that second model used to shine:

  • Subtitles and HUD Text: XDA Developers notes that moving text under Preset C can resemble basic frame blending rather than smart AI reconstruction. Digital Foundry observed the exact same behavior in Crimson Desert, where Preset B preserved shifting subtitles cleanly while Preset C blurred them with simpler blending.
  • Particles and Fast Motion: Fire particles tend to break up more noticeably on Preset C, and fast-moving objects or wall textures during rapid camera pans can show extra smearing or instability.
  • Low Base Frame Rates: According to community testing documented by the NVIDIA Profile Inspector team, UI blur and ghosting become more pronounced if your underlying base frame rate dips below roughly 40 FPS.

To be fair, at 2X in a calm single-player scene, you often need slowed-down side-by-side footage to spot the difference. The catch is that Preset C's biggest speed gains occur at 4X and 6X—where 75% (three out of four) and 83% (five out of six) of the frames hitting your eyeballs are AI-generated. At 6X, Preset B already shows occasional interpolation artifacts during chaotic combat. Asking a lighter, less accurate algorithm to invent 83% of your image means trading extra smoothness for noticeably messier particles and text in fast-paced games.

  • Section takeaway: Preset C essentially steps backward on UI, subtitle, and particle stability in exchange for speed, making Preset B the safer choice for text-heavy RPGs or lower base frame rates.

How to Enable and Verify Preset C on Windows 11​

Even in NVIDIA App 11.0.9.565, NVIDIA still classifies the Frame Generation Performance Mode as a Beta feature, and it only officially supports GeForce RTX 40-series, RTX 50-series, and RTX Spark systems. (RTX 30-series owners are left out officially, though unofficial third-party mods exist—and as always, you should never combine driver-level Smooth Motion with native DLSS Frame Generation.)

Follow these steps to test Preset C cleanly on your Windows PC:

  • Opt in to the NVIDIA App Beta: Open the NVIDIA App, navigate to Settings → About, and check "Opt in to access Beta or experimental features." Wait for the beta update to download and install when prompted.
  • Close your game first: NVIDIA's DLSS override documentation specifies that the target game must be closed before changing override presets, with Frame Generation enabled inside the game's own graphics menu.
  • Select your target profile: Go to the Graphics tab and either pick an individual supported game under Program Settings or choose Global Settings at the top to apply it across supported titles.
  • Switch the Frame Generation preset: Scroll down to Driver Settings, click DLSS Override - Model Presets, choose Custom, open the Frame Generation dropdown, select Preset C, and click Apply. (If Preset C does not appear in the list, reboot Windows so the updated DLSS runtime files register properly.)
  • Verify it is actually running: Launch the game and press Alt+Z to open the NVIDIA Overlay, then head to Statistics → Statistics View → DLSS (you can toggle the on-screen readout with Alt+R) to confirm which Frame Generation preset the driver loaded.

Power users who prefer NVIDIA Profile Inspector (version 3.0.2.1 or pre-release 3.0.2.3) can force the exact same driver flag (DLSS-FG - Forced Preset Letter set to 0x00000003, alongside enabling DLSS-FG - Enable DLL Override), provided the v310.9.16 Frame Generation DLL is present on the system. Just be careful not to confuse DLSS-FG - Forced Preset Letter with the similarly named DLSS - Forced Preset Letter, which controls Super Resolution upscaling rather than Frame Generation. To revert at any time, simply switch the NVIDIA App override back to Recommended or Preset B.

  • Section takeaway: Enabling Preset C takes a quick trip into the NVIDIA App beta's DLSS Override menu—and using the built-in Alt+Z DLSS overlay is the easiest way to verify the change actually stuck.

Which Preset Should You Actually Use?​

Choosing between Preset B and Preset C comes down to what your PC is already achieving before Frame Generation enters the chat. If you are gaming on an RTX 4090 or another RTX 40-series GPU at 2X, a 5% frame-rate bump rarely justifies turning crisp subtitles and HUD markers into smeary frame blends. On the other hand, if you have an RTX 50-series card hooked up to a 240 Hz or 360 Hz monitor and you are pushing 4X or 6X Multi Frame Generation in a heavy path-traced showcase—or trying to stretch an RTX 5060's frame budget—Preset C's 10% to 35% uplift can genuinely help keep output near your panel's refresh ceiling.

Just remember the golden rule of frame generation: base frame rate is king. If a game feels sluggish at 35 FPS natively, neither Preset B nor Preset C will turn it into a responsive esports experience. Get your base frame rate healthy first with DLSS Super Resolution and sensible settings—topics fellow WindowsForum.com members frequently dissect in our GPU tuning and Windows 11 optimization threads—and treat Preset C as a specialized turbo button rather than a free lunch.

  • Final verdict: Stick with Preset B for 2X Frame Generation, text-heavy games, or lower base frame rates; flip on Preset C when you are driving high Multi Frame Generation multipliers on RTX 50-series hardware and care more about hitting peak refresh rates than keeping every subtitle razor-sharp.

Correction (November 22, 2026): An earlier version of this article said NVIDIA's RTX 5060 demonstration showed the underlying baseline frame rate rising from 42.5 FPS to 58 FPS. Those figures were the displayed totals divided by six, not the base rate. NVIDIA's chart lists frame generation off at 83 FPS; the 6X displayed output rose from 255 FPS to 348 FPS because each generated frame costs less, not because the base render rate climbed.

 

References

  1. Nvidia's new Frame Generation preset is faster, but there's a catch XDA 2026-11-22T17:00:23+00:00
  2. DLSS 5 Comes To Hogwarts Legacy & RTX Spark, Powered By 2X Faster Model | NVIDIA nvidia.com
  3. DLSS Frame Generation Preset C in NVIDIA Profile Inspector nividiaprofileinspector.org