-
Notifications
You must be signed in to change notification settings - Fork 72
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
Disabling Gamescope Gamescope not found #1137
Comments
I'm not sure if GameScope Flatpak works with SteamTinkerLaunch. Do other Flatpak tools work? The Flatpak sees very little testing compared to the official Steam Client. I don't use Flatpak Steam so I'm not sure if it's expected to work. |
The GameScope dependency check is as straightforward as running GameScope is not listed as an add-on for Steam Flatpak on Flathub. Are you sure you got one that is used as an Add-On? There is a GameScope Flatpak as a VulkanLayer but it is not an Add-On for the Steam Client, so I am not sure if it is available by default for the Steam Client. There used to be a Steam Client Add-On for GameScope, but it is archived now (and it looks like historically it had issues with any Proton version that used the Steam Linux Runtime, which Flatpak'd Proton add-ons did not). Does replacing |
Okay, it seems like this is all to do with the Steam Linux Runtime. You can try disabling the Steam Linux Runtime from SteamTinkerLaunch to see if it fixes the issue, but this may cause crashes as you are disabling the container that the game is intended to run inside of. If War Thunder passes a Steam Linux Runtime you will need to ignore the Steam Linux Runtime coming from the game as well. This may work with some games and not others, and system updates may break your game! Games are intended to run inside of the Steam Linux Runtime. When not using the Steam Linux Runtime, games are running against the libraries on your system, which may not be fully compatible with your game, resulting in either failures to start up (if they are too old/too new) or crashes (they may be compatible enough to start up but may cause crashes later in gameplay). The root cause of this whole issue is that you cannot use GameScope inside of games/tools using the Steam Linux Runtime. See these issues:
If running If War Thunder requires Steam Linux Runtime 3.0, you'll have to manually set it in Steam's So this is a known issue with Flatpak GameScope that is being tracked, and is almost entirely out of their hands as per flathub/org.freedesktop.Platform.VulkanLayer.gamescope#6. Disabling the Steam Linux Runtime from SteamTinkerLaunch (and disabling the Steam Linux Runtime coming from the game itself) may resolve this problem, but could introduce others. I am going to close this as this is not a SteamTinkerLaunch bug, but I will note this on the GameScope wiki. Please feel free to comment if disabling the Steam Linux Runtime resolved this issue for you, as once I finally get around to making a good Steam Linux Runtime wiki page, I can include this caveat on there as well. |
Looking at the log again, it seems the native Steam Linux Runtime 1.0 with AppID
The final outgoing start command also does not include the Steam Linux Runtime.
This means sadly there may be no workaround. It does seem overall like you can't use the Flatpak GameScope with Flatpak Steam based on the above linked issues. There could be other sandboxing-related issues preventing this from working. |
System Information
Issue Description
Installed gamescope via Flatpak and wanted to use it with Steamtinkerlaunch. When I start a game there is a Message Warning - disabling 'USEGAMESCOPE' because 'gamescope' was not found
Logs
steamtinkerlaunch.log
The text was updated successfully, but these errors were encountered: