Packaging Request: GameScope #162562
Comments
Krutonium
added
the
0.kind: packaging request
|
For those interested, it's available in the NUR: https://github.com/nix-community/nur-combined/blob/master/repos/dukzcry/pkgs/gamescope.nix. |
|
I can take care of porting the NUR derivation to nixpkgs and becoming the official maintainer. Just need a few weeks to understand the codebase a bit before committing to it. |
Are you still interested in doing that? Would love to see this in nixpkgs :) |
|
I read on NixOS's discord that ValveSoftware/gamescope#380 is a blocker. |
|
Yeah, that issue kinda upset me. I've been accompanying its progress but not being able to use controller for gamescope games suck. I do intend to free up some time to work on this. The NUR package was very oudated and not so well written at the time I checked it out, so I'd most likely would have to refactor it, which would take some effort. |
|
Oh nice, that helps a lot. |
|
I did it this way as a shortcut. It would probably be best to have an "updater" script next to the derivation that builds a |
|
Of course, yes. I think it'd be sufficient to make gamescope dependent on the output paths instead of the subproject build result; just like any other dependency. Were you able to make gamescope work from within Steam (as in: |
|
I've only used gamescope to run the new steamos interface, so games were in gamescope since steam itself was in gamescope. I haven ot tried any other kind of use. I tested it nested (within X11) and directly off of KMS. |
|
I've tried prepending games in steam with If anyone knows how to debug this, I'd be happy to help. |
|
Add |
|
Meant to say I also added the |
|
I tried
tested with intel GPU and nvidia dedicated GPU on NixOS unstable For the intel GPU, sometimes there are corruption in the image, using |
|
I tried to use it in Steam by putting logs |
|
Check the stdout/err log, it's probably the xwayland issue. |
|
I'm able to use the flatpak gamescope with few problems (doens't work well with the vanilla proton, but it works with the recent versions of proton-ge just fine apparently) |
|
FWIW, I have to use the patch mentioned here to get it to work on the Intel chip (the Nvidia works fine without it though, in my optimus setup): |
|
Oh nice! |
|
I tried to run the nixpkgs gamescope to open the 0ad game to test it out, and it failed on swaywm: |
|
It's the xwayland issue as I suspected. I think we should have a separate issue on that. |
|
I don't think that's our issue, there is an upstream issue as well as a PR to potentially address it: |
|
When I dug into this a while ago, it was due to it not being able to start its own xwayland session because a directory was owned by nobody rather than root or the current user inside our container IIRC. |
I'm hitting a problem when attempting to use the package that sounds similar. It attempts to use the ~ > ls -l /tmp/.X11-unix
total 0
srwxrwxrwx 1 ivv users 0 Aug 16 21:11 X0Im a bit confused as to why this socket isnt owned by root in the first place, looking at some documentation from Xorgs release notes it seems like that is required:
This issue seems to stem from Log: Afterwards it exits, so no games launch. |
|
@IvarWithoutBones I use SDDM in combination with sway or i3. |
|
Gdm with gnome wayland here. In my case Maybe it's xwayland's issue? |
Is |
|
After adding |
|
@BillHuang2001 mind showing exactly how you did it? |
|
Yes, the two packages are added in steam's extraPkgs. nixpkgs.config.packageOverrides = pkgs: {
steam = pkgs.steam.override {
extraPkgs = pkgs: with pkgs; [
xorg.libXcursor
xorg.libXi
xorg.libXinerama
xorg.libXScrnSaver
libpng
libpulseaudio
libvorbis
stdenv.cc.cc.lib
libkrb5
keyutils
];
};
};And launch option in steam |
|
Are you running that in Xorg? I tried the same steps on Wayland and it still fails with the |
|
I'm on wayland, you still have to manually run |
FWIW this also works on sway. |
|
There must be something different, because I have launched gamescope in embedded mode, from a wayland session and from an X session, and I never had to chown anything |
|
Same, nested (X11) and embedded (VT) worked on my end without anything wonky Just in case, here's my groups: |
|
@BillHuang2001 I've tried your suggestion with extraPackages. Doesn't seem to work for me, even when chowning X11-lock: I still get krb5 errors and the game doesn't show up, but steam reports it as running. Perhaps I missed a step? Config is here. EDIT: My bad, I was using Sorry for necro-ing! |
|
Using xorg & SDDM, and I do seem to have to It appears that Steam's namespace maps all instances of users other than the current one in to |
|
gamescope does work in Flatpak Steam, I did some digging and what Flatpak is doing is mostly equivalent to passing in |
|
Did anyone mange to get past this issue? |
|
Workaround: The solution was a combination of multiple steps:
{
wayland.windowManager.hyprland.xwayland.enable = true;
home-manager.users.me.home.sessionVariables = {
GDK_BACKEND = "wayland,x11";
QT_QPA_PLATFORM = "wayland;xcb";
#SDL_VIDEODRIVER = "x11";
CLUTTER_BACKEND = "wayland";
XDG_CURRENT_DESKTOP = "Hyprland";
XDG_SESSION_TYPE = "wayland";
XDG_SESSION_DESKTOP = "Hyprland";
WLR_NO_HARDWARE_CURSORS = "1";
};
}
{
environment.systemPackages = with pkgs; [ gamescope ];
nixpkgs.config.packageOverrides = pkgs: {
steam = pkgs.steam.override {
extraPkgs = pkgs: with pkgs; [
xorg.libXcursor
xorg.libXi
xorg.libXinerama
xorg.libXScrnSaver
libpng
libpulseaudio
libvorbis
stdenv.cc.cc.lib
libkrb5
keyutils
];
};
};
}
Some minor issues that I've encountered with GameScope:
I benchmarked GameScope versus running directly in Wayland with my configuration and I found the Wayland session to be noticeably smoother. Frametimes and FPS were slightly better in Hyprland/Wayland according to MangoHud with Xanmod 6.2 kernel and performance governor. I also found that GameScope performs a lot better when VRR is enabled and direct scanout is disabled: Hope this helps anyone! |
Project description
This is the Wayland based compositor that Valve is using, that when paired with a running application, can fix minimizing and other such issues, as well as allowing AMD FSR on any application.
Metadata
The text was updated successfully, but these errors were encountered: