How to Fix DLSS Model Preset Override Not Working

Windows PC troubleshooting

To fix a DLSS model preset override that appears not to work, check the active DLSS feature, apply the setting to the correct game profile, relaunch, and verify the model in NVIDIA’s overlay. Recommended does not select the same Super Resolution model in every quality mode, so seeing an unexpected preset letter can be normal.

I would establish what the game is actually running before reinstalling anything. A saved setting, an unchanged FPS counter, and an older DLL filename each tell you something different; none alone settles whether the intended model is active.

The diagnostic route

Follow the setting into the game

  1. 1SupportConfirm the exact feature and title.
  2. 2ProfileSelect the installation you launch.
  3. 3FeatureEnable the matching DLSS option.
  4. 4ApplySave the override and relaunch.
  5. 5EvidenceCheck the active model in-game.
01 / Identify the failure

Does the setting fail to save, or fail to activate?

Open the affected game’s Driver Settings and note the exact control. If your choice remains selected after leaving the page and returning, move to runtime verification. If it immediately reverts or reports an error, investigate that saving problem first.

CONTROL UNAVAILABLE

The selector is greyed out

Check eligibility before chasing model letters. The greyed-out override checks cover unavailable controls, GPU requirements, and detection problems.

CONTROL SAVED

The result looks unchanged

Continue below. You may be expecting the wrong model, testing a different DLSS component, or comparing a scene where the visual difference is subtle.

Write down whether you mean Super Resolution, Ray Reconstruction, or Frame Generation. Super Resolution reconstructs the image from a lower input resolution; Ray Reconstruction handles ray-traced image reconstruction; Frame Generation creates additional displayed frames. Their model controls and requirements are not interchangeable.

02 / Check your expectation

Current NVIDIA App guidance uses Recommended where older instructions show Latest. For the separate Super Resolution model, its selection depends on the active DLSS mode:

Recommended Super Resolution presets, checked October 2026
Active modeExpected preset
PerformanceM
Ultra PerformanceL
Quality, Balanced, or DLAAK

M is tuned for Performance mode, while L is optimized for 4K Ultra Performance. Quality mode plus Recommended plus a reported K is also consistent with the documented selection. Reapplying Recommended repeatedly would not resolve a mismatch that exists only in your expectation.

If your goal is specifically to compare M or L in Quality, select that Super Resolution preset explicitly where supported. Keep the quality mode unchanged during the comparison. Otherwise, you are changing both the model and its input resolution, making the result harder to interpret.

This table describes Super Resolution. Do not use it to interpret a Ray Reconstruction or Frame Generation preset letter.

03 / Check the active component

Ray Reconstruction needs its own model check

Ray Reconstruction combines denoising and Super Resolution within one model. When it is active, checking only the separate Super Resolution preset can therefore lead you to diagnose the wrong component.

WHAT YOU NOTICE

M or L does not appear as expected

You selected a Super Resolution preset, but the game also has Ray Reconstruction enabled. First establish which component the overlay’s model readout describes.

WHAT TO CHECK

Inspect Ray Reconstruction separately

In Model Presets, use Custom to inspect the Ray Reconstruction selection. NVIDIA’s DLSS 4.5 instructions specify Recommended or Preset F for this component in supported titles.

For a controlled Super Resolution comparison, temporarily turn Ray Reconstruction off if the game allows it, then relaunch and check again. This is a diagnostic isolation step, not a recommendation to permanently give up Ray Reconstruction’s image treatment.

Keep that change out of your performance comparison: switching Ray Reconstruction also changes the rendering workload. Establish the active model first, then restore the feature combination you actually want to evaluate.

04 / Apply one controlled change

Use one game profile from start to finish

Global overrides are convenient after everything works. During diagnosis, I would make the intended setting explicit for one game so that inherited settings and changes elsewhere in the library do not obscure the result.

1

Confirm feature support

Check the exact game and feature in NVIDIA’s RTX Games and Apps list. Its Super Resolution and Ray Reconstruction override annotations are more specific than a general DLSS checkmark. The override compatibility guide explains those distinctions.

2

Update the relevant software

Update NVIDIA App, the compatible graphics driver, and the game. Restart when an installation requires it. An updated driver does not establish that the app is current; old beta instructions also do not make Early Access a permanent requirement.

3

Enable the in-game feature

For a Super Resolution test, select DLSS upscaling in the game and record its quality mode. Save the settings, then exit fully to the desktop. An override cannot change the active DLSS model while the game is using a different upscaler.

4

Select the correct entry

Open Graphics → Program Settings and choose the game. Check the edition and installation path, particularly after moving a library or adding an executable manually. Refresh the list through its three-dot menu if detection looks stale.

5

Apply the intended preset

Scroll to Driver Settings → DLSS Override - Model Presets. Select Recommended, or use Custom to choose the relevant component’s preset. Click Apply. Revisit the entry to confirm the choice remains saved.

6

Relaunch and load a scene

Start the same installation normally and load actual gameplay. Confirm the in-game DLSS settings survived the restart. A title screen or a graphics menu is a poor place to decide what the gameplay renderer is using.

If the app cannot load the profile, use the settings retrieval fixes. Record that message separately from the override’s saved state; a warning in the optimization area is not a complete diagnosis of driver settings.

05 / Verify during gameplay

Read the model, then judge the result

Enable NVIDIA Overlay and open its DLSS statistics view:

Alt+ZStatisticsStatistics ViewDLSS

Use Alt+R to show or hide the configured statistics. Read the available model and override information for the component under test, and capture it alongside your in-game DLSS mode. That pairing is more informative than a screenshot of the app alone.

Two observations that mean different things

The expected model is reported

Activation is supported by runtime evidence. Next evaluate image stability, responsiveness, and performance in the same scene.

The readout is blank or N/A

The result is inconclusive. Check overlay availability and updates before declaring the override broken.

NVIDIA has documented statistics display fixes in its app release history. A missing readout can therefore be a reporting problem. Recheck after updating and restarting; if it remains unavailable, preserve the uncertainty instead of substituting an FPS guess.

Also compare the baseline model. If the game already uses the model you are selecting, a working override may produce no meaningful before-and-after difference.

06 / Isolate a genuine mismatch

If the saved preset and runtime model still disagree

Start with the affected installation

Check whether you are launching a different executable or edition from the one configured. If you previously installed a DLSS replacement, graphics wrapper, or preset-enforcement tool, restore the original setup using its removal instructions and the launcher’s file verification. Keep a record of your custom files so the comparison is reversible.

I would test the official game integration before combining multiple methods of selecting a model. Otherwise, a successful change still leaves you uncertain about which method produced it. Avoid renaming executables or forcing another game’s profile merely to make an unsupported option appear available.

Compare one other supported title

If available, repeat the same component check in a second game with confirmed override support. Success there points the investigation toward the first title’s profile or integration. Failure in both broadens the investigation toward shared app or driver state, although it does not identify the cause by itself.

For persistent problems across supported games, record your settings before considering an NVIDIA App reinstall. Reserve broad driver resets for evidence of a wider driver fault or a specific support recommendation. Repeatedly clearing caches does not answer which model the game loaded.

07 / Separate activation from performance

A working override can still be slower

Newer Super Resolution models are not a guaranteed FPS upgrade. NVIDIA notes that M and L impose a heavier cost on RTX 20 and 30 series GPUs, which lack native FP8 support. Model K can be the more practical balance on those cards.

COMPARE FAIRLY

Hold the workload steady

Use the same save, camera route, output resolution, quality mode, and Frame Generation setting. Look at motion and fine edges as well as still images. Judge whether the difference is useful during ordinary play.

CHECK A SEPARATE SYMPTOM

Watch for gradual slowdown

If performance deteriorates as the PC warms up even with the override disabled, investigate PC overheating checks. That pattern needs a temperature and cooling check beyond preset selection.

These independent DLSS image comparisons offer useful visual examples. Their January 2026 setup instructions predate subsequent app changes, so use the current controls described above when reproducing your own comparison.

If the change introduces distracting artifacts or an unacceptable performance cost, restore the preferred preset. To test the game’s native behavior, choose Use the 3D application setting, apply, and relaunch. Returning to a global setting may instead reintroduce a global override.

Frequently asked questions

Does the DLSS DLL version prove the override failed?

No. A filename or file version describes the file on disk, not a complete report of the active model and driver override. Use runtime information. Replacing DLLs simply to obtain a newer version number adds another variable to the diagnosis.

Why does the game still say DLSS Quality?

Quality is a rendering mode, not a model letter. A model override can change the reconstruction model while leaving that mode selected. You should not expect the game’s menu to rename Quality to M or L.

Should a model override enable Frame Generation?

A Super Resolution model change does not activate Frame Generation or grant support for it. Check the separate feature, GPU eligibility, and game integration if generated frames are your actual goal.

Make the unresolved case reproducible

If a supported preset still fails, send NVIDIA feedback with the GPU, Windows version, app and driver versions, game edition, selected preset, DLSS mode, Ray Reconstruction state, and overlay screenshot. Include whether another supported game works.

The useful report is specific: “This component reports this model after these saved settings and a relaunch.” That gives support a repeatable case and gives you a clear condition to retest after an update.