I was recently experimenting with using Gamescope to check whether HDR works on Plasma.

The games run perfectly if I set the compositor resolution (via -W and -H arguments) to a lower value like 1920x1080 (I have a 1440p monitor). But if I were to maximize the compositor window or make it fullscreen (via the Super + F shortcut), the window becomes invisible and I see my desktop. In case of maximizing, the title bar is visible but nothing else.

I have not set --expose-wayland since games don’t even start when I set that. When running gamescope with Steam integration (via the -e argument), steam starts and I am also able to make it fullscreen without any issues, but when I launch a game, I only see the Steam window.

During this time, I can hear the audio from the game, implying that the game is running in the background.

Has anyone else faced this issue and what could be done about this?

FWIW, I am on EndeavourOS with the git version of Gamescope installed from the AUR, though the non-git version does not fare any better. GPU is AMD Radeon with Mesa.

  • deathmetal27@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    Cool, I tried your launch options and it worked, though I have modified it a bit:

    ENABLE_HDR_WSI=0 DXVK_HDR=1 gamescope -f -H 1440 --hdr-enabled --mangoapp -- %command%

    Everything however had a slight blurriness and I wish FSR worked, however toggling FSR freezes the game. I never used FSR to begin with though.

    gamescope-wsi_git

    What is WSI exactly and what patches does this package of gamescope have?

    • Klaymore@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      Looking at the Nix package, it seems like it just enables the Meson flag “enable_gamescope_wsi_layer” and adds the package “vulkan-headers” to the build inputs. Looking at the AUR package it uses vulkan-headers but idk what meson flags it uses.