protonscr

DXVK HUD shader compilation message persistent despite no performance issues

dxvkclosed
doitsujin/dxvk#5801 · opened 2026-07-20 by JavaDaVinci · updated 2026-07-20 · 6 comments · github
JJavaDaVinci 2026-07-20 github

Description:
Since updating to Proton-cachyos-11.0-20260702, the DXVK HUD is spamming the "Compiling shaders..." notification on-screen indefinitely while playing Assassin's Creed IV: Black Flag.

Image

steam-14930299295893553152.log

System Information:

OS/Kernel: CachyOS (Linux 7.1.3-2-cachyos)

Proton/Wine: Proton-cachyos-11.0-20260702-slr

Game: Assassin's Creed IV: Black Flag

Issue Details:
The game runs perfectly fine, but the DXVK HUD overlay is constantly spamming shader compilation messages. This behavior was not present in previous versions of Proton. It appears to be enabled by default in this release, causing constant visual obstruction during gameplay despite the game being stable.

Please provide a way to disable this forced HUD spam or revert this change in future builds.

Mmbriar 2026-07-20 github

DXVK never enables any HUD element by default. If it's enabled, you either did it yourself, or it was set by Proton-cachyos or whatever launcher you use.

Ddoitsujin maintainer 2026-07-20 github

Please provide a way to disable this forced HUD spam or revert this change in future builds.

There already is a way, it's called not setting the fucking env var.

Guess I'm going to remove that too, we still have the dxvk.conf option.

Mmbriar 2026-07-20 github

It's proton-cachyos that sets DXVK_HUD=compiler in their proton launch script btw. So you can go complain there.

Ttannisroot 2026-07-20 github

Please provide a way to disable this forced HUD spam or revert this change in future builds.

There already is a way, it's called not setting the fucking env var.

Guess I'm going to remove that too, we still have the dxvk.conf option.

Please don't remove the compiler option, it's very useful in Overwatch

JJavaDaVinci 2026-07-20 github

Please provide a way to disable this forced HUD spam or revert this change in future builds.

There already is a way, it's called not setting the fucking env var.

Guess I'm going to remove that too, we still have the dxvk.conf option.

I didn't set any env variables !

Ddoitsujin maintainer 2026-07-20 github

Well, yeah, apparently proton-cachyos did as explained above (and they already reverted the change so it'll just disappear on its own at some point).

Either way, DXVK_HUD="" (i.e. empty string) should work around this for now as well. But yeah, this isn't our fault.

Launch options