[BUG] 2D menus are invisible in certain games
Describe the bug A clear and concise description of what the bug is.
2D surfaces like menus are invisible while in a 3D scene in certain games:
- Project Cars 2
- Assetto Corsa Competizione
- Automobilista 2
- Assetto Corsa EVO
The menu is visible for a split second then disappears. Moving my head, I can hear that different menu elements are getting selected, but I just can't see them. The issue happens in multiple games, leading me to believe it's related to SteamVR and / or Proton.
To Reproduce Steps to reproduce the behavior:
- Launch Project Cars 2
- Start any race
- Wait until 3D scene loads (interior of the car)
- Try to start the race via the menu
Expected behavior A clear and concise description of what you expected to happen.
Menu is visible, can start a race
System Information (please complete the following information): Please use the latest Steam beta client and SteamVR beta for your bug reports!
- CachyOS rolling (Linux 6.17.1-2-cachyos Mon, 06 Oct 2025 23:26:58 +0000 x86_64 GNU/Linux)
- Radeon RX 9070 XT / Ryzen 5700X3D
- Meta Quest 3 HMD
- Steam Link connection between PC and HMD
- Steam client version (build number or date): 1759461205
- SteamVR version: 2.13.6
- Distribution (e.g. Ubuntu): CachyOS
- Steam runtime diagnostics: [generate via Help -> Steam Runtime Diagnostics in the Steam client] steam_runtime_info.log
- Steam and SteamVR logs: [generate by running this command in a terminal
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs] steam-logs.tar.gz - Minidumps: [run the following command:
tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps] steam-minidumps.tar.gz
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
I have tried downgrading Proton, using different forks of Proton, but not downgrading SteamVR to the non-beta version, since only beta supports VRLink on Linux so far.
Update: Works with ALVR and SteamVR non-beta 2.12.14, so it seems like it's definitely a SteamVR issue.