Giter Club home page Giter Club logo

Comments (3)

hivehivemind avatar hivehivemind commented on June 16, 2024

Gamescope doesn't have output selection built into the interface and its rules for display selection can be a bit arbitrary at times.
You can:

  1. Check your user home .gamescope-stdout.log file (it's a hidden one), which will tell what connector your TV is in. i.e. a graphics card with 3 display ports and 1 HDMI should have DP-1, DP-2, DP-3, and HDMI-A-1. I have a LG TV connected into DP-3 (I use a DP to HDMI adapter) so the log shows drm: Connector DP-3 -> GSM - LG TV SSCR2 for it.
  2. Once you know the connector your TV is in, now open in your user home the .gamescope-cmd.log file and copy its contents.
  3. In the home folder, go to .config/ (it's a hidden one) and create a folder called environment.d/. Inside it, create a new file called gamescope-session-plus.conf.
  4. In our new .conf file, type GAMESCOPECMD=", paste the content you copied from .gamescope-cmd.log, and type another ", so what we just pasted is inside our double quotes wrap. Here is an example:
    GAMESCOPECMD="/usr/bin/gamescope --max-scale 2 --adaptive-sync -e --xwayland-count 2 -O *,eDP-1 --default-touch-mode 4 --hide-cursor-delay 3000 --fade-out-duration 200 --cursor-scale-height 720 -R /run/user/1000/gamescope.yQe3x0S/startup.socket -T /run/user/1000/gamescope.yQe3x0S/stats.pipe"
  5. Note from our previous step we have *,eDP-1. Replace it with your connector we checked in the step 1. In my case the final file now is:
    GAMESCOPECMD="/usr/bin/gamescope --max-scale 2 --adaptive-sync -e --xwayland-count 2 -O DP-3 --default-touch-mode 4 --hide-cursor-delay 3000 --fade-out-duration 200 --cursor-scale-height 720 -R /run/user/1000/gamescope.yQe3x0S/startup.socket -T /run/user/1000/gamescope.yQe3x0S/stats.pipe"

Restart the system and whenever you go into game mode it should now select the proper monitor. Desktop mode will retain its own monitor configuration independently.

from bazzite.

unicornsandcandies avatar unicornsandcandies commented on June 16, 2024

Gamescope doesn't have output selection built into the interface and its rules for display selection can be a bit arbitrary at times. You can:

1. Check your user home `.gamescope-stdout.log` file (it's a hidden one), which will tell what connector your TV is in. i.e. a graphics card with 3 display ports and 1 HDMI should have DP-1, DP-2, DP-3, and HDMI-A-1.  I have a LG TV connected into DP-3 (I use a DP to HDMI adapter) so the log shows `drm: Connector DP-3 -> GSM - LG TV SSCR2` for it.

2. Once you know the connector your TV is in, now open in your user home the `.gamescope-cmd.log` file and copy its contents.

3. In the home folder, go to `.config/` (it's a hidden one) and create a folder called `environment.d/`. Inside it, create a new file called `gamescope-session-plus.conf`.

4. In our new .conf file, type `GAMESCOPECMD="`, paste the content you copied from `.gamescope-cmd.log`, and type another `"`, so what we just pasted is inside our double quotes wrap. Here is an example:
   `GAMESCOPECMD="/usr/bin/gamescope --max-scale 2 --adaptive-sync -e --xwayland-count 2 -O *,eDP-1 --default-touch-mode 4 --hide-cursor-delay 3000 --fade-out-duration 200 --cursor-scale-height 720 -R /run/user/1000/gamescope.yQe3x0S/startup.socket -T /run/user/1000/gamescope.yQe3x0S/stats.pipe"`

5. Note from our previous step we have `*,eDP-1`.  Replace it with your connector we checked in the step 1. In my case the final file now is:
   `GAMESCOPECMD="/usr/bin/gamescope --max-scale 2 --adaptive-sync -e --xwayland-count 2 -O DP-3 --default-touch-mode 4 --hide-cursor-delay 3000 --fade-out-duration 200 --cursor-scale-height 720 -R /run/user/1000/gamescope.yQe3x0S/startup.socket -T /run/user/1000/gamescope.yQe3x0S/stats.pipe"`

Restart the system and whenever you go into game mode it should now select the proper monitor. Desktop mode will retain its own monitor configuration independently.

It's great but will it also change audio?

from bazzite.

hivehivemind avatar hivehivemind commented on June 16, 2024

Gamescope doesn't have output selection built into the interface and its rules for display selection can be a bit arbitrary at times. You can:

1. Check your user home `.gamescope-stdout.log` file (it's a hidden one), which will tell what connector your TV is in. i.e. a graphics card with 3 display ports and 1 HDMI should have DP-1, DP-2, DP-3, and HDMI-A-1.  I have a LG TV connected into DP-3 (I use a DP to HDMI adapter) so the log shows `drm: Connector DP-3 -> GSM - LG TV SSCR2` for it.

2. Once you know the connector your TV is in, now open in your user home the `.gamescope-cmd.log` file and copy its contents.

3. In the home folder, go to `.config/` (it's a hidden one) and create a folder called `environment.d/`. Inside it, create a new file called `gamescope-session-plus.conf`.

4. In our new .conf file, type `GAMESCOPECMD="`, paste the content you copied from `.gamescope-cmd.log`, and type another `"`, so what we just pasted is inside our double quotes wrap. Here is an example:
   `GAMESCOPECMD="/usr/bin/gamescope --max-scale 2 --adaptive-sync -e --xwayland-count 2 -O *,eDP-1 --default-touch-mode 4 --hide-cursor-delay 3000 --fade-out-duration 200 --cursor-scale-height 720 -R /run/user/1000/gamescope.yQe3x0S/startup.socket -T /run/user/1000/gamescope.yQe3x0S/stats.pipe"`

5. Note from our previous step we have `*,eDP-1`.  Replace it with your connector we checked in the step 1. In my case the final file now is:
   `GAMESCOPECMD="/usr/bin/gamescope --max-scale 2 --adaptive-sync -e --xwayland-count 2 -O DP-3 --default-touch-mode 4 --hide-cursor-delay 3000 --fade-out-duration 200 --cursor-scale-height 720 -R /run/user/1000/gamescope.yQe3x0S/startup.socket -T /run/user/1000/gamescope.yQe3x0S/stats.pipe"`

Restart the system and whenever you go into game mode it should now select the proper monitor. Desktop mode will retain its own monitor configuration independently.

It's great but will it also change audio?

Yup. Gamescope takes control of the DRM and will output audio to the HDMI you have connected or any other device as normal. It's only not possible to output video with one HDMI and audio with another HDMI in the same device (i.e. using to HDMIs from the same graphics card for it).

from bazzite.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.