CS2 sticky input issue

[henrym11106]

System information

I am experiencing freezing inputs on Arch Linux; if I'm doing multiple key presses simultaneously there is a chance that one input will get stuck on.

a common example being crouch-jumping while moving and then not being able to stand up again, even after trying to duck, jump etc.

the issue is more serious when using "null" movement binds since that makes simultaneous inputs even more frequent.

this is consistent with steam-native and the runtime, AMDGPU and an Nvidia GPU with proprietary driver. all xorg, not tested on Wayland or non Arch-based systems.

this is pretty much the same behavior that I encounter in older Source engine games like CS:S. in that case a workaround is to use the system's libsdl2 by e.g. LD_PRELOAD="/usr/lib32/libSDL2-2.0.so.0 %command% in the launch options.

CS2 appears to use SDL3, and that does not appear to be packaged for Arch as of now. I could build the git version but I'm not sure my trust score or VAC status would like that very much.

this was not an issue with CS:GO

[Xinayder]

I'm not sure I understood the problem but I noticed something kind of similar? On CS:GO, I could press the left mouse button or right mouse button and before the animation ended, I pressed F and the inspect animation started. This is not the case with CS2, I can no longer do this.

[Remyrios]

System Information

I can report the sticky keys issue on my end too. No matter if the game is in full screen or windowed the keys after a while just get stuck. The most common I encounter is the back movement key at variable speed. With time it's more stuff getting stuck like even the mouse movement. The only thing that has made me able to resolve the issue is restarting the entire computer. Relaunching the game does not seem to help at all.

As for the mouse it is either being completely stuck and not being able to move it or furiously rotating but mostly from just the center in this position:

I should note that I run my desktop on Wayland but running it natively or adding SDL_VIDEODRIVER=x11 %command% to the launch parameters did not change anything.

[grgpw]

(not exactly sure if this is the same problem)

to reproduce: -start spraying -walk left/right/whatever -move mouse -View doesn't move

happens on sway but apparently not on hyprland (both wayland). I first encountered this problem playing half-life alyx with the NoVR mod (shrugged it off because unofficial mod and so on) but not in other games (e.g. xonotic), so this could be an Source 2 thing.

[henrym11106]

These input problems might all be related, but in my case closing and relaunching CS2 resets input state. if the issue is not cleared after a relaunch it may be that something is happening on your system, perhaps a persistent SDL3 runtime? or maybe a Wayland thing? my OS only includes SDL2 and X11. either way if HL:A also triggers this and no other games it could be Source 2 thing.

the stuck-input issue I'm having is triggered by using binds that combine actions, e.g. +jump;+duck or -left;+right.

this is my usual movement config switched to wasd to replicate, put that file in steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg/ and exec. the easiest way to cause stuck input is to play offline and tap move left and right simultaneously (a+d) or do the same with crouchjump + crouch. the player will eventually end up running in one direction with no input or get stuck crouching in the other example.

Also, while holding +duckjump (space) I should be able to un-crouch by tapping +crouch (ctrl) but nothing happens in CS2.

the only other game I've played with this problem is the current Momentum Mod (modded Source engine) steam beta, but that game allows non-cancelling/null input to be set in the options menu - which I think ought to be an option in all fps games. valve please fix?

@kisak-valve just want to confirm that this is an issue on Windows 10 as well. same behavior on Arch and Win10, Momentum and CS2.

[Remyrios]

I have managed to fix the issue on my end. It seems to be related to controller support as after unplugging my steering wheel from the computer the issue got fixed. I tried reproducing it without the wheel plugged in and I was unable to even after 2 hours of gameplay. I still find it weird that this is how the game is reacting to plugged in controllers that are not bound in game at all.

[henrym11106]

Nice @Kaperios . it does seem that CS2 handles axial input differently. for example, running unbindall also unbinds mouse aim...

anyway I seem to have found a workaround for my issue as well. my movement binds are a bit messier now but they seem to work fine.

I'm not 100% sure if this issue should be closed, the differences are annoying but that might not change. as long as the workaround works, eh.

[Xinayder]

@henrym11106 that's not a good reason to close the ticket. The bug exists and it should remain open until a fix is released. Otherwise we will remain with broken things on Linux that should've been fixed. An existing workaround is not a fix, if you have to connect a controller to fix your sticky input it's definitely not a proper fix and not a reason to close this ticket.

[henrym11106]

@Xinayder connecting a controller has nothing to do with this issue, nor is it limited to Linux as I mentioned earlier.

this issue is particular to how the game handles +movement aliases.