Why DLSS Frame Generation Override Is Greyed Out
A greyed-out DLSS Frame Generation override does not always mean something is broken. NVIDIA App separates the Frame Generation model from the Frame Generation mode, and those controls have different requirements. Your GPU may support a model upgrade while being ineligible for Multi Frame Generation or Dynamic mode.
First, identify which Frame Generation control is greyed out
Open NVIDIA App, select Graphics, and choose the affected game under Program Settings. Check the driver settings for that game rather than judging availability from a global preference alone.
The important distinction is between DLSS Override - Model Presets, which includes a Frame Generation model selection, and DLSS Override - Frame Generation Mode, which controls supported fixed multipliers and Dynamic mode. A disabled option in one does not tell you whether the other should work.
| Disabled control | First thing to check |
|---|---|
| Frame Generation model selection | RTX 40 or RTX 50 hardware, a supported game, and in-game Frame Generation enabled. |
| Preset B specifically | Whether that game supports the newer model; general Frame Generation support is insufficient. |
| Multi Frame Generation or Dynamic mode | RTX 50 hardware and the game's corresponding override support. |
| 6X while another multiplier works | Whether the title supports 6X rather than only the earlier 4X capability. |
If several unrelated DLSS controls are unavailable, the broader guide to general DLSS override troubleshooting covers the wider profile and app checks. For a Frame Generation-only issue, establish the specific requirement before changing anything.
An RTX 40 GPU can support the model override without supporting MFG
NVIDIA's official Frame Generation model upgrades support GeForce RTX 40 and RTX 50 GPUs in compatible games. Official Multi Frame Generation, including Dynamic Multi Frame Generation, requires RTX 50 hardware.
This matters on cards such as the RTX 4070 or RTX 4090. A working in-game Frame Generation option does not mean every NVIDIA App multiplier should become selectable. A model upgrade changes the implementation used by the supported feature; it does not change the GPU's eligibility for a different feature.
Likewise, DLSS Super Resolution working on an RTX 20 or RTX 30 card does not establish support for NVIDIA's DLSS Frame Generation override. Super Resolution reconstructs the rendered image, while Frame Generation creates additional displayed frames. Treat their controls as separate capabilities when diagnosing the app.
If the disabled control matches an unsupported hardware feature, stop there. Repeated driver installations will not make that combination officially supported.
Check the game's exact feature, not just its DLSS badge
NVIDIA's RTX games and applications compatibility list separates Frame Generation, Multi Frame Generation, and other DLSS features. Use the entry for the actual game or edition you are running. A title appearing somewhere on the list does not mean every override is available.
In the relevant columns, the list distinguishes MFG support marked for 4X from support marked for 6X. Its Frame Generation upgrade marker, U, identifies model-upgrade availability, but does not by itself guarantee Preset B in every title.
That gives you a useful stopping point: if the game has a narrower supported feature set than the control you want, an unavailable option is not evidence of a corrupt installation. If the exact feature is supported, continue with the game's settings and the local app state.
Why Preset B can be unavailable when Frame Generation works
NVIDIA documents Preset B for selected games on RTX 40 and RTX 50 GPUs. It depends on additional information supplied by the game engine, including buffers used to improve the handling of interface elements. The older Frame Generation integration alone does not guarantee those inputs exist.
Look for it within DLSS Override - Model Presets, using the Frame Generation dropdown. If another supported model is available but B is not, check the game's update and compatibility status before treating the entire override system as faulty. A supported existing model remains a valid choice; forcing a preset name cannot supply missing engine data.
Make Frame Generation work in the game first
NVIDIA's override instructions require Frame Generation to be enabled inside the game. The app's override is not a universal switch that adds native DLSS Frame Generation to a game without it.
- Launch the affected game and open its graphics settings.
- Enable its NVIDIA DLSS Frame Generation option, following any restart prompt from the game.
- Exit the game before changing the override in NVIDIA App.
- Select an eligible override, apply it, and relaunch the game.
Interpret the result at each stage. If the game's own Frame Generation option is missing or unavailable, solve that prerequisite first. If native Frame Generation works but the app's model or mode remains disabled, return to that particular override's requirements. These are different symptoms and should not trigger the same sequence of reinstalls.
Check Windows GPU scheduling if native Frame Generation is unavailable
NVIDIA's Streamline documentation requires Hardware-accelerated GPU scheduling, commonly called HAGS, for DLSS Frame Generation on Windows. Find it under Windows Settings > System > Display > Graphics; the additional graphics settings page can vary with the Windows version.
Enable the setting if it is off, restart Windows, and retest the game's own Frame Generation option. If the switch is absent, check the Windows and graphics-driver prerequisites instead of assuming that an NVIDIA App refresh will create it.
HAGS is a prerequisite, not an override unlock. Enabling it does not make an RTX 40 card support official Multi Frame Generation or make an unsupported game accept Preset B.
Missing 2X and unavailable 6X are different problems
NVIDIA's instructions direct users who want ordinary 2X Frame Generation to select Use 3D app setting for the override and enable Frame Generation in the game. Where the game exposes its own multiplier selection, choose the intended native mode there.
Do not assume that the absence of a separate 2X override means normal Frame Generation has been removed. The control can delegate that choice to the game. At 2X, one generated frame accompanies each rendered frame; the label does not promise that measured performance will double in every workload.
For a supported fixed MFG multiplier, NVIDIA's setup path is Graphics > Program Settings > DLSS Override - Frame Generation Mode > Fixed. Check which choices are available for the selected title before looking for a software fault.
RTX 50 ownership alone does not guarantee 6X in every MFG game. NVIDIA documents 6X for compatible titles with the required Frame Generation integration. If 4X works while 6X is unavailable, that can be the game's supported limit. The same reasoning applies when comparing two games on the same PC: one title's working setting does not establish eligibility in the other.
Dynamic mode has its own requirements and behavior
Dynamic Multi Frame Generation is an RTX 50 feature that adjusts the frame-generation multiplier toward a target frame rate. In the supported NVIDIA App control, choose Dynamic under Frame Generation Mode, then select the maximum refresh rate target or a custom target. NVIDIA also documents an optional maximum multiplier.
This creates two separate checks. First, can you select Dynamic mode for this GPU and game? Second, once enabled, is it behaving as expected during play? A low multiplier during an easy scene can be consistent with already meeting the target; it does not, by itself, show that the override failed.
NVIDIA's Dynamic MFG setup guidance warns that the feature is incompatible with frame-rate limiters and V-Sync. Check those conditions when diagnosing its operation, and record existing settings before changing them. That warning concerns supported operation; it does not establish that every greyed-out Dynamic selector is caused by V-Sync.
If support is confirmed, refresh the software state
Once the hardware, game, and in-game setting match the requested feature, a disabled control becomes worth investigating as an app or profile issue. Update NVIDIA App, the graphics driver, and the game through their normal update mechanisms, then close the game and refresh the app's graphics information.
NVIDIA App release notes have documented fixes for missing overrides and unavailable options in supported titles. Software state can therefore matter, but it should be checked after eligibility rather than used as an explanation for every disabled option.
Also avoid following an old instruction to join the NVIDIA App beta just to access Dynamic MFG. NVIDIA subsequently announced general availability of those DLSS features. Historical rollout instructions should not override the requirements of the version you are using now.
If the whole override entry disappeared immediately after a driver update, use the separate steps for overrides missing after updates. An absent entry and a visible but disabled multiplier provide different clues.
For a persistent problem, compare another game that explicitly supports the same feature. Failure in one eligible title points toward that game's profile or integration; failure across several eligible titles gives you a stronger reason to investigate the app or driver installation. This comparison narrows the next action without requiring an immediate clean driver reinstall.
Verify the result during gameplay
After applying a supported change, relaunch the game and use NVIDIA's DLSS statistics view: open the overlay with Alt+Z, select Statistics, and choose the DLSS statistics view. Use the displayed feature information alongside the game's settings to check what is active.
Check a playable scene rather than relying on the title screen. NVIDIA's integration guidance recommends disabling Frame Generation in situations such as menus and loading screens, so those locations can give a misleading impression of whether it works during play.
Activation is only the first check. Evaluate motion, interface clarity, and control response in a repeatable scene before choosing a multiplier for regular use. PC Gamer's frame generation comparisons offer a useful independent examination of those trade-offs.
If Frame Generation is active but the image tears, the remaining symptom concerns display synchronization. Artificial Ignorance's guide to screen tearing fixes explains that issue. For Dynamic MFG, retain the compatibility caveat above instead of automatically combining it with a conventional V-Sync or frame-cap recipe.
Frequently asked questions
Why does Frame Generation work in-game while the override stays greyed out?
The native feature and the requested override can have different requirements. An RTX 40 card can run supported DLSS Frame Generation while official MFG modes remain unavailable. A game's existing integration can also work without supporting a particular newer model.
Should I reinstall the driver if only the Apply button is disabled?
First distinguish the Apply button from the feature selector. Check whether you have actually selected a different supported value; an unchanged configuration may leave nothing to apply. A disabled Apply button alone is not enough evidence to justify a driver reinstall.
Can a global override force support in an incompatible game?
No. Global preferences still apply within compatibility limits. Use the game's Program Settings entry to investigate what that title supports, and verify the result after relaunching it.
What should I include when reporting a supported option that remains disabled?
Include the exact GPU, Windows version, driver and NVIDIA App versions, game version, and a screenshot identifying the disabled control. State whether native Frame Generation works and whether another game supporting the same override has the problem. That makes the report more useful than saying only that DLSS is greyed out.
Before making another change, name the unavailable feature precisely: model upgrade, Preset B, fixed multiplier, or Dynamic mode. Match that control to your GPU and the game's supported integration, then retest one change at a time.
