protonscr

GTA 4: Severe rendering artifacts (black cars) on RDNA2 Windows using DXVK 3.0

dxvkclosed
doitsujin/dxvk#5732 · opened 2026-06-26 by sanjiamca · updated 2026-06-26 · 6 comments · github
Ssanjiamca 2026-06-26 github

Software information

  • Game: Grand Theft Auto IV (GTA 4)
  • Issue: After upgrading to the new DXVK 3.0, severe rendering artifacts appear specifically on vehicles. The interiors and certain geometry of the cars are rendered completely black (missing shaders/materials). The issue was not present in older DXVK versions (e.g., 2.7.1).
  • Settings: Standard in-game settings. MSAA is disabled. No external graphical mods (like ENB) are causing this.
  • Screenshot: Image

System information

  • GPU: AMD Radeon RX 6800
  • Driver: 26.6.2
  • OS: Windows 11
  • Wine version: N/A (Running natively on Windows)
  • DXVK version: 3.0

Apitrace file(s)

Log files

Ddoitsujin maintainer 2026-06-26 github

Can we please have a trace? I don't want to have to play GTA 4 for god knows how many hours to get to the same spot, just to find out that it's most likely an AMD driver bug anyway. Keep in mind that the RDNA1/2 driver is practically unsupported.

The parts of the game that I can easily test are fine on RADV and Nvidia.

Ssanjiamca 2026-06-26 github

https://drive.google.com/file/d/1TNPThsVW5WcpC9E6aZeyWEGkwco7andJ/view?usp=sharing

You might be right—I was experiencing some crashes with DXVK version 2.7.2. There are issues with the 32-bit version of DXVK on AMD systems; I looked into this on Gemini and noticed that there were no issues at all with the AMD version 25.10.2.

https://docs.google.com/document/d/1znEVjJJ3hz8Hs496B9W6UrFiDHAKcXcsK5m-oFZKtWk/edit?usp=sharing

I tried to troubleshoot the issue with Gemini; as you said, it's most likely a driver issue.

Ddoitsujin maintainer 2026-06-26 github

Getting the good old "You need access" on the Google Drive link.

Ssanjiamca 2026-06-26 github

Getting the good old "You need access" on the Google Drive link.

I fixed the links.

Ddoitsujin maintainer 2026-06-26 github

Thanks. Turns out there's a bug with legacy float emulation (which we don't use on RADV/Nvidia), so DXVK_CONFIG="d3d9.floatEmulation=Strict" should work around this for now.

Need to evaluate if we can use the strict path on AMD by default these days without losing perf.

Ssanjiamca 2026-06-26 github

Thanks. Turns out there's a bug with legacy float emulation (which we don't use on RADV/Nvidia), so DXVK_CONFIG="d3d9.floatEmulation=Strict" should work around this for now.

Need to evaluate if we can use the strict path on AMD by default these days without losing perf.

Adding “d3d9.floatEmulation = strict” to dxvk.conf completely solved the problem—thank you very much.

Launch options