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

gamescope only works with com.valvesoftware.Steam.CompatibilityTool.Proton-GE #138

Open
un-couteau opened this issue Jan 14, 2024 · 9 comments

Comments

@un-couteau
Copy link

cs2 does not want to work with gamescope, although with gamescope-git from AUR there are no problems with it

image

image
although the proton games seem to be working fine.

also gamescope works with Half Life, but does not work with CS 1.6.

@ColinKinloch
Copy link
Collaborator

I've got a hunch SDL3 is defaulting to wayland try either:

  • the --expose-wayland for gamescope
  • or use the environment variable SDL_VIDEODRIVER=x11.

@un-couteau
Copy link
Author

SDL_VIDEODRIVER=x11 I tried, but it didn't help (I think it's only relevant for SDL2)

--expose-wayland didn't help me either.

Looking at the logs, I saw this:
image

I also tried mesa-git.

@un-couteau un-couteau changed the title SDL3 doesn't work Gamescope doesn't work Jan 15, 2024
@orowith2os
Copy link
Collaborator

SDL_VIDEODRIVER should be working with any SDL version, there's no reason for them to try anything new. The SDL3 FAQ also says SDL_VIDEODRIVER.

@un-couteau
Copy link
Author

as mentioned #6 the error is the same, in carx I used proton-ge from flatpak, but for cs2 this method will not help.

I have no ideas how to fix it in my head

@ColinKinloch
Copy link
Collaborator

Could you change the issue title to something a bit more descriptive like: "Counter-Strike 2 maps window outside gamescope"

@un-couteau un-couteau changed the title Gamescope doesn't work gamescope only works with com.valvesoftware.Steam.CompatibilityTool.Proton-GE Jan 19, 2024
@Eckoa
Copy link

Eckoa commented Feb 21, 2024

Just to add a bit to this, Ive found that i simply cant get flatpak gamescope working with any game not just CS2 when using it with steams own proton with Flatpak Steam (everything works on native). I have tried on a fresh install of Arch, Fedora, and Tumbleweed. It works with the proton flatpaks but those have all been abandoned between May last year and January this year making this tool effectively unusable for Flatpak Steam unless you want to use the unmaintained flatpaks which will stop working eventually or you build your own.

Seeing as this tool is used fine by other flatpak applications and the current abandoned state of the proton flatpaks it might be wise to add a note to the readme that this tool currently will not function as expected for steam flatpak as the previously mentioned issue #6 which has been around for 2 years now seems to suggest this is a limitation with flatpak at the moment in regards to Steam.

@zastrixarundell
Copy link

I don't see how it #6 as any other game launcher using proton doesn't have an issue. Heroic works, Lutris works. Should this be reported to the steam flatpak itself?

@Eckoa
Copy link

Eckoa commented Apr 7, 2024

I don't see how it #6 as any other game launcher using proton doesn't have an issue. Heroic works, Lutris works. Should this be reported to the steam flatpak itself?

steam uses sub sandboxing for the proton versions you download through steam which the other flatpaks dont do. This is part of how proton works and is what is causing the issues with gamescope as far as i read in the other issue and the original issue from the original steam gamescope flatpak. It works if you use the proton flatpaks but those are abandoned now which makes for problems.

This is not something that can be solved by the steam flatpak or this gamescope flatpak as it is a core flatpak issue (maybe even an X11 issue in regards to flatpak)

This sort of issue is known about already in the steam flatpak

@devurandom
Copy link

This is not something that can be solved by the steam flatpak or this gamescope flatpak as it is a core flatpak issue

Is there a flatpak issue tracking this?

I found flatpak/flatpak#5116 mentioning XWayland (which #6 and #199 mention as the cause of this issue), but it seems not immediately related to Gamescope or Proton. flatpak/flatpak#5167 mentions Gamescope, but it does not seem to relate to sub-sandboxing.

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

6 participants