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

Steam Compatability layers not showing up in gamescope #490

Open
ScarsTRF opened this issue Mar 4, 2025 · 4 comments
Open

Steam Compatability layers not showing up in gamescope #490

ScarsTRF opened this issue Mar 4, 2025 · 4 comments

Comments

@ScarsTRF
Copy link

ScarsTRF commented Mar 4, 2025

I ran into a few games that need Proton-GE and other few packages, but when installing them into steams extraCompatPackages they ONLY show up inside of desktop mode through either GNOME or KDE, if I try and access them inside of a gamescope session, they don't seem to persist if set or show up anywhere.

Here is how I've installed my compatibility packages:

  programs.steam = {
    enable = true;
    remotePlay.openFirewall = true;
    dedicatedServer.openFirewall = true;
    extraCompatPackages = [
      proton-ge-rtsp
      proton-ge-custom
    ];
  };

Both of the packages you see here are pulled using builtins.fetchTarball and have worked on my desktop, laptop, and in desktop mode

Here's a clip of the list of compatibility layers on gamescope:

GAMESCOPE.mp4

Here's another clip of me checking the compatibility layers on Desktop Mode:

DESKTOP.mp4
@K900
Copy link
Contributor

K900 commented Mar 4, 2025

This is kind of a weird side effect of how things are implemented, programs.steam overrides the Steam package, but so does Jovian, so we end up with two copies of Steam, one with your overrides and one with ours. I'm not really sure what a good solution would be here...

@ScarsTRF
Copy link
Author

ScarsTRF commented Mar 4, 2025

Since you mentioned that programs.steam is a separate copy, I might remove that. Though wouldn't it just be possible to add another option under jovian.steam to do the same thing? Like jovian.steam.extraCompatPackages?

@sg-qwt
Copy link
Contributor

sg-qwt commented Mar 7, 2025

Why can't jovian override on top of programs.steam.package, and jovian gamescope always use the final steam as input. This also affects #373 btw

@K900
Copy link
Contributor

K900 commented Mar 7, 2025

It's complicated because other packages in the overlay depend on Steam, so we would have to somehow backpropagate the Steam changes.

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