Proton actually works, and three things stop misleading you
DLSS 5 under Proton — the recipe, from a log that reached 3,600 frames
A reporter got DLSS 5 running on Elden Ring under Proton 10.0-4 with no launch options at all (#76). The whole fix is a copy of Microsoft's real d3dcompiler_47.dll beside the game executable:
[feed] d3dcompiler_47.dll: .../ELDEN RING/Game/d3dcompiler_47.dll (not System32, but it accepts cs_5_1 -- fine)
[feed] feature ready: 2560x1440 DLAA, flags=74 (SDR MVLowRes DepthInverted AutoExposure)
[feed] 600 frames: feed CPU 0.58 ms/frame | frame interval 17.78 ms (56.3 fps) | stalls 0
Diagnose now hands you that recipe instead of the generic "install a compiler" advice, and WINEDLLOVERRIDES="d3dcompiler_47=n" is offered only as a fallback for a prefix that still loads Wine's copy.
And it no longer tells you to delete the file that makes it work. The warning about a game-shipped d3dcompiler_47.dll used to say "rename it". Under Proton that file is deliberate, and once the recipe works the compile-failure line is gone from the log — so the warning now says to leave it alone there.
"is a combination measured to fail" — on the build that passes
Every build of the DLSS 5 add-on carries the same embedded FileVersion: 0.2026.0828.0517 in 4.55 and 4.70 alike, differing only in size (1,694,720 against 1,732,608 bytes). The Feeder's host reads that version, calls them all "v4.6 engine", and warns about a driver combination the classic build is not part of — the build its own text recommends. Two reporters read that as proof the pin had not taken.
Install now records the release tag beside the add-on, and diagnose reads it: pinned to the classic build, the warning is reported as nothing to do; otherwise it says to run Install, which pins it automatically. Upstream inconsistency tracked in DLSS5-Feeder#90.
RTX 40 multi-frame generation: the tick sticks, and says 5X too
- Selecting a game reset the tick, so re-running Install on a game that already had
renodx-mfgunlock.addon64quietly dropped it. The tick now comes from the game folder itself — the add-on being there is the setting, and Remove clears it. - The label said 3X/4X/6X. 5X exists; it now reads "3X and above, up to 6X".
Confirmed by a reporter since v0.13.13: Avatar: Frontiers of Pandora at 6X with nvngx_dlssg.dll 310.9.0.