Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues launching many Windows games through Proton #6982

Closed
2 tasks done
xxkfqz opened this issue Jul 31, 2023 · 5 comments
Closed
2 tasks done

Issues launching many Windows games through Proton #6982

xxkfqz opened this issue Jul 31, 2023 · 5 comments

Comments

@xxkfqz
Copy link

xxkfqz commented Jul 31, 2023

Compatibility Report

System Information

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

Symptoms

Proton Experimental (also 8.0-3 and 7.0-6) stopped launching many Windows games like BattleBit, SuperPower 2, Wings of Vi but runs Quake.

PROTON_LOG=1 %command% outputs:

vulkaninfo

Reproduction

  1. Enable Steam Play
  2. Select "Proton Experimental"
  3. Launch Windows game
@kisak-valve
Copy link
Member

Hello @xxkfqz, it looks like your system is configured to use AMDGPU-Pro. Can you test how these games behave with mesa/RADV? Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

@xxkfqz
Copy link
Author

xxkfqz commented Aug 1, 2023

@ipr
Copy link

ipr commented Aug 1, 2023

Steam client seems to have a random issue. Closing the client and starting it again (without rebooting) seems to solve it sometimes.

For me this appears after computer has been rebooted (which doesn't happen often). Restarting Steam seems to fix whatever it is.

@xxkfqz
Copy link
Author

xxkfqz commented Aug 1, 2023

@kisak-valve Yep, removing AMDGPU-Pro drivers makes all games run again

@xxkfqz xxkfqz closed this as completed Aug 1, 2023
@kisak-valve
Copy link
Member

Looking over the diagnostics information, looks like VK_ICD_FILENAMES was forcing the Vulkan loader to only try a single option, and since that didn't exist it broke all Vulkan render paths.
Set variable: https://gist.github.com/xxkfqz/d0d5bf178a81ac14ab0b18b640c974ea#file-runtime-diag-L62
Driver ICD does not exist: https://gist.github.com/xxkfqz/d0d5bf178a81ac14ab0b18b640c974ea#file-runtime-diag-L328-L337
Broken 32 bit Vulkan: https://gist.github.com/xxkfqz/d0d5bf178a81ac14ab0b18b640c974ea#file-runtime-diag-L77-L90
Broken 64 bit Vulkan: https://gist.github.com/xxkfqz/d0d5bf178a81ac14ab0b18b640c974ea#file-runtime-diag-L189-L202

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants