protonscr

EDID colorimetry parsing failure causes white flickering in DirectX 8 apps on AMD RX 6600 XT / Wayland

protonclosed
ValveSoftware/Proton#9624 · opened 2026-03-28 by GarrettHJ · updated 2026-03-28 · 2 comments · github
GGarrettHJ 2026-03-28 github

System Info:

GPU: AMD Radeon RX 6600 XT
GPU Driver: 26.0.3 (amdgpu)
GE-Proton Version: GE-Proton10-34
OS: Arch Linux
Desktop: KDE Plasma (Wayland session)
Monitor: BenQ ZOWIE XL LCD (BNQ model 32639, manufactured week 7 of 2024)
Launch method: Lutris 0.5.22 with GE-Proton via UMU launcher

Issue:
On every launch, the following errors appear in the log:
err: wsi: parseColorimetryInfo: Failed to get parse edid.
err: DXGI: Failed to parse display metadata + colorimetry info, using blank.
This causes white flickering during right-click viewport panning in the Warcraft 3 World Editor (a DirectX 8 application running through DXVK D3D8).

What is affected:
Warcraft 3 World Editor — white flickering during right-click pan

What is NOT affected:
World of Warcraft (DirectX 11) — no flickering
Warcraft 3 Reforged — no flickering

Additional info:
The application is launched through Lutris, not Steam. The Battle.net launcher is configured as a Wine/Proton game within Lutris, with the WC3 World Editor running as a child process of the Battle.net launcher.
The EDID data is fully readable at the system level. Running edid-decode confirms the monitor communicates correctly with the OS. The colorimetry parsing failure appears to be specific to how Proton reads the EDID, not a system level issue.

The issue only manifests in the DirectX 8 rendering path — modern DirectX titles handle the blank colorimetry fallback gracefully, but the older D3D8 pipeline does not.

EDID decode output:
Display Product Name: 'ZOWIE XL LCD'
Manufacturer: BNQ
Model: 32639
Display Range Limits: 40-144 Hz V, 30-167 kHz H, max dotclock 350 MHz

Mmbriar 2026-03-28 github

The flickering in DX8 applications is with 100% certainty unrelated to the harmless EDID error message.

Kkisak-valve maintainer 2026-03-28 github

Hello @GarrettHJ, you're presenting an issue with a third party utility, run with a third party build of Proton from a third party launcher. I think it would be better to pursue this on the DXVK issue tracker since there's not much that a Proton dev can do with this feedback.

Proton versions