-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mouse pointer speed slower in gamescope #196
Comments
I can confirm that when rendering the game at a high resolution (4K in my case) and then rendering it on the client at a lower resolution (in my case, a 2560x1440 monitor) the mouse is slow indeed. Rendering at the same resolution does not have that issue. |
I'm fairly certain I figured out why this happens: |
I am on KDE Plasma BTW. |
I noticed this also with BattleTech (Not using native) |
Anyone find a work around for this issue? |
There should be a way to configure this, having a different cursor behaviour inside gamescope than outside it makes playing some games (like osu! or shooters) really hard.
in swaywm. |
When i start Control under gamescope i cant look around with the mouse. |
Playing Battlefield 1 I found out the mouse wasn't working. I could move around but I couldn't look around. Turning OFF raw mouse input fixed this problem, but after a while the whole game would begin to stutter and jitter and the aim was jumping all over the place. All of these issues were not present without gamescope. I'm on a Ryzen 5 3400G (iGPU) on Arch Linux. |
I'm on Manjaro KDE using Wayland. Tested only on Dota 2. |
In Apex it goes crazy, can't even play the game with a mouse 😂 |
Can confirm that it still happens. My mouse cursor gets very slow on gamescope. |
I feel light slowdowns when using Gamescope in Splitgate. Mostly on up/down axis. Could it be FPS related?
Edit: It only happens when moving in diagonal axis up/left. |
Still happening. |
I'm facing the same problem but in reverse. |
I think gamescope uses a fixed mouse sensitivity. That's why people with higher sensitivity are complaining about the slower speed while other people with lower sensitivity complain about the higher speed. |
Possibly related: #628 |
Can confirm, although in my case, when using Gamescope at a lower resolution, my cursor speed is faster than the host (might be due to the 1000hz and 12000 dpi mouse?), if the Gamescope launched with the same resolution as the host, the cursor is the same speed as in the host. And the lower resolution you use, the faster the cursor speed is, at least that's what I feel when testing at a bunch of resolution, I'm not sure if it is related or not just because the screen area is smaller thus the mouse reach the other side faster. |
I think multimonitor setups are confusing gamescope. |
Mousespeed itself is manageable but the mousewheel is unusable in this state. |
Some people are using more sophisticated acceleration profiles available in X, like this
Those options (or, just behavior of the mouse after applying them) are not grabbed by gamescope either, and the custom acceleration profile created by modifying those numbers gets lost, when playing through gamescope. |
I have tried gamescope in both X11 and Wayland, and the issue is identical for me in both. I am using the default mouse settings in Manjaro KDE, which makes the gamescope mouse movements much slower. When I tried using gamescope on Wayland it was via Hyprland, and I was using it because Hyprland wasn't capturing the mouse within a fullscreen application. This makes playing RTS games difficult, as I expect the mouse to move the same distance both in and out of game. |
Any workaround for this? |
Still having these issues |
I'm also having this issue. It's annoying to have to separate mouse speed especially for rts. |
Same issue here, the mouse speed is very slow. I'm on a 4 monitor setup. |
hey guys, idk about ya'll but i think this issue might have been fix, well atleast for me. the mouse movement seems to be sync with the wm itself. |
For me, it is in sync with WM only when the cursor is shown. With invisible cursor (like mouse look in most games), acceleration profile and sensitivity settings are still thrown out of the window (metaphorical one, not the window manager), sadly. |
I haven't deal with gamescope in a long time but I still believe it is caused by the different size/resolution the gamescope has compared to your actual resolution, I have 4K monitor and I tried playing some games using gamescope and set the resolution to 1080p (smaller than 4K obviously), the cursor is faster than it should, not slower, but if I set it as the same as my monitor, it move about the same, I'll test this again. |
As said earlier, it is not the whole issue. The main problem is that - even using 1:1 resolution in gamescope - host stuff, like acceleration profile mentioned in: ...is totally ignored (for situations, where cursor is invisible). It only works fine for visible cursor. |
Confirming. Just tried gamescope for the first time in a steam game, and cursor is old-school X11 "X" symbol in the game, and mouse movement is very slow. |
Mouse pointer speed in gamescope windows is noticeably slower than when running without. This happens on all games I've tried.
Mouse pointers on (other?) XWayland windows don't exhibit the same behavior.
Acceleration profile is flat both in and out of gamescope.
Setupinfo:
WM: sway, commit: 009c58fc
mesa git, commit a1c56b80915
Gamescope, commit g756b3a6
3 monitors: 2 are 1080p, one 1440p
I normally run gamescope with just
-W 2560 -H 1440
, but it also happens with upscaling, specifying -f and pretty much any combination of flags.Not sure which logs would be helpful, but just tell me if any would be then I'll post them.
The text was updated successfully, but these errors were encountered: