RADV: Menu static/artifacts in Doom Eternal
Description
Doom Eternal (in Steam via Steam Play) has lots of white or red/blue static and artifacts all over the screen, both in the menu and in game, making it unplayable. See screenshot below.
I tried playing with various graphical settings, but the only one that seemed to have any noticeable effect was the "Present from Compute" option. Disabling that cleared up the static on screen, but also immediately froze the menu. This also causes the game to hang before displaying the menu when restarted, you have to remove the r_presentFromAsync option from the config file to fix that.
Screenshots/video files
Steps to reproduce
For me, happens just by starting the game once reaching the menu screen.
I am using the following launch options in Steam, but the same issue happens with no options: %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
System information
System: Host: haswell Kernel: 5.13.12-200.fc34.x86_64 x86_64 bits: 64 compiler: gcc v: 2.35.2-4.fc34 Desktop: GNOME 40.4
tk: GTK 3.24.30 wm: gnome-shell dm: GDM Distro: Fedora release 34 (Thirty Four)
CPU: Info: Quad Core model: Intel Core i5-7500 bits: 64 type: MCP arch: Kaby Lake rev: 9 cache: L2: 6 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27199
Speed: 800 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] vendor: ASRock driver: amdgpu
v: kernel bus-ID: 03:00.0 chip-ID: 1002:7340
Device-2: Microsoft LifeCam HD-3000 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-9:3 chip-ID: 045e:0779
Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: ati,vesa
unloaded: fbdev,modesetting,radeon resolution: 3840x2160~60Hz s-dpi: 96
OpenGL: renderer: Radeon RX 5500 XT (NAVI14 DRM 3.41.0 5.13.12-200.fc34.x86_64 LLVM 12.0.1) v: 4.6 Mesa 21.1.7
direct render: Yes
Tested with Proton Experimental and Proton 6.3-6, same issues.
Further information (optional)
Does the issue reproduce with the LLVM backend (RADV_DEBUG=llvm
) or on the AMDGPU-PRO drivers?
Tested RADV_DEBUG=llvm, no difference in behavior.
Does your environment set any of the variables ACO_DEBUG
, RADV_DEBUG
, and RADV_PERFTEST
?
No