search

ValveSoftware / csgo-osx-linux

Counter-Strike: Global Offensive
http://counter-strike.net
776 stars 69 forks source link

Sensitivity tied to screen resolution #3342

Open Xinayder opened 1 year ago

Xinayder commented 1 year ago

Your system information

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:

  1. Change aspect ratio to 4:3 and resolution to 1024x768
  2. Apply settings
deanrih commented 1 year ago

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>)

Xinayder commented 1 year ago

@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

UNIm95 commented 1 year ago

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:

  1. Set native display resolution.
  2. Set game resolution lower than monitor resolution.
  3. Set mouse dpi to 800, im-game sensitivity 2.12
  4. Start any type of game(in -menu mouse works)
  5. 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

gerelef commented 1 year ago

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)

sevuu commented 1 year ago

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

Inq-B commented 1 year ago

Exclusive fullscreen is the only option that works but it's forced to 60hz without the ability to change it.

miklhh commented 1 year ago

I can confirm this issue as well!

ghost commented 1 year ago

I have the same problem on my laptop. Any non-standard resolution leads to this problem.

LennoxLuther commented 1 year ago

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.

gerelef commented 12 months ago

Still happens after latest patch on 10/6/2023

spynetS commented 12 months ago

I found that if i increase my dpi on my mouse the effect decreased I first used 800 and now with 3000 its playable

hb4ch commented 12 months ago

can confirm. latest patch updated. Manjaro linux with 6.6 kernel, steel series prime mouse. rtx 2080.

fischer8 commented 11 months ago

I have the same problem. Ubuntu 22.04.3 LTS.

0xdeface commented 11 months ago

I have the same problem on my laptop. Any non-standard resolution leads to this problem.

i have same problems, archlinux btw

JustASpeedrunner commented 11 months ago

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.

UNIm95 commented 11 months ago

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.

Mk-arc commented 11 months ago

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.

GaetanLepage commented 11 months ago

Same here

mnb06 commented 11 months ago

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

leitnermatias commented 11 months ago

Still hapenning

gerelef commented 10 months ago

@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.

spynetS commented 10 months ago

@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

wwklnd commented 10 months ago

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

Mk-arc commented 10 months ago

Just saying. I had the same Issue on Kubuntu. Lately I switched to KDE Neon with the latest KDE updates and the problem disappeared.

gerelef commented 10 months ago

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.

Mk-arc commented 10 months ago

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

glvno commented 10 months ago

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.

TheJanzap commented 10 months ago

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

gerelef commented 10 months ago

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.

Mk-arc commented 10 months ago

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.

fischer8 commented 10 months ago

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.

I tried the flatpak steam version but the problem still exists (ubuntu 22.04 LTS)

fischer8 commented 8 months ago

Problem solved when using Wayland instead of Xorg

MathiasOdlund commented 6 months ago

I have the same issue.

Info: 4:3, 1280x960 Arch Linux x86_64 6.7.9-arch1-1 GNOME 45.4 AMD Ryzen 9 3900X (24) @ 4.000GHz NVIDIA GeForce RTX 2070 SUPER

stetskevych commented 6 months ago

I have this issue and it prevents me from aiming correctly. When I move the mouse slowly the crosshair does not move in the left--up direction. Notably my graphics card is Intel so this is not an Nvidia issue. Thanks.

Resolution: 4:3, 1280x960 Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.10 Kernel Version: 6.7.9-100.fc38.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 14.9 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics

feschber commented 6 months ago

VALVE PLEASE FIX this issue has been there since the beta.

Or at least give us back the option to run in native wayland which did not have this problem. I do not understand why wayland support was straight up removed.

spynetS commented 6 months ago

VALVE PLEASE FIX this issue has been there since the beta.

Or at least give us back the option to run in native wayland which did not have this problem. I do not understand why wayland support was straight up removed.

I find sort of a solution. If you set your mouse dpi very high, I think I have 3000, and decrease you sensitivity in the game it becomes playable. The only problem is in the buy menu :/ (hard to buy what that high dpi)

feschber commented 6 months ago

Replying to https://github.com/ValveSoftware/csgo-osx-linux/issues/3342#issuecomment-2015302582

Not really. I also play at 1600 dpi and it's utter ****

brejela commented 6 months ago

Just to add that I am also having this problem:

Any non-native resolution makes the mouse ignore small movements up and left.

By "any non-native resolution" I mean any resolution that is not 1920x1080.
This is a major bummer as I don't much enjoy playing 16:9

un1t commented 6 months ago

Arch Linux. I had 1080p monitor and all worked well. Now i have 4k monitor (3840x2160) and i play CS with 1920x1080 resulution selected in the game. Horizontal mouse movements work well, but vertical completely unplayable. It moves vertically more slowly and sometime don't move at all. It happens not always. After restarting the game it could be normal.

OS: Arch Linux x86_64 Kernel: 6.8.2-arch2-1 Uptime: 1 day, 8 hours Packages: 1107 (pacman), 52 (flatpak) Shell: bash 5.2.26 Resolution: 3840x2160 DE: GNOME 46.0 WM: Mutter WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: kgx CPU: Intel i5-9400F (6) @ 4.100GHz GPU: NVIDIA GeForce GTX 1080 Ti Memory: 5035MiB / 32035MiB

rzr000 commented 6 months ago

I have the same here. Bought a new mouse, still happens. It is much less noticeable with a non-gamer mouse, though. With a logitech G502 it's horrible, with a logitech M500S it's much less noticeable, although aiming just a couple pixels up or down is also very difficult. This happens only during gameplay. In the game menu the movement is smooth and moving just a single pixel is perfectly possible. During gameplay, only larger movements are registered. I have tried all kinds of DPI and sensitivity combinations

losuler commented 5 months ago

Just going to chime in and say that I can confirm the only solution that seemingly worked to resolve this issue is the one provided by a plugin for Hyprland^1. Hopefully this helps Valve or with other desktop environments in the meantime.

thatpumpkin commented 4 months ago

Still happens, -fullscreen does not fix it for me.

HannesMC commented 3 months ago

I‘ve had also the same issue. Today i started my Wayland Test and i discovered by chance that with wayland my mouse problems have disappeared.

I will submit detailed information on my start options later.

With Mouse issues: PopOS 22.04 Nvidia 2070 Super X11 / Gnome

Without Mouse Issues: PopOS 22.04 Nvidia 2070 Super Wayland / Gnome

scr0llbaer9000 commented 3 months ago

Playing non-native resolution seems to the cause for this issue and should be reproducible on most Linux systems.

However, few others and me have this problem only since recently (and I use rolling Arch btw, so always most-up-to-date kernel and libraries) and not since Sep 2023, on the same machine without having changed anything, so that makes me wonder what is it that has actually changed and has introduced the problem.

jedthehumanoid commented 3 months ago

Same for me, just recently got this issue.

Running native resolution fixes the problem. Using -fullscreen does not fix it.

oalonesbr commented 3 months ago

vc conseguiu arrumar esse erro? estou com esse mesmo problema no Zorin OS, meu notebook a resolução nativa é 1920x1080 144hz mas eu jogo em 1280x960 e se coloco em tela cheia fica com BORDA PRETA, agora se eu coloco em janela sem borda, fica com esse lag na sensibilidade

andreatsilva commented 3 months ago

O OS tem que ter a mesma resolução do jogo infelizmente, -fullscreen só funcionou comigo 1 vez. Depois de 3 meses tentando jogar em Linux eu desisti. Se quer continuar a jogar seus games suavemente, use windows, Linux não foi feito para jogos. Para mim não faz diferença pois eu apenas uso o terminal do linux e hoje em dia com o wsl você consegue usar Linux em ambiente windows apenas instalando atravez da Microsoft Store, Pesquise Ubunto ou Debian e é só instalar.

superboss2300 commented 2 months ago

Any updates on this? Currently experiencing this issue and the game is almost unplayable.

deanrih commented 2 months ago

Playing non-native resolution seems to the cause for this issue and should be reproducible on most Linux systems.

However, few others and me have this problem only since recently (and I use rolling Arch btw, so always most-up-to-date kernel and libraries) and not since Sep 2023, on the same machine without having changed anything, so that makes me wonder what is it that has actually changed and has introduced the problem.

I believe it's there since CS2 release (i guess the Linux version, not sure about Windows), native resolution is fine, but anything lower is screwing up mouse movement

scr0llbaer9000 commented 2 months ago

I believe it's there since CS2 release (i guess the Linux version, not sure about Windows), native resolution is fine, but anything lower is screwing up mouse movement

No, I was playing CS2 with reduced resolution before too (because my last gaming notebook broke, and still waiting to get a new one). The bug for me was introduced with the version in May that had the shaky viewmodel bug (hence I had thought it's related).