R9 fixes and verification limits

• Native FFX contexts created through AMDNR now stay on AMDNR's path when a native host relays a later call on them. Targets the Uncharted Anywhere 0xC000041D crash at FG teardown; not yet confirmed in the game.
• FG stability: re-entrant resizes from the FG owner are skipped, FG resize and present share a bounded lock, and ForceBorderless window changes for windows owned by another thread are posted instead of called directly.
• Native DLSS-G MFG (Phantom Blade Zero reports): timing re-arms on 2X to 4X changes, menu DLSS-G changes no longer replay on the presenting thread, a count change applies to the batch in flight, native 2X keeps its interleave hold and slow-line stalls re-arm. New [DLSSG-PHASE] and [DLSSG-BOOT] log lines. Pacing is not confirmed fixed in the game.
• lmxxf: a spike guard steps down one quality tier, once, after a stall of 4 s or more; the host HIP stream priority can be switched; rebuilt streams are logged.
• NR quality: new NRBRIGHT and RESCEIL ceilings for lmxxf warped history and residual edits. Both are off by default (opt-in). FFX reset reads are initialised.
• VRAM: NeuralHub VRAM ownership is tracked and FG steps down under pressure (kill switch DiagNoNhFgStepDown). Re-entry guards for dlss_d/RR probes, Metro DXGI spoof downgrade and bounds-checked IAT parsing.
• Qualification: FSR4 patched-model rule, fakenvapi QueryInterface locking and unknown-id handling, NeuralHub 0.8.0 RDNA 2 gate now evaluates the described adapter (CPU tests only), Model B exchange 64-bit sizes and a watchdog race fix.
• GTA V: the legacy menu and hotkeys are wired to the NeuralHub host's FSR output; not yet confirmed in the game.
• Launcher 0.3.5.63 displays AMDNR 0.3.5.8R9. Anywhere no longer loops minimising exclusive-full-screen games, never raises the host above the game's GPU priority class, and installs the separate lmxxf runtime when the Anywhere window uses lmxxf. Reports include ReShade.ini and AMDNR_BFI.ini and surface start-up crashes (Application Error 1000, amdnr_crash.log). The game picker offers an outside exe as a separate game, shows AMDNR files without an install record and warns when GPU spoofing is on for metro.exe.

These changes passed the production build, CPU regression tests, host contracts and a native startup fixture. None of them has been tested in an actual game for this release. Crash, pacing and image-quality fixes need fresh reports with COLLECT LOGS to be confirmed.

Previous release: R8 (0.3.5.8R8, Launcher 0.3.5.62)

• Fixed two public swapchain entrypoints that could return an existing XeFG swapchain to a different FG owner. Ordinary same-owner preservation remains enabled; actual game MFG presentation still needs verification.
• Fixed fresh-install provisioning of the shared DLSS host when DLSS services are selected with NR off, lmxxf or mochizuki. Service dependencies are resolved independently of the NR runtime choice; the selected NR runtime/model and native FG choices are preserved.
• Improved repair of missing/corrupt shared-host dependencies and the generated index. A valid installed host remains usable when its download package is unavailable.
• Preserved unchanged lmxxf NR settings byte-for-byte during repeat installation/repair instead of rewriting matching profile entries.
• Corrected readable-depth resource retirement and per-slot fence certificates in the AMD NR bridge. These are targeted lifetime fixes; the reported RE9 hang is not confirmed resolved in the game, and cross-queue scratch/history overlap remains under investigation.
• Corrected native FFX provider/context ownership and a verified native-host Anti-Lag 2 routing path. These changes are not proof that the E-Day shader-compilation crash or MFG pacing reports are resolved.
• Fixed repeated logging of one cached update-check error in the overlay. Added bounded native MFG state diagnostics without an extra SDK query.
• Launcher 0.3.5.62 displays AMDNR 0.3.5.8R8. R7 named reports and previous release changes are retained.

CPU regression tests demonstrate installation/repair behavior and resource/state contracts. A successful build or accepted FG option does not prove SR/RR output, actual generated-frame presentation, or an in-game crash fix. E-Day/PBZ MFG stutter, AL2 stalls, and remaining game-specific crashes require fresh reports and actual game validation. Experimental Runtime Agent performance work is not included.

AMDNR 0.3.5.8R9 Public View

Neural Rendering for AMD Radeon, built on OptiScaler. Paired launcher: 0.3.5.63.

Video

https://youtu.be/PGMeJsf4utY — existing 0.3.5.8 overview, not an R9 validation video.

Retained R5 changes

• Fixed startup crashes caused by applying menu colours before the ImGui context exists.
• Corrected RR discovery and late-load GPU capability queries that could re-enter the loader or wait on each other.
• Reject NGX providers that forward their exports back into AMDNR, while allowing recovery to a valid provider.
• Resolve existing module handles and loader caller/diagnostic policy before waiting for GPU discovery.
• Added custom DLSSG provider support: custom/<name>/dlssg/<dll>, with menu selection, saved settings and the active provider in the overlay.
• Extended file discovery for Phantom Blade Zero's steam directory layout.
• Launcher: validate lmxxf packages before replacing a working installation; preserve NR on/off, quality and independent SR/FG choices during profile restoration and runtime recovery.
• Mochi settings now use per-installation storage shared consistently by the launcher, menu and authored worker. Updates preserve other keys and reject unreadable settings instead of silently restoring stale choices.
• The authored worker uses a writable working directory and defers cleanup until its process exits and the job is idle. The runtime author's core files remain unchanged.
• Clear AMDNR data now removes the AMDNR-Uninstall helper workspace after successful cleanup. Game files outside the fixed LocalAppData product folders remain untouched.

Retained features

AMDNR Neural controls, menu languages, SR/RR/FG separation, ReShade controls, FSR 4.1.2 and the separate Exact/Lossy experimental choices remain. Includes the earlier R4 swapchain/resize, FG completion and shader-preparation corrections, plus the October 29 OptiScaler FFX SDK 2.4/custom-provider, XeSS mask, BeamNG and XeFG detection updates. They are retained changes, not new performance claims.

Install / update

Close the game, update AMDNR Launcher to 0.3.5.63, then update AMDNR for the game to 0.3.5.8R9. The paired authored worker and launcher fixes are required; replacing only OptiScaler.dll does not apply all changes. Keep your selected runtime installed separately. Save settings and restart where requested.

For custom FG providers, place a compatible replacement DLL under custom/<name>/dlssg beside OptiScaler, select it in FG Nvngx / FG Nvngx Replacement, save and restart. If multiple DLLs are present, nvngx_dlssg.dll takes precedence. Provider availability does not guarantee compatibility with every game or GPU.

Use COLLECT LOGS after reproducing a problem. Include game, GPU, runtime/model, upscaler, FG and NR placement/interleave settings. For visual artifacts include a short moving-scene video. Send dumps privately.

Files

• AMDNR-v0.3.5.8R9.zip: mod, paired authored worker, dependencies, licence notices and documentation.
• AMDNR-Launcher.exe: Launcher 0.3.5.63.
• SHA256SUMS.txt: hashes of the published files.
  Runtime and Anywhere packages remain separate. No NVIDIA DLLs or NR weights are included in this main mod package.

Known limits

These corrections address reproduced code defects; they do not certify every game or close every report.

• Phantom Blade Zero DLSS MFG pacing/timeouts remain under investigation. Neither the R5 directory-discovery fix nor the R9 DLSS-G MFG timing changes establish a pacing fix.
• S.T.A.L.K.E.R. 2 artifacts/ghosting require a controlled scene comparison and remain unresolved.
• F1 25's recorded R4 menu-theme crash is covered by the code correction; in-game acceptance and separate spoofing/driver crashes remain unconfirmed.
• Cyberpunk native FSR FG/AL2 and Phantom Blade Zero FSR FG need fresh R9 player confirmation. Flight Simulator and other game-specific failures remain under investigation.
• Long-session Darktide XeFG failures, foreground/background pacing, high-interleave latency, remaining ghosting and other game-specific reports are not claimed fixed.
• Launcher 0.3.5.63 stops the Anywhere exclusive-full-screen minimise loop; Metro Anywhere still needs player confirmation. The separate capture-host crash is outside this update. Existing Runtime/Anywhere packages stay separate.
• Loader paths involving unknown NVAPI callers and some FSR4/custom RDNA 2 capability paths, and worker deferred/concurrent/resize scenarios, are not fully qualified.
• No general FPS improvement, image-quality guarantee or new universal GPU compatibility claim is made. Stock FSR, Exact/Lossy and experimental options remain distinct.

Credits

DLSS-NR on AMD by Daniel Blanco (danielblnc) · lmxxf by Kien (MIT) · mochizuki by mochizuki0323 (MIT) · built on OptiScaler (GPL-3.0). HelixSR by lonewolf0622; TheAutomatic integration lineage; AMD FidelityFX, Intel XeSS and other dependency authors. Experimental shader overrides by zgauthier2000 (cyboman); see included licences. Copyright (c) 2026 3zwr1 (AMDNR). Not affiliated with AMD or NVIDIA.

Support

https://ko-fi.com/3zinr