Update DLSS 5 Swapper and Check Game Components

Record the current state

Before updating, write down the Swapper version, target game build, active API, installed route, driver, and known component versions. Save diagnostics if the update is intended to fix a problem. Keep _DLSS5_Backup; deleting it makes rollback harder, not cleaner.

The release history is the source for changes. A repository commit date is not a new application release. Our download page identifies the package version checked for this guide.

Update the desktop application

Close the game and read the new release’s update instructions. Use the application’s update check or obtain the appropriate installer or portable package from the developer’s release page. If replacing a portable copy, close its running process first. Do not interpret a failed update check as proof that you already have the newest version.

Version 2.2.4 improved update-check failure messages; later releases also changed tray behavior. Confirm the version shown after reopening the application, rather than assuming that closing its window ended the old process.

Check installed game components separately

A new executable on the desktop does not prove that every game folder has received new add-ons. Review the release’s component changes and any explicit instruction to reinstall the selected route. Close the game before performing that installation, retain its recovery files, and read the final status.

A concrete example is the v2.2.5 native-route regression: that release installed the Multipass consumer in the ordinary native route. The v2.2.6 notes correct the selection and instruct affected users to install again on the same route. Merely updating the application leaves the previously installed game files to be checked.

The v2.2.8 update is the clearest current case. Its component table moved DLSS5-Feeder from 0.15.1 to 1.17.0 and the ordinary RenoDX consumer from v4.7 to 6.5.3. The notes do not say that games installed earlier are upgraded automatically, so check the consumer named in each game’s log or panel. Reinstall a game still on v4.7 on the same route, with the game closed: on driver 616.64 or newer, that old consumer is what faulted. Other routes use different consumers; do not replace all of them with the same DLL.

Verify one game first

1. Confirm the application version and the intended game-level route.
2. Start the same executable and renderer used before the update.
3. Check component loading, overlay connection where applicable, and a fixed scene.
4. Compare stability and image behavior without changing the driver and several settings at the same time.
5. If this game is working, repeat the check for the next installed game.

Use the component guide to identify the parts. If F8 still fails, use the overlay checks; an update cannot guarantee that every reported overlay problem is resolved.

Recover if the update introduces a problem

Save the new diagnostics before restoring. Close the game, select Restore originals, and verify its baseline. If the button is greyed out although the game still holds modded files, use v2.2.9 or later, which fixed that case (issue 325). A previous release may be useful for a controlled comparison, but choose it from actual release history and follow its route requirements. Do not mix old and new components at random.

The restoration guide explains recovery when the application has already been removed. A useful bug report includes both the last working configuration and the changed version, rather than only “updated and stopped working.”