The information hover says it’s optimized for gaming on Steam, which I do. But is this just “gamemode” the daemon/lib thing? I don’t know/understand what any of these things do.
3 Likes
Jes it worth it on my side. Some Games would not start without it crazy but it worked with gamescope layer on top 
1 Like
Ah the old gamescope to be or not to be “why there are so many” question
gamescope >
- classic gamescope that is beying used per game when activeted with the launch command option
gamescope session >
- gamescope intergration that runs as a based user session
gamescope session (steam) >
- gamescope intergration that runs as a Steam Big Picture session
Gamemode has nothing to do with gamescope. The versions are about “HOW” do you want your gamescope, per game? per whole DE? or only in Big Picture?
2 Likes
At the very least I find gamescope --force-grab-cursor -- %command% pretty much mandatory for all Steam game launch options. This is due to having multiple monitors(and Sway perhaps). Otherwise I end up mousing out of the game anytime I want to go left.
In the end it usually ends up being something as wild as:
gamescope -O DP-1 -r 120 -W 3840 -H 2160 --adaptive-sync -f --force-grab-cursor – %command%
Previously that would also include --backend sdlbut that recently broke…I think with the recent wlroots0.19 update…though I am entirely unsure. Most of the options are self explanatory, but you should look them up. I think setting the viewport size(-W,-H) is important as well.
Either way, I like using gamescope to be explicit about things, especially having multiple monitors of differing specifications. Steam is weird about ‘Primary’ monitors and such.