To reset DLSS Override, close the game, open its profile in the NVIDIA app, and return the relevant DLSS override controls to Use the 3D application setting or the equivalent application-controlled option. Check global settings too: an inherited global override can prevent a profile reset from giving you the baseline you expect.
This returns control to the game’s DLSS integration. It does not automatically restore a manually replaced DLL, remove a mod, turn DLSS off, or recover the settings from an older game patch. Start by identifying which of those outcomes you actually want.
Decide what “original game settings” means
There are three different baselines worth separating before changing anything. A game can use its own DLSS model while still running in Performance mode. It can also have application-controlled driver settings while loading a DLL you previously swapped.
Undo the NVIDIA app override. Keep your chosen in-game quality mode unless you also want to change it.
Undo a manual DLL replacement or modification separately, using a suitable backup or the launcher’s repair process.
My recommendation is to start with the driver controls if that is the only place you made changes. A narrowly targeted reset gives you a clearer answer than changing the driver, game configuration and installation together. If the problem disappears, you know which layer mattered.
For troubleshooting, “original” usually means the current game build’s unmodified integration. Recovering a particular older appearance may require the same game version and configuration; resetting an override cannot reverse a developer’s update.
Reset the game’s DLSS overrides in the NVIDIA app
Save your progress and exit the game completely before changing its profile. Take a screenshot of the existing DLSS settings first, especially if you experimented with several model presets. It gives you a record without requiring a broad profile reset.
- Open the NVIDIA app and select Graphics.
- Open Program Settings and choose the affected game. Check that the profile corresponds to the version or executable you actually launch.
- Scroll to Driver Settings and locate the available controls beginning with DLSS Override.
- For model presets, return any overridden DLSS components to the application-controlled choice. Check Super Resolution, Ray Reconstruction and Frame Generation individually when the interface exposes them separately.
- Return the Super Resolution override to application control as well. This matters if you forced DLAA, a quality mode or a custom rendering scale.
- Return the Frame Generation override to application control if you forced a multiplier or another generation mode.
- Apply the changes where prompted, then reopen the game.
NVIDIA’s DLSS override instructions explicitly identify the application-controlled option as the route back to the integrated models and Frame Generation feature set. Labels vary between releases, so match the function rather than expecting every screenshot to use identical wording.
I would inspect all available DLSS override entries rather than resetting only the one most recently changed. Otherwise, you might restore the model but leave a forced rendering mode active, making the result look like an incomplete rollback.
Check global settings before assuming the reset failed
NVIDIA app supports both global and per-game DLSS configuration. That makes a global preference another place to investigate when the same behaviour appears across several compatible games.
Open Graphics → Global Settings and inspect the DLSS controls. If your goal is an application-controlled baseline across your library, remove the forced global choices too. Record the original values before doing so, because this changes your intended configuration for other compatible titles.
If you want the override everywhere except one game, keep the global preference and choose an explicit application-controlled setting for that game where the interface permits it. Pay attention to any inherited or global indicator: using a global preference and using the game’s setting express different intentions.
Do not use a whole-profile restore as your first move simply because it sounds more thorough. A broad reset can disturb unrelated choices such as a frame limit or synchronisation preference. For this task, change the DLSS controls you can identify and preserve the rest until evidence points elsewhere.
Understand what the reset changes—and what it keeps
| What you changed | What to restore | What remains separate |
|---|---|---|
| Model preset | Application-controlled model selection | The game’s quality-mode selection |
| Forced rendering mode | Application-controlled Super Resolution | The game’s output resolution |
| Frame Generation override | Application-controlled generation behaviour | The in-game Frame Generation switch |
| Replaced DLL | Original file for the installed build | Driver profile preferences |
Resetting an override is not the same as disabling DLSS. If the game’s own menu still has DLSS enabled, the game may continue using it. That is expected when the goal is to restore the developer’s integration.
Likewise, application control does not mean “use the oldest model.” A game update can ship a newer integration. The baseline follows that installed version rather than a remembered screenshot from before the update.
Current NVIDIA app terminology also differs from older guides: newer releases use a Recommended model choice where older instructions referred to Latest. Neither should be treated as a reset label. For rollback, look for application control rather than a model recommendation.
If you swapped DLLs or installed a DLSS mod
A driver-setting rollback does not undo a file operation. If you replaced the game’s DLSS library yourself, handle that separately after restoring the NVIDIA app controls.
If you kept a backup, verify that it belongs to this game and the currently installed build before restoring it with the game closed. A backup from an older patch is not automatically the right baseline after the launcher updates the installation.
For a Steam installation, the supported verification route is Library → game Properties → Installed Files → Verify integrity of game files. Use this when you need Steam to check the installed content. Verification can take several minutes and should not be treated as a universal reset of personal settings.
For another launcher, use its documented repair or verification process. Before repairing a modded installation, preserve the mod configuration and backups you need: repairing official files may undo intentional replacements.
Restore a suitable original backup or repair the official files. Keep a note of exactly what was replaced.
Follow the mod’s removal instructions. Do not delete unfamiliar DLLs merely because their names look graphics-related.
I would not assume that a successful file check removed every added mod component. Checking official files and removing additional files are different jobs. If a mod has its own installer or manager, use that removal path and then verify the game if necessary.
Verify the reset with a controlled comparison
Launch the game again and inspect its own graphics menu. Keep the same output resolution, quality preset and scene while checking the result. If you also change ray tracing or the DLSS quality mode, a visual or performance difference will be harder to interpret.
The NVIDIA overlay can expose DLSS override status in supported situations. In the overlay’s Statistics settings, select the DLSS view where available; the configured statistics display can be toggled with Alt+R. Use the reported override status as supporting evidence rather than relying on an FPS counter alone. The detailed override verification guide explains how to compare the saved request with the active DLSS component.
Choose a reproducible symptom: an unstable outline, a specific ghosting trail, an unexpected rendering mode or a crash at a repeatable point. Compare that symptom after each completed change. An FPS increase or decrease by itself does not identify which model or file is active.
If the overlay does not expose useful DLSS information for this title, record what you can verify: saved profile values, the in-game options, the installed-file state and the result after relaunching. Do not interpret a missing overlay field as proof that an override is active or inactive.
If the game still looks different
First confirm that you edited the profile used by the running game. Multiple editions, alternate renderers or different executables can make a familiar game name an unreliable identifier. Check the launch target instead of repeatedly changing whichever profile appears first.
Next, ask whether another utility was used to configure the driver profile. If so, inspect and undo the changes through that utility’s documented controls. Reapplying settings from another tool can make troubleshooting across applications confusing; keep a single record of the intended baseline. If a saved choice actually changes after launch or exit, follow the sister site’s restart persistence checks to isolate the event that triggers it.
If the application-controlled values are saved and the installation is unmodified, reconsider the original assumption. An in-game setting or game patch may explain the difference. I would investigate that evidence before deleting configuration folders or reinstalling the graphics driver.
Stop once the baseline is restored. A driver cleanup or Windows reset is far broader than this task and makes it harder to preserve a useful before-and-after comparison.
Frequently asked questions
Does resetting DLSS Override turn off Frame Generation?
Not necessarily. Returning the driver override to application control lets the game decide. To disable Frame Generation itself, use the game’s own option where it is available.
Should I choose Recommended to restore the original model?
No. A recommended override is still a choice to override supported behaviour. Use the application-controlled option when your goal is the game’s integrated baseline.
Do I need to restart Windows?
Start by fully exiting and relaunching the game after applying the settings. If a setting does not appear to persist, close and reopen the NVIDIA app to inspect it before escalating to broader troubleshooting.
Will reinstalling the game reset everything?
Do not rely on it as a combined reset of game files, external driver preferences and personal configuration. Restore each affected layer deliberately; otherwise a lengthy reinstall may leave the relevant preference untouched.
Leave the game in control, then reassess
For a straightforward rollback, restore application control for the game’s DLSS overrides, inspect global preferences and relaunch. Only repair files if you actually changed them or have evidence of an installation problem.
Once the game runs with the intended baseline, decide whether the original symptom remains. Keep that baseline recorded before trying another preset. You will have a much more useful comparison than a sequence of changes with no clear starting point.