-
Notifications
You must be signed in to change notification settings - Fork 260
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
Steam pressure vessel might be a futur problem for MangoHUD #523
Comments
The executable isn't the problem afaik.The problem are the Vulkan Layers and libraries. |
There should be some technical restrictions under this decision I understand. Anyway, thank you for your feedback, I have renamed the ticket anyway now to make it more clear there is a bug in MangoHUD with Steam Pressure Vessel, and it should be more search friendly like that :) Steps to reproduce :
Notice the following error is shown
Attempting to create a symbolic link of
The only way I have found to fix was to copy |
If you use recent proton versions, you should use |
Ho thank you I didn't know this trick :) |
From #369 (comment). |
Hello guys,
Firstly, thank you for your work on MangoHUD this is a great project for the linux community :)
I wanted to have your attention on a possible issue, that you possibly haven't caught yet because it requires to run a Windows game under Proton of Steam for Linux, with the Steam Client Beta update with MangoHUD enabled.
I have opened the following issue here because I believe this is something the Valve's devs have to consider
ValveSoftware/steam-runtime#408
To resume briefly the problem, Steam's pressure vessel redirects every request made to the directory
/usr/bin/
to the following one/pressure-vessel/usr/bin
So any executable present in
/usr/bin/
but NOT in/pressure-vessel/usr/bin
, will fail the C/C++ call topopen()
, for instanceglxinfo
but the issue does not limit only to this executable, taking into accounts that pressure vessel can do this can probably save you from futur problemsLet me know if you need much informations
The text was updated successfully, but these errors were encountered: