-
-
Notifications
You must be signed in to change notification settings - Fork 671
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
Lutris 0.5.17 Fails to Correctly set the Vulkan ICD Loader #5439
Comments
That's an issue for me too, but the games are working fine with vulkan. |
I think you may be affected by a bug I just turned up; where Lutris does not fall back to lspci if Vulkan is present, but fails to work with your GPU. You could try to download the latest master, run the |
the error in the terminal still shows for me with master version (don't understand why no wrapped text in code, maybe new firefox update, sorry):
|
Could you bring back the Vulkan ICD Loader option? |
We absolutely DO NOT WANT anyone on this planet or in the whole galaxy to use AMDVLK or AMDGPU-Pro for gaming. We will do everything in our power to prevent people from using those. |
You're being ironic, right? Using any of them when necessary is an advantage, see this issue on Mesa as an example. And anyway, it's a useful option, I don't see anything against it.. |
No I'm not being ironic. I've messed up more than one system trying to get AMD proprietary drivers working. If anything, I would add detection of AMDGPU Pro in Lutris to show a warning users to switch back to mesa. We have good free and open source drivers for AMD GPUs while AMD offers piss poor support for their proprietary alternative, we can do without. |
I was having stutters for a few months and I realized just today that I was running on |
After upgrading to .17 I get the following error when launching lutris
I disabled my internal GPU from the bios as seen here
And launching
vulkaninfo
myself works fineDowngrading to 0.5.16 fixes the issue and I can see the correct loader in the configuration (it's also the only option)
The text was updated successfully, but these errors were encountered: