Use DLSS 5 Swapper in Games Without Native DLSS

What Feeder adds

A non-DLSS game does not make the native calls expected by a DLSS consumer. Feeder connects suitable ReShade inputs to a neural rendering consumer. Its operation therefore depends on the game, renderer, and usable depth and motion information. Copying a DLSS DLL into an arbitrary game does not provide those inputs.

Read the Swapper compatibility notes together with DLSS5-Feeder’s documentation. Feeder’s upstream abilities can extend beyond the routes currently exposed by Swapper.

Check the route before installing

Check	What to establish
Graphics card and driver	A documented combination for the chosen consumer; see the compatibility guide
Executable	The rendering executable, its folder, and whether it is 32-bit or 64-bit
API	The renderer currently selected by the game, not simply every API it can support
Runtime	Required Visual C++ runtime, including x86 for a 32-bit game where needed
Existing modifications	Any ReShade build, proxy DLL, or loader already using the same entry point

Swapper v2.2.7 bundles Feeder 0.15.1 and ReShade 6.8.0. Legacy DirectX routes can require dgVoodoo and bitness-specific bridging. Swapper’s current direct DX10 support must not be inferred from a newer upstream Feeder feature. See the compatibility conditions for these distinctions.

Install the ReShade / Feeder route

Close the game, select its actual executable in Swapper, and choose the ReShade / Feeder route that matches the active renderer. If a different Swapper route is already installed, restore it first. Let the application’s installer obtain the matched components; mixing individual files from unrelated bundles creates a different configuration from the documented one.

Launch the game and inspect the ReShade Home panel and its loaded add-ons or effects. Feeder needs its corresponding effects and input data. The compact Swapper F8 overlay is an additional control surface with narrower x64 DX11/DX12 requirements; its absence alone does not identify the underlying Feeder failure.

For Metal Gear Rising: Revengeance or Skyrim Special Edition, confirm the active API, bitness, and existing mods before choosing this route. If Skyrim already has ENB, use the coexistence checks. For Half-Life 2, the v2.2.7 release notes describe a detection correction for games sharing the name hl2.exe; check that the detected title is the game you intend to modify. In each case, validate the inputs and result below before treating the setup as working.

Check whether the inputs and result are usable

Use a scene with geometry at several distances and some camera movement. Check that depth corresponds to the scene and that the visual result remains coherent when moving, opening the HUD, or entering a menu. A shader loading successfully proves only that it loaded. Incorrect depth, unavailable motion data, black output, or severe artifacts mean the route needs further investigation.

Keep the scene and game settings fixed when comparing before and after. Do not report a working result solely because a control value changes or a frame counter moves. Use the performance measurement procedure to separate rendering cost from generated-frame output.

When to stop or restore

If expected effects are missing, use the missing-files guide. If installation completes but nothing connects, use the diagnostic entry page.

If the renderer is unsupported or you cannot establish valid inputs, close the game and Restore originals. Return to a working baseline before trying a different route. Emulator selection has extra steps; PCSX2 has its own checklist.