Open ifohancroft opened 4 years ago
May be the same issue as mine here. Do you remember if you had mouse acceleration enabled (specifically xorg mouse acceleration), as that is what made my issue happen.
I currently don't have mouse acceleration (explicitly disabled it via an xorg config) and as far as I can remember, I didn't have it enabled when I encountered the bug either and I don't use any acceleration in-game (I can't remember if the game even offered the option for acceleration) Unfortunately, I don't currently have enough space on my SSD to install CS:GO and try again.
I currently don't have mouse acceleration (explicitly disabled it via an xorg config) and as far as I can remember, I didn't have it enabled when I encountered the bug either and I don't use any acceleration in-game (I can't remember if the game even offered the option for acceleration) Unfortunately, I don't currently have enough space on my SSD to install CS:GO and try again.
Maybe gnome accel is enabled? Would be interesting if both cause the issue.
I currently don't have mouse acceleration (explicitly disabled it via an xorg config) and as far as I can remember, I didn't have it enabled when I encountered the bug either and I don't use any acceleration in-game (I can't remember if the game even offered the option for acceleration) Unfortunately, I don't currently have enough space on my SSD to install CS:GO and try again.
Maybe gnome accel is enabled? Would be interesting if both cause the issue.
At the time of reporting the bug, I was already on Manjaro, so I believe I was using XFCE with it. I first set the acceleration via the GUI to the middle then disabling via X.Org then not touching the GUI so there shouldn't be any acceleration whatsoever.
Your system information
Please describe your issue in as much detail as possible:
Disabling raw mouse input in CS:GO causes negative acceleration on slow downward mouse movements. If you move the mouse fast, the movements and responsiveness of the mouse seem totally normal, however, if you move it slow, you need to move it about an inch (400DPI 3.13 in-game sensitivity, since that actual distance may vary depending on that, I don't know) until it moves on the screen at all, while all other directions are totally fine in either slow or fast movement regardless of the state of m_rawinput.
Steps for reproducing this issue: