... Install AMDVLK VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command% RADV_DEBUG=invariantgeom %command% RADV_DEBUG=nodcc %command% Don ...

... Install AMDVLK > > VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command% > > RADV_DEBUG=invariantgeom %command% > > RADV_DEBUG=nodcc %command% > > Don ...

... In the mean time, you can workaround it with `RADV_DEBUG=nocompute %command%` or `RADV_DEBUG=nongg %command%`. Let me ...

... In the mean time, you can workaround it with `RADV_DEBUG=nocompute %command%` or `RADV_DEBUG=nongg %command%`. Let me ...

... Would be interesting to confirm that RADV_DEBUG=nongg on the Deck also fixes the GPU hang. Also if ...

Does RADV_DEBUG=nohiz help?

Does RADV_DEBUG=zerovram help?

RADV_DEBUG=zerovram shouldn't be necessary because in Vulkan, VRAM allocations aren't supposed to the zeroed but ...

@NTMan Does RADV_DEBUG=nodcc fix it?

I assume RADV_DEBUG=nofastclears fixes the rendering issue?

> I assume RADV_DEBUG=nofastclears fixes the rendering issue? Unfortunately not

Unfortunately, using `RADV_DEBUG=nohiz %command%` doesn't fix it :[

Does it still happen if you add RADV_DEBUG=nohiz to launch options?

RADV_DEBUG=llvm removes the flickering surfaces but creates a different problem where terrain surfaces are blackish. So the ...

> RADV_DEBUG=llvm %command% Ok, i can confirm…this is working. Nice :)

I have no issues on AMD, when I force llvm instead of aco: `RADV_DEBUG=llvm %command%`

... Right click the game Select `Properties` In the `General` tab, select `SET LAUNCH OPTIONS` Enter `RADV_DEBUG=llvm %command ...

... RADV_DEBUG=nodcc` without PROTON_LOG=1 its not working thanks ! and also its not worked with full option `RADV_DEBUG ...

... This occurs with no custom launch options. "RADV_DEBUG=nodcc,nodisplaydcc %command%" also does not change the behavior. [System ...

@laichiaheng does `RADV_DEBUG=zerovram` work around the graphical glitches in D3D12 mode?

... Setting `RADV_DEBUG=nohiz` does get rid of it again, but I've noticed some artifacts on the pillars ...

With the new patch (`1.03.00`) setting `RADV_DEBUG=nohiz` crashes the game on startup for me. Did ...

... Setting the option `RADV_DEBUG=nohiz` also seems to fix the issue for me, allowing me to set the ...

It seems RADV_DEBUG=nohiz "fixes" the shadows flickering. I will look into a fix.

@PoorPocketsMcNewHold Does it also happen if you launch the game with `RADV_DEBUG=zerovram %command%` ?

There was a working workaround posted in GitLab RADV bug thread: ` RADV_DEBUG=syncshaders %command%` completely stops the RADV ...

... Looks like some people reported that RADV_DEBUG=syncshaders would fix the crashes/hangs, maybe you can try this ...

... So `PROTON_LOG=1 PROTON_NO_ESYNC=1 RADV_DEBUG=syncshaders %command%` is working fine for me, `PROTON_NO_ESYNC=1 RADV_DEBUG=syncshaders %command ...

... Also PROTON_NO_ESYNC=1 RADV_DEBUG=syncshaders in launch option remove the stuttering during game for me (i5 3570/RX580 ...

... 1 RADV_DEBUG=syncshaders %command%``` ```PROTON_NO_ESYNC=1``` to prevent prevents constant stuttering after 30+ mins of gameplay ```RADV_DEBUG=syncshaders ...

Crashes with RADV and `RADV_DEBUG=llvm` too. So not ACO specific, far as I can tell.

@rKsanu2MMYvypWePtQWM Are you still able to reproduce this issue on your R9 380 *without* RADV_DEBUG=nocompute?

> Trying right now with old method of shader pre-caching and RADV_DEBUG=nogpl same issue with shader pre ...

> @rKsanu2MMYvypWePtQWM Are you still able to reproduce this issue on your R9 380 _without_ RADV_DEBUG=nocompute? The video ...

Isnt it possible to enable these as launch parameters? e.g `radv_legacy_sparse_binding=true RADV_DEBUG=nodcc,zerovram %command%`

... radv_legacy_sparse_binding=true radv_zero_vram=true RADV_DEBUG=nodcc %command% Regarding blank pictures, that issue might have been fixed? I haven ...

... the issue for me (set in heroic). **RADV_DEBUG=llvm** OR **RADV_DEBUG=llvm %command%** if your using steam. I ...

... I have WINEDLLOVERRIDES=winedbg.exe=d for online, also got RADV_DEBUG=zerovram and DXVK_HUD=fps,frametimes,memory but ...

See above, poor performance was due to RADV_DEBUG=hang and DXVK 1.10.3 is from stable proton ...

Also @NTMan, I see in one of your d3d12 logs that you have RADV_DEBUG=hang enabled, I assume ...

... Without `RADV_DEBUG=hang` FPS is reached expected 60FPS. Unfortunately, despite the fact that the GPU has a margin ...