GitHub Issue

Wuthering Waves: black screen in async mode (UI visible), error in inline mode — RX 7900 XT (RDNA3)

Discovered On Sep 4, 2026

Primary Metric open

Environment GPU: AMD Radeon RX 7900 XT Driver: latest Adrenalin OS: Windows 11 (build 10.0.26200) Game: Wuthering Waves, DX12 Res: 2560x1440,running in fullscreen (borderless) mode DLSS-NR-on-AMD: v0.2.10 Issue On RDNA3 the overlay works, but the DLSS NR pass produces a wrong result: 1. Inline mode → the game errors / crashes. 2. Async mode → the 3D scene is a black screen, but the game UI renders correctly on top. Suspected cause: linear input color space mismatch Steps to reproduce 1. Install the proxy + `nvngx_dlssnr.dll` (310.8.0.0) correctly, then launch the game. 2. At the login screen, open the overlay and switch to Async mode, then log in and enter the game → black screen. 3. At the login screen, switch to Inline mode, then log in and enter the game → error after 2 minutes. Attachments `dlssnr_on_amd.log` attached (RDNA3 / gfx1100 run) Error screenshot (crash dialog shows DXGI_ERROR_DEVICE_REMOVED / DXGI_ERROR_DEVICE_HUNG at D3D12Resources.cpp:596) attached. [dlssnr_on_amd.log](https://github.com/user-attachments/files/31830136/dlssnr_on_amd.log)

View Raw Thread

Developer & User Discourse

KOPLAKMAL • Sep 5, 2026

so i do test on rx 9070 xt. but when i open clientshipping exe, it show fatal error. how you open the game?

CosmicDictator • Sep 6, 2026

Put the proxy DLLs and `nvngx_dlssnr.dll` in the same folder as `Client-Win64-Shipping.exe` (`Client\Binaries\Win64`), then launch the game by running `Client-Win64-Shipping.exe` directly — that works for me.

Also, on my multi-GPU system this fixed the async-mode black screen: in Device Manager, disable every display adapter that is NOT used for the game, and keep only the GPU the game actually renders on enabled.

KOPLAKMAL • Sep 6, 2026

hoo okay will try, arigathanks🙏

but i still dunno what is 'proxy DLLs' means

KOPLAKMAL • Sep 6, 2026

still not launch the game and throw fatal error Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000018

0x00007ffa26f95007 amdhip64_7.dll!UnknownFunction []
0x00007ffa26fd01b4 amdhip64_7.dll!UnknownFunction []
0x00007ffa2738f878 amdhip64_7.dll!UnknownFunction []
0x00007ffa2738f933 amdhip64_7.dll!UnknownFunction []
0x00007ffa26fd1f17 amdhip64_7.dll!UnknownFunction []
0x00007ffa26f0a9bc amdhip64_7.dll!UnknownFunction []
0x00007ffa26eff270 amdhip64_7.dll!UnknownFunction []
0x00007ffa26f1637b amdhip64_7.dll!UnknownFunction []
0x00007ffa26bcce2b amdhip64_7.dll!UnknownFunction []
0x00007ffa26bd9f8f amdhip64_7.dll!UnknownFunction []
0x00007ffa26b493b7 amdhip64_7.dll!UnknownFunction []
0x00007ffa26d9d056 amdhip64_7.dll!UnknownFunction []
0x00007ffa26d746b3 amdhip64_7.dll!UnknownFunction []
0x00007ffa26d72323 amdhip64_7.dll!UnknownFunction []
0x00007ffa26eca508 amdhip64_7.dll!UnknownFunction []
0x00007ffa916f08a0 version.dll!UnknownFunction []
0x00007ff...

danielblnc • Sep 7, 2026

Does this still happen on v0.2.15?