Diagnostic order
- Confirm the game launches in offline, borderless mode.
- Check that ReShade itself loaded and opens with Home.
- Open the Add-ons tab and confirm the neural-rendering add-on is listed and enabled.
- Read
ReShade.logand, when used,dlss5-feed.log. - Confirm the log reports feature creation and frames delivered.
- Only then compare the visual result and performance.
DLSS 5 panel is missing
The add-on may be disabled after a crash, removed by antivirus, placed next to the wrong executable, or blocked as an unsigned DLL. Check the actual game executable rather than a launcher or bootstrapper.
WAITING FOR NGX MODULES
The ReShade add-on loaded, but the expected NVIDIA libraries did not. Confirm that the DLSS/Streamline set is beside the same ReShade.ini used by the game, enable Load DLSS Libraries for a non-DLSS game, and check that the correct API was selected. Disable NVIDIA App overrides during diagnosis. Swapper users should also verify that the correct native-DLSS or Feeder backend was selected in the DLSS 5 Swapper route guide.
Duplicate or conflicting RenoDX add-ons
The current ShortFuse instructions use renodx-dlss.addon64. A separate community branch uses renodx-dlss5.addon64. Do not load both: remove the older/different file or rename its extension so ReShade cannot load it. Confirm the active filename in ReShade.log.
“No effect files found”
On a game using its own DLSS, this can be expected because the relevant control is an Add-on, not a ReShade shader effect. Check the Add-ons tab. On a Feeder route, missing effects are a real problem because the feed and motion-vector shaders are required.
“Hooks armed — no DLSS create seen”
The add-on loaded but did not observe the expected NGX lifecycle. The wrong API, a stale Bridge, a game that never activated its own DLSS, or an incompatible add-on build can cause this. Confirm API detection and update the Bridge from its original release page.
Installed, but nothing changes
Confirm the feature is evaluating real frames rather than merely registered. Use a same-frame toggle and monitor frame time. A subtle output can be normal; increasing intensity should not replace verification.
Black screen, freeze, or crash
Turn neural rendering off before changing resolution or display mode. Prefer borderless. Remove duplicate proxy DLLs and avoid loading two engines that both expect the same dxgi.dll position. The documented ShortFuse build currently does not support Vulkan, OpenGL, or 32-bit DX9; using an unsupported API can fail before the panel appears.
Large FPS drop
Neural rendering adds a full inference pass. RTX 40 carries a meaningful cost, while RTX 20/30 community paths can be much heavier. Disable V-sync during diagnosis so a small threshold crossing does not appear as a hard 60-to-30 FPS step.
Ghosting, soft UI, or altered colors
Feeder quality depends on estimated motion vectors and depth selection. Incorrect vectors can smear motion, while processing UI with the scene can soften text. HDR, AutoHDR, RTX HDR, and game tone mapping can also stack incorrectly.