csgo-osx-linux
csgo-osx-linux copied to clipboard
ValveSoftware
Sensitivity tied to screen resolution
Your system information
- System information from steam (
Steam->Help->System Information) in a gist: https://gist.github.com/Xinayder/9d064f9843d4e1d9e39143983fcde0b2 - Have you checked for system updates?: Yes
Please describe your issue in as much detail as possible:
The mouse sensitivity seems to be tied with the game's resolution. Changing to a different aspect ratio and resolution, like 4:3, 1024x768 will make your mouse sensitivity be lower.
Steps for reproducing this issue:
- Change aspect ratio to 4:3 and resolution to 1024x768
- Apply settings
Can confirm, also setting to lower resolution seems to make the game to "skip" some mouse movement, for context I have 4K Monitor using RTX 2060, the game run... okay, but the mouse movement itself is the same as CS:GO, but when trying to use lower resolution, e.g 1080 so I can get more FPS (not much), my mouse become somehow slower and skips certain small movement, and if I swing around the mouse left and right, it eventually drift towards bottom right, perhaps because I have 2 monitors( 1 4K and 1 1600x900 on the right )? but that doesn't tell the bottom part of the drift. Note that the drift doesn't occur on 4K resolution
Update: My system configuration is Manjaro (Arch Linux) Intel i3-8100 NVIDIA 2060 2 Monitors (1 4K < primary >, 1 1600x900 <secondary, located on the right side of the primary>)
@deanrih that's what I noticed as well, on lower resolutions it seems like the mouse is drifting towards the bottom right corner, as if something was physically impeding the mouse cable and constricting its movement, even though it isn't.
I managed to record a video trying to show the problem. In both cases (1024x768 and 1080p), I was moving my mouse at roughly the same speed.
https://youtu.be/nsN1LUU18Us https://youtu.be/6toVSxiF34E
Can confirm.
I have even 2 issues with resolutions and CS2.
Issue 1:
Same like by @Xinayder
If i change resolution of screen and or game - mouse sensitivity changes in CS2.
If i check it with Team Fortress 2 it changes only if raw input is not enabled.
It looks like CS2 does not have raw input at all.
Issue 2 If game has different resolution from display, i'm getting dead zone for mouse movement. How to reproduce:
- Set native display resolution.
- Set game resolution lower than monitor resolution.
- Set mouse dpi to 800, im-game sensitivity 2.12
- Start any type of game(in -menu mouse works)
- Try to slowly move mouse and notice that crosshair is not moving.
My Setup: Ubuntu Mate 22.04 with X11. Ryzen 9 3950x 64GB RAM Radeon 5500x 2 4k Displays. Mouse Logitech G502
Adding that is happening on the latest build currently on Fedora 37/GNOME Xorg with Ryzen 5 3600 / 2070 SUPER on 4:3 (1280x1024)
Sidenote: when I lowered my mouse's polling rate to below 500, this issue stopped (tested with 2 mice)
Lowering my mouse's polling rate to 125 did make this issue less noticeable, but the deadzone is still here. Playing 4:3 stretched (1280x1024) on 1000hz polling rate is basically impossible, on 125hz it's playable, but aiming still feels very off
My setup: Arch Linux + BSPWM (X11) 6.4.11-273-tkg-eevdf kernel Intel Core i5 8400 Nvidia GTX 1070 Two 1080p monitors (60 & 144hz) Razer Viper Mini
Exclusive fullscreen is the only option that works but it's forced to 60hz without the ability to change it.
- Distribution: Debian 12 (6.1.0-12-amd64)
- Graphics Card: RTX 2070 Super
- CPU: Ryzen 5 5600X
- Graphics Drivers: Nvidia PPA 535.104.12
- Display Server: X11
- Mouse: G502
I have the same problem on my laptop. Any non-standard resolution leads to this problem.
I am having this issue too on Fedora 38 withe steam flatpak. Tested with X11 and wayland and both have the issue. The issue is only in full screen or windowed full screen.
There is a deadzone when moving slowly up or left., if you move the mouse quickly it will respond but not quite as far as expected. Down and right movement seems unaffected.
I am playing at 1920x1080 on a 2560x1440 display. When I play at native resolution or in a 1080 window it works fine. I've tried with gamescope but that made no difference. Polling rate lowered will mask the issue rather than resolve it.
It makes the game unplayable, I have resorted to playing in a window in the middle of the screen.
I found that if i increase my dpi on my mouse the effect decreased I first used 800 and now with 3000 its playable
can confirm. latest patch updated. Manjaro linux with 6.6 kernel, steel series prime mouse. rtx 2080.
I have the same problem on my laptop. Any non-standard resolution leads to this problem.
i have same problems, archlinux btw
Not sure if this is the same issue but I'll put this here anyway, if I should make a new issue lmk. When playing with a stretched resolution, slow movements up or left are not registered below a certain speed threshold--right and down work fine at any speed. If I am playing non-stretched it works as intended, even on 4:3 resolutions.
This isn't always consistent though, sometimes it works properly, other times it will not.
EDIT: If it matters, I'm on Hyprland and Arch linux. I have also attached a video of the issue here: https://streamable.com/bkjh2i Any time my mouse is not moving I am either moving it up or left slowly.
With latest update (2023-10-24) i still have same issues. If i move mouse left or up slowly -> crosshair is not moving. If i move it right or down -> all ok.
With latest update (2023-10-24) i still have same issues. If i move mouse left or up slowly -> crosshair is not moving. If i move it right or down -> all ok.
Yes. Exactly the same issue here.
I have temporarily solved it by changing the resolution via launch options:
xrandr --output HDMI-A-0 --primary --mode 1280x960_240.00 --left-of DisplayPort-0; ENABLE_VKBASALT=1 gamemoderun %command%; xrandr --output HDMI-A-0 --primary --mode 1920x1080 --rate 240 --left-of DisplayPort-0
(I had to add a custom resolution to make it work at maximum hertz)
Sometimes when I change workspace the problem reappears, restarting the game returns it to normal
Arch, I3-wm
@kisak-valve Is there any update to this issue? I imagine this would be a problem for steam decks with gamescope as well, when playing with resolutions below native.
@kisak-valve Is there any update to this issue? I imagine this would be a problem for steam decks with gamescope as well, when playing with resolutions below native.
It's still happening for me
I've been playing in 1080p on a 4K monitor, and noticing that moving the mouse slowly up or to the left does not move the crosshairs at all. It seems to be more severe when moving upwards.
** Edited to add: the issue disappears when I play on the internal laptop display at its native resolution.
Lenovo Legion 5 15ACH6H AMD Ryzen 7 5800H CPU Nvidia GeForce RTX 3070 Laptop GPU 64GB RAM Manjaro Linux + GNOME 45.1 (X11) Linux 6.1.63-1-MANJARO
Internal laptop display is 1920x1080 @ 165Hz Secondary monitor is 3840x2160 @ 60Hz (in use for CS2) Tertiary monitor is a pen display, 1920x1080 @ 60Hz
Just saying. I had the same Issue on Kubuntu. Lately I switched to KDE Neon with the latest KDE updates and the problem disappeared.
Just saying. I had the same issue on Kubuntu. Lately, I switched to KDE Neon with the latest KDE updates, and the problem disappeared.
Makes somewhat sense, actually, considering this isn't an issue with Wayland/XWayland or X11... I'd ask you to list your installed packages, but I don't know the relevant system packages that could affect CS2. What's your kernel version, though? Perhaps the issue is the way the current kernel's handling input events from mice.
Just saying. I had the same issue on Kubuntu. Lately, I switched to KDE Neon with the latest KDE updates, and the problem disappeared.
Makes somewhat sense, actually, considering this isn't an issue with Wayland/XWayland or X11... I'd ask you to list your installed packages, but I don't know the relevant system packages that could affect CS2. What's your kernel version, though? Perhaps the issue is the way the current kernel's handling input events from mice.
OS: Neon 22.04 jammy Kernel: x86_64 Linux 6.2.0-37-generic
Both the bug in the OP and the polling rate workaround are reproducible on Windows 10 as well. Using any 4:3 (stretched, in my case) resolution at 1000hz polling rate effectively lowers sensitivity by about 75%. 500hz or lower and the problem seems to vanish.
Just tested it and the bug seems to be gone
Arch Linux with Kernel 6.6.2-arch1-1 KDE Plasma 5.27.9 1920x1080 @ 144hz w/ 100% scaling (primary) & 3840x2160 @ 60hz w/ 150% scaling (secondary) Steam Flatpak
Just tested it and the bug seems to be gone
Arch Linux with Kernel 6.6.2-arch1-1 KDE Plasma 5.27.9 1920x1080 @ 144hz w/ 100% scaling (primary) & 3840x2160 @ 60hz w/ 150% scaling (secondary) Steam Flatpak
I'm on Fedora 39, w/ Steam from rpmfusion and it's still not fixed; perhaps it's the fact that you're running flatpak steam?
EDIT:~~I tried to install flatpak Steam alongside regular Steam & test with the same install but I couldn't make it work... if anyone else who's facing this issue (from a native package) can try running the flatpak version and report back that'd be great?~~ I tested it with flatpak Steam. It's not fixed for me. I'd argue that NVIDIA drivers might be (somehow) to blame, however the entire pro scene would be in an uproar if it were, lmao. Since the bug is reproducible on Windows as well, it's most likely not the kernel, and definitely not a Linux or Windows specific issue. I can (personally) testify that the mouse or keyboard brand doesn't matter, it worked on any combination of hardware I tested. However, I don't know if it's a third party library thing, right? if it were, wouldn't flatpak steam also work on my machina? 🤔 Weird stuff. If anyone has any ideas into how we could debug this and hopefully help Valve ourselves, that'd be great...
Could we also add the Windows label as well @kisak-valve? if it's reproducible for even one person on Windows, I'd imagine there are thousands that are facing the same issue.
EDIT 2: With the native package of Steam, if I manually downscale my monitor to 1280x1024 stretched, instead of ingame, the issue disappears. Note: this applies to both Wayland, and XOrg GNOME.
I'm on Fedora 39, w/ Steam from rpmfusion and it's still not fixed; perhaps it's the fact that you're running flatpak steam?
Interestingly I had a native steam install on my old system. Where the bug was present.
On my new install I use the flatpak steam version and its fine.