Graphics Driver Issues

Graphics Driver Issues

This page quickly summarizes graphics driver quirks and issues present in GPU drivers by different manufacturers.

» AMD (Proprietary)
» Intel (Proprietary)
» NVIDIA (Proprietary)

» AMD (Mesa)
» Intel (Mesa)
» NVIDIA (Mesa)

» Hall of Fame (List of fixed issues)

---

AMD (Proprietary)

OpenGL

• No known problems at this time

Vulkan

• MSAA with sample shading disabled does not work on NAVI when using Vulkan
  » Workaround implemented: Yes (automatic)
  » Reported: Yes
  » Note: Forcefully enabling sampleRateShading for all pipelines and calculating the minimum ratio works around this problem

• Regression on amdvlk/adrenalin causing visual corruption and driver crashes on FBO loops
  » Workaround implemented: No
  » Reported: Yes
  » Note: Disabling the usage of VK_IMAGE_LAYOUT_ATTACHMENT_FEEDBACK_LOOP_OPTIMAL_EXT works around the issue at the cost of violating the Vulkan specification

Intel (Proprietary)

OpenGL

• GLSL compiler is very broken
  » Workaround implemented: No
  » Reported: No
  » Note: Intel proprietary OpenGL drivers are unsupported by RPCS3 due to their poor state.

• Unsupported. There are likely other issues as well...

Vulkan

• Driver crashes with VK_ERROR_FRAGMENTATION
  » Workaround implemented: No
  » Reported: No
  » Note: Intel proprietary Vulkan drivers are unsupported by RPCS3 due to their poor state.

• Missing shaderStorageImageMultisample Vulkan feature support on Intel iGPUs
  » Workaround implemented: Yes, Anti-Aliasing (MSAA) will be automatically disabled by RPCS3
  » Reported: Yes, on 2020-08-03. Feature unsupported by hardware.
  

• Unsupported. There are likely other issues as well...

NVIDIA (Proprietary)

OpenGL

• Floating point precision issues with Nan/Inf values
  » Workaround implemented: Yes (automatic)
  » Note: This is not a driver bug as it can be considered implementation-defined behavior.

Vulkan

• Floating point precision issues with Nan/Inf values
  » Workaround implemented: Yes (automatic)
  » Note: This is not a driver bug as it can be considered implementation-defined behavior.

• Unexpectedly slower performance (-25%) when replacing VK_FORMAT_B8G8R8A8_UNORM with VK_FORMAT_R8G8B8A8_UNORM
  » Workaround used: None
  » Reported: Yes, on 2020-10-30. No replies.
  

AMD (Mesa)

OpenGL

• No known problems at this time

Vulkan

• No known problems at this time

Intel (Mesa)

OpenGL

• crocus Driver (Legacy hardware): No known problems at this time.
• iris Driver (Modern hardware): No known problems at this time.

Vulkan

• Missing shaderStorageImageMultisample Vulkan feature support on Intel iGPUs
  » Workaround implemented: Yes, Anti-Aliasing (MSAA) will be disabled automatically by RPCS3
  » Reported: Yes, on 2020-08-03. Feature unsupported by hardware.
  

NVIDIA (Mesa)

Vulkan

• No known problems at this time

---

Hall of Fame

List of reported graphics driver bugs that are now fixed. We'd like to thank the developers who fixed these!

• CRITICAL: OpenGL no longer renders any game on any AMD GPU! (Windows)
  » Affected drivers: Radeon Software Adrenalin 19.12.1, 19.12.2, 19.12.3, 20.1.1, 20.1.2, 20.1.3
  » Workaround used: None, not possible
  » Fixed on: Radeon Software Adrenalin 20.1.4

• High: AMD RADV driver crash when using ACO due to unusual control flow (Mesa)
  » Affected drivers: Mesa 20.0.2 and earlier
  » Workaround used: None, using RADV with LLVM instead of ACO
  » Fixed on: Mesa 20.0.3

• High: Incorrectly rendered Vulkan shaders due to broken SPIR-V optimization on NVIDIA
  » Affected drivers: NVIDIA Windows 452.06 and earlier, NVIDIA Linux 450.56.06 and earlier
  » Workaround used: None
  » Fixed on: NVIDIA Windows 452.28, NVIDIA Linux 450.56.11

• High: Driver instability leading to crashes on NVIDIA Windows
  » Affected drivers: NVIDIA Windows 526.XX
  » Workaround used: None
  » Fixed on: NVIDIA Windows 527.37

• High: glMultiDrawArrays is broken on the old AMD OpenGL Windows driver
  » Affected drivers: Radeon Software Adrenalin 22.6.1 and older
  » Workaround used: Yes - this seems to be undefined behavior in the spec. The gl_VertexID propagation behavior across MultiDrawArrays is not defined, i.e whether it should continue incrementing of reset to 0 on a new instance. However, due to the comparison with a loop of [first, count] and implied functional equivalence, this may be interpreted as a bug. Either way, RPCS3 provides a workaround using index lookups.
  » Fixed on: Radeon Software Adrenalin 22.7.1

• High: Performance regression on AMD Windows with very high submit and flip latency per frame
  » Affected drivers: Radeon Software Adrenalin 23.3.2, 23.4.1, 23.4.2
  » Workaround used: None
  » Fixed on: Radeon Software Adrenalin 23.4.3

• High: Graphical corruption on AMD Windows with RDNA3 GPUs when upscaling games
  » Affected drivers: Radeon Software Adrenalin 24.1.1 and older
  » Workaround used: None
  » Fixed on: Radeon Software Adrenalin 24.2.1

• High: Vulkan depth buffer comparison does not work on AMD Windows
  » Affected drivers: TBD
  » Workaround used: None
  » Fixed on: Radeon Software Adrenalin 25.11.1

• High: Primitive restart is broken, this is a GCN hardware bug that affects both proprietary and FOSS drivers
  » Affected drivers: Mesa 18.2.3 and older
  » Workaround used: Yes, 185c2177@rpcs3/rpcs3 (automatic)
  » Fixed on: Mesa 18.2.4, eae8f49f@mesa/mesa

• Medium: Missing descriptorBindingUniformBufferUpdateAfterBind support
  » Affected drivers: Mesa 21.2.3 and older
  » Workaround used: Yes, an alternative (slower) code path
  » Fixed on: Mesa 21.2.4

• Medium: OpenGL's glGetTexImage/glGetTextureImage/glGetTextureImageEXT do not work with immutable textures if pack/unpack byteswap is requested on any AMD GPU (Windows)
  » Affected drivers: Radeon Software Adrenalin 19.4.2 and earlier
  » Workaround used: Manually byteswap texel data (now removed)
  » Fixed on: Radeon Software Adrenalin 19.4.3

• Medium: Unnecessary implicit subpass dependencies caused performance regression on AMD RADV (Mesa)
  » Affected drivers: Mesa 20.0.0, 20.0.1
  » Workaround used: Explicitely injecting null subpass dependencies (now removed)
  » Fixed on: Mesa 20.0.2

• Medium: vkGetQueryPoolResults returns incorrect values when VK_QUERY_RESULT_PARTIAL_BIT is set on NVIDIA (Windows)
  » Affected drivers: NVIDIA GeForce 442.59 and earlier
  » Workaround used: Keeping NVIDIA driver from using partial results (now removed)
  » Fixed on: ~NVIDIA GeForce 442.74

• Medium: Missing shaderStorageImageMultisample Vulkan feature support on GCN1 GPUs (RPCS3 crashes if MSAA is enabled)
  » Affected drivers: Mesa 20.0.8 and older
  » Workaround used: None (disable MSAA on affected drivers)
  » Fixed on: Mesa 20.1.0

• Medium: Vertex explosion when using ACO shader compiler on AMD RADV (Mesa)
  » Affected drivers: Mesa 20.2.1 and older
  » Workaround used: None, not possible. Using the older shader compiler instead of ACO, which was the default prior to Mesa 20.2
  » Fixed on: Mesa 20.2.2