DLSS 5 Swapper: No Effects Found or Missing Files

First distinguish an empty effects list from a missing component

The v2.2.0 documentation explains that No effects found can be expected in a native DLSS setup. Check the game’s native DLSS setting and the loaded Add-ons rather than installing a large shader pack to silence the message.

For ReShade / Feeder, the required effects and usable inputs matter. An empty or failed effect list there has a different meaning. Confirm your route using the component map.

Match the symptom to the file type

Symptom	What to inspect	Correct direction
Empty effects list on native route	Native DLSS enabled, correct consumer in Add-ons	Verify native evaluation; do not assume effects are required
Missing Feeder effect	Installed route, expected effect files and paths	Recheck the matched Feeder installation
Native add-on absent	Bitness, add-on-capable ReShade, consumer file	Repair the route’s component installation
A named model or runtime DLL missing	Exact filename, source package, version	Follow that component’s documented prerequisite
sl.common.dll or another game-supplied file missing	Game or component ownership and installation log	Verify the owning package, not a random DLL website
Read-only configuration warning	File permissions and configured path	Investigate separately from effect discovery

Save the exact message and path. “No effects,” “failed to load,” and “read-only” describe different failures.

Repair only the identified installation

Close the game. Check that Swapper targets the actual rendering executable and current API, and that its installation completed. Compare the files expected by that route with its installation record and official package. If files were quarantined, inspect the security alert and source-verification steps before deciding what to run.

When a route reinstall is required, follow the relevant release instructions and preserve _DLSS5_Backup. If switching routes, use Restore originals first. Do not manually combine new model files with an old consumer unless the component documentation explicitly describes that combination.

The Feeder documentation and current release table identify the relevant components.

Treat read-only warnings as a separate branch

Version 2.2.7 added a startup check for installed games’ ReShade.ini state, but issue 155 contains continued reports and configuration-specific discussion. A community path adjustment is not a guaranteed repair for every installation, and a later reinstall can change those files again.

Inspect the exact path and write permission. Do not delete backups or disable protection broadly just because one report did so.

Confirm the repair

Restart the same game and renderer. Confirm that the previously missing component loads, the relevant error is gone, and the expected route receives valid inputs. A disappearing warning alone does not prove the neural result is correct.

If loading succeeds but controls fail, continue with overlay diagnosis. If the game becomes unstable, restore the originals and return to the main diagnostic flow.