Frame generation for any RTX card, a third engine, and one zip for bug reports
Frame generation on RTX 20 and 30 (OptiScaler engine)
OptiScaler ships AMD's FSR 3.1 interpolation in every package this tool installs, so 2X frame generation in a game that never had it is four ini keys. A new tick on the OptiScaler engine — Frame generation (2X, FSR 3.1 inside OptiScaler) — any RTX card — turns it on. D3D12 games only (every FG output there is a D3D12 component). Turn the game's own frame generation off; expect added latency.
Found on the way: the RTX 40 multi-frame tick on the OptiScaler route did nothing from v0.13.12 to v0.13.14. AdaMfgUnlock lives under [DLSSG], not [FrameGen], and the key was being written where OptiScaler never read it. Fixed, and from wilsjo2's v0.8.3 the key exists only in the -rtx40-mfg package, which the tick now selects. The same release ships two zips; both pickers used to take the first one, which would have handed the MFG build to everyone.
Also: the ini was only patched on a fresh install. Changing Model Resolution or any tick on an already-current OptiScaler install wrote nothing. It does now ("already current, settings applied").
Third engine: ReShade + standalone AIO (experimental)
kibblerz's DLSS5 ReShade AIO is one ReShade add-on that runs neural rendering, DLSS super resolution / DLAA and frame generation itself — for 64-bit games with no DLSS of their own, that is the first route here to FG at all. Pick the third card or --engine=aio: ReShade, the AIO zip beside the exe (manifest-tracked, Remove takes it out), the model, and nvngx_dlss.dll + nvngx_dlssg.dll when the game has none. In game: turn the game's own upscaling, anti-aliasing and frame generation off, run windowed, Home → Add-ons → Standalone DLSS-NR + SR. Switching a game back to the ReShade engine removes the AIO first. Not run in a game by the author — report what you see.
NVIDIA's DLLs from NVIDIA
nvngx_dlss.dll and nvngx_dlssg.dll now come from NVIDIA/DLSS at its newest tag (byte-identical to the mirror at 310.9.1 — checked); the mirror is the fallback. The RTX 40 MFG add-on (v0.9) validates the frame-generation provider and refuses unknown builds (#90) — Install now places a provider it accepts, moving a game's own to .original, and Remove puts it back.
Save report — one zip for issues
New Save report button (--report): dlss5oneclick-report-<game>-<time>.zip on your Desktop with the folder listing, the last 4 MB of ReShade.log / dlss5-feed.log / OptiScaler.log / REFramework's log, the inis this tool wrote, every version sidecar, and Diagnose's output. Attach that instead of hunting for files.
Diagnose and detection
- Neural Upstream installs were diagnosed against the wrong add-on's log and reported "never registered" / "no NGX call" over a healthy log (#86). Diagnose now reads
[NRPRE]lines on their own terms: registered, hooked, network created, evaluated, or stopped at a menu. - Graphics API override: a dropdown beside the DLSS-mode one (Auto / Force DX11 / Force DX12),
--api=dx11|dx12on the command line, for when "API unknown, assuming DX12" is wrong. - Access denied on Install or Remove now says what it is: a game under Program Files or a read-only folder — run as administrator, take ownership, or move the game.
- OptiScaler "update available" that never cleared (#88): the pre-SR fork's tags were compared against the stable build's. The manifest records which repo an install came from.
- 32-bit exes are back in the picker (#89) — 64-bit is a preference, not a filter.
- Remove takes dgVoodoo out when this tool placed it (#91); a DX9 game that would not start no longer stays that way after Remove.
- The status line no longer overlaps the Install button (#94); the classic-build tick says it also covers "worse image than before".