AMDNR 0.3.5.8R4
Neural Rendering for AMD Radeon, built on OptiScaler. Paired launcher: AMDNR Launcher 0.3.5.57.
Video
https://youtu.be/PGMeJsf4utY — existing 0.3.5.8 overview, not an R4 validation video.
Changes in 0.3.5.8R4
- Updated the OptiScaler integration to the 2026-10-28 upstream snapshot, retaining AMDNR's Neural menu and runtime integration. Includes updated XeSS/XeFG, latency routing, resource ownership and Vulkan provider paths.
- Corrected swapchain resize lock ownership and null ResizeBuffers1 handling.
- Corrected FG resize completion checks: a stale event or device-removal fence value is not accepted as successful GPU completion.
- Deferred RR runtime ABI probing out of DLL discovery to avoid re-entrant discovery; ABI validation is retained when creating the feature.
- Upscaler selection is available before the first active upscaler feature, and the pending choice is saved.
- The AMDNR-authored Mochi worker uses the system shader compiler for input-guide preparation. The author's runtime is unchanged.
- Launcher 0.3.5.57 distinguishes unknown first-install inventory from genuinely missing Exact/Lossy providers. The authored worker overlay is preserved through installation, repair and runtime switching.
- Existing stock AMD FSR 4.1.2, Exact/Lossy and separate experimental RDNA 2/3 options remain available. These are separate provider choices, not a new universal GPU-support claim.
Install or update
Close the game and update through AMDNR Launcher. Keep the selected runtime installed as a separate component. Enable a supported upscaler in the game's graphics settings and load into gameplay. Some model/runtime changes require restarting the game. For manual installation, preserve original game files and avoid duplicate proxy installations.
Neural runtime/model, upscaling, ray reconstruction and frame generation are separate settings. Existing menu languages remain under Interface; ReShade and NR shortcut settings remain in Game Settings.
Files
AMDNR-v0.3.5.8R4.zip: main mod, dependency providers, licences and documentation.AMDNR-Launcher.exe: paired launcher 0.3.5.57.- Runtime and Anywhere packages remain separate. This release does not promise new runtime archives or an Anywhere replacement. No NVIDIA runtime DLLs or NR weight files belong in the main mod package.
Validation
Release x64 mod compilation/link completed using MSVC 14.44.35207 after the five targeted corrections. The five focused CPU groups passed. All 15 broader mod CPU groups and five targeted groups passed. Launcher checks passed: 90 Core and 35 App tests. The paired launcher Release publish and authored-worker build succeeded. The previous LIBCMT conflict warning was corrected in this build; existing C4250 warnings remain. No new GPU/game result is claimed.
Known limits
The update addresses reproduced code defects. It does not close every player's crash report or certify all games.
- Cyberpunk R3, Forza and Witcher sessions ending around RR discovery: the re-entrant probe correction is included; matching in-game confirmation is still required.
- Cyberpunk crashing only when started through PLAY (
C00000FDin_nvngx) remains a separate open case. - Where Winds Meet: the worker shader-preparation correction is included; an in-game result is still needed.
- GTA V Mochi settings persistence remains open. Bootstrap coverage does not prove settings are saved.
- Crimson Desert: the upscaler-selection barrier is addressed; availability of native DLSS is not certified.
- Kingdom Come: Deliverance and GTA III reports with no completed NR output remain open.
- Darktide XeFG's reported failure after about 20 minutes needs a matching dump. A rejected destroy does not make its context safe to reuse.
- Metro Anywhere minimization and its separate Magpie crash are not resolved by updating the main mod DLL.
- F1 spoofing, CONTROL status reports, TLOU Part II, Flight Simulator and remaining game-specific crashes still need matching sessions and confirmation.
- XeFG foreground/background pacing, ghosting, high-interleave latency and motion artifacts remain under investigation. No measured FPS improvement or general ghosting cure is claimed.
No new GPU or game qualification was performed for this release assembly. CPU checks and a successful DLL build do not establish visual correctness or gameplay stability. Experimental Exact/Lossy remains separate from stock AMD providers; compatible hardware and driver requirements still apply.
Reporting a problem
Use COLLECT LOGS after reproducing the issue. Include game, GPU, runtime/model, upscaler, FG, NR placement and interleave settings. For ghosting/flicker include a short moving-scene video; share crash dumps privately.
Credits
DLSS-NR on AMD by Daniel Blanco (danielblnc); lmxxf by Kien (MIT); mochizuki by mochizuki0323 (MIT); TheAutomatic integration lineage; HelixSR by lonewolf0622; AMD FidelityFX, Magpie and OptiScaler contributors. Experimental FSR shader overrides by zgauthier2000 (cyboman), GNU GPL v2 or later; modified AMD shaders. See the included licence notices. Copyright (c) 2026 3zwr1 (AMDNR). Not affiliated with AMD or NVIDIA.
Support
The fifth correction requires the paired AMDNR-authored worker overlay; Launcher 0.3.5.57 installs and preserves it. Updating only OptiScaler.dll does not apply that worker correction. The author's runtime DLL remains unchanged.
Clear AMDNR data
Settings includes Clear AMDNR data for the fixed LocalAppData folders AMDNR and AMDNR-SupporterPreview. After confirmation, the launcher exits and the helper removes their settings, cache, logs and installation records. Game mods and game backups outside those folders, the launcher executable and shortcuts remain. A removal receipt remains outside the cleared folders under AMDNR-Uninstall.
This removes installation records without removing game mods: keep any game backups you need, and uninstall game mods through their normal route before clearing records if that is your intention. The isolated removal helper passed 16 checks. Launcher tests passed: 90 Core and 35 App, including 11 Clear AMDNR data checks and WPF binding/Cancel coverage. Publication has not yet been verified.