Two things: 32-bit games get an honest Diagnose, and Neural Upstream's preset can be set before launch.
32-bit games: Diagnose was reading the wrong ReShade log (#69)
On a 32-bit game (GTA IV, Max Payne, Spore…) the DLSS 5 add-on does not run in the game process. It runs under the 64-bit ReShade inside host64\, driven by dlss5-feed-host64.exe. Diagnose was reading ReShade.log from the game folder — the feeder's 32-bit ReShade, which never loads the add-on — so it always concluded:
FAIL: The DLSS 5 add-on never registered. renodx-dlss5.addon64 is missing from the game folder…
That fired on every 32-bit game no matter how healthy the install was. Now it reads the log that belongs to the add-on, names host64\ when the add-on is genuinely absent, and no longer reports "ReShade loaded into the wrong exe" when ReShade loaded into the host64 helper — which is exactly where it is supposed to load.
Neural Upstream: pick the strength preset in the tool (#68)
Choose Experimental — Neural Upstream and a HOW TRANSFORMATIVE dropdown appears, with the add-on's own five presets:
| preset | intensity | local tone | local structure | skin structure |
|---|---|---|---|---|
| Light | 0.45 | 0.55 | 0.25 | 0.15 |
| Moderate | 0.70 | 0.80 | 0.55 | 0.40 |
| Reference (default) | 1.00 | 1.00 | 1.00 | follow structure |
| Overdrive | 1.30 | 1.25 | 1.45 | 1.20 |
| AI slop | 1.80 | 1.60 | 2.00 | 1.90 |
Install writes the choice into ReShade.ini under [NRPreUpscale], where the add-on reads its settings at startup — so it is set before the game launches. Both the preset id and the four strength values are written, because the add-on reads them as separate keys and does not derive one from the other. The in-game overlay still works and still wins.
Note from the add-on's author: the strength parameters are forwarded and exposed, but it is not confirmed the network acts on them. Compare Light against AI slop and judge for yourself.
SHA-256 of dlss5oneclick.exe: 41b0ff80364d94f32a84bd698be9b752359d315571a053a857aeb581e4d4189f