Linux Gaming

15911 readers

46 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago

MODERATORS

[email protected]

How do I properly use gamescope (self.linux_gaming)

submitted 3 months ago* (last edited 3 months ago) by Blxter to c/[email protected]

8 comments fedilink hide all child comments

I am trying to use gamescope and mangohud at same time so I ran gamescope -e -W 2560 -H 1440 -r 144 --mangoapp %command% (to run at 1440p at 144fps I think) as the launch option on steam but when I load into the game aiming goes crazy like 100x sensitivity but cursor movement (like in setting etc is normal). Is the command wrong I also hit win+f to make full screen. Is this the right way to use gamescope?

nvidia gpu
endeavoros

Thanks

all 9 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 3 months ago

Is your scaling set to something other than 100%? That seems to mess with gamescope and mouse location detection or something like that.

[–] [email protected] 1 points 3 months ago (1 children)

I'm surprised to game can launch at all. For me it crashes instantly.

[–] Blxter 1 points 3 months ago* (last edited 3 months ago) (1 children)

are you talking about hunt showdown the game or just playing with gamescope. For Hunt you need to use bleeding edge version of proton. Its in the beta setting of proton experimental.

Edit: as for gamescope yea it has not went well haha

[–] [email protected] 1 points 2 months ago

Sorry for the late response, I meant gamescope. I looked into it, it seems like umu-run has a bug where it expects DISPLAY=:0 but gamescope sets DISPLAY=:1. At least that's my understanding. It has been patched in the repo but there's no release with the patch yet.

Gamescope works fine if umu-run is not used to run the program.

[–] [email protected] 1 points 3 months ago (1 children)

It's setting the full screen size as the target area for input, not the resolution you're setting. Reduce your desktop resolution to the resolution you want to play at first if you're going that route. This is a known issue with a long list of problems leading up to this particular display of symptoms. Easier to just change your resolution before you play a lower resolution.

[–] Blxter 2 points 3 months ago (1 children)

Ok you lost me. I don't want to downscale or do any form of upscaling. I want to still render the game at 1440 p full screen. When I left those arguments blank it rendered the game screen at something small not sure what. My desktop screen resolution is 144. I might be misunderstanding.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago) (1 children)

Set your desktop resolution to whatever you're setting gamescope to, then see if it works properly. Turn off DLSS as well.

Edit: look here to see if you find anything useful: https://github.com/ValveSoftware/gamescope/issues/1145

[–] Blxter 1 points 3 months ago

Yes desktop resolution is the same resolution. If I'm understanding the github link it seems to be game specific and fixed for that game now (overwatch) I did not try with another game I was playing hunt showdown witch needs the bleeding edge of proton right now so maybe gamescope does not work? Sorry if I sound stupid not entirely sure thanks for the help though I will try another game today.