Why DLSS Super Resolution Override Shows Unsupported in NVIDIA

A selectable model override does not establish that the resolution-mode override must also be selectable. Likewise, an unavailable mode control does not tell you whether a separately supported model override can operate. Inspect each row independently.

This distinction explains an apparently contradictory screen: the game offers DLSS Quality, Model Presets allows a choice, and Super Resolution says Unsupported. Those observations describe three different capabilities; they are not automatically evidence of one broken installation.

The mode override can expose choices beyond a game’s own menu. Supported configurations allow preset selection or custom scaling between 33% and 100%. DLAA uses native-resolution input; Performance mode uses approximately half the output width and height.

That flexibility is the reason custom resolution scaling matters: it offers finer control over the image-quality and performance trade-off. Its absence is a restriction on that control, rather than proof that ordinary in-game upscaling has stopped working.

The example also shows why changing the model and the scale together makes a comparison ambiguous. A different input workload can alter performance independently of the model. To assess a model change, keep the mode steady; to assess scaling, keep the model steady.

In NVIDIA’s RTX Games and Apps list, a basic checkmark indicates support for the listed feature. The Super Resolution model-upgrade annotation is more specific. The DLAA annotation referring to Super Resolution Mode describes another override capability. Read the legend alongside the feature column.

Compare the exact title and edition. A screenshot from a remaster, another build, or a modified installation is a clue to investigate, not proof that your configuration should expose the same controls. The broader override compatibility guide covers cases involving other DLSS features.

Super Resolution is available across GeForce RTX generations in supported games. Do not import a Frame Generation hardware restriction into this diagnosis. Conversely, owning a newer RTX card does not establish support for every override in every game.

These patterns narrow an investigation; they do not identify a cause by themselves. I would preserve the exact wording in a screenshot before making changes, especially when several warnings appear on the same page.

NVIDIA’s app release history includes fixes for missing overrides in manually added games and unavailable overrides in supported titles. Software problems are therefore possible. Updating is a sensible check when support matches; it is not a promise that an unsupported integration will become supported.

1. Record, then update

   Note your GPU, app version, driver version, and game build. Update the app, compatible driver, and game through their official channels. Complete any required restart before comparing results.

2. Enable the relevant in-game feature

   Select DLSS upscaling in the game, save, and exit to the desktop. This prepares the feature for an override; it does not guarantee that an unavailable mode selector will unlock.

3. Refresh the correct entry

   Open Graphics, use the program list’s three-dot menu and Refresh, then inspect Program Settings for the installation you actually launch. Confirm the executable and edition before drawing a conclusion.

4. Apply only an available choice

   Under Driver Settings, select the supported override, click Apply, and relaunch. If the same row remains Unsupported, record that result and return to the compatibility question.

I would stop this loop after a clean comparison. Repeating the same update-and-refresh sequence without new evidence is unlikely to explain why one specific mode is unavailable. Keep unrelated settings unchanged so that any improvement has an identifiable cause.

If you want a newer Super Resolution model and its override is supported, the unavailable mode row may not prevent that goal. Current app instructions use Recommended where older guides show Latest. Recommended can select different models depending on the active mode, so do not equate one unexpected letter with failure.

If you want DLAA or a particular custom scale, inspect the game’s own options. A native option may already provide what you need. When neither the game nor the supported app controls offer it, retain an available native mode rather than treating every local tweak as an official fix.

Performance is a separate decision. NVIDIA notes that the newer M and L models can carry a greater cost on RTX 20 and 30 series cards because those generations lack native FP8 support. An active override that runs slower is not the same problem as an unavailable override.

For an available override, enable NVIDIA Overlay and open its DLSS statistics view:

Read the available information for the relevant component while playing. A model readout helps evaluate a model change; it does not, on its own, prove a requested custom scale. Keep the in-game mode and app selection with your screenshot so that the evidence describes the same configuration.

If a model selection saves but runtime evidence disagrees, follow the model preset checks. If the overlay supplies no useful data, keep the result inconclusive. An FPS counter alone cannot identify the active model or confirm a particular input scale.

Once activation is established, assess image quality separately. For example, persistent horizontal tearing deserves screen tearing checks; it is not a useful test of whether an override selector should be available. Change one variable at a time during that second investigation.