#CSGO Movement inputs being dropped

1 messages · Page 1 of 1 (latest)

atomic helm
#

I've had this issue for a while, but I've finally done some investigating on whether the issue is to do with me or the keyboard (using https://github.com/DjCrqss/Woot-verlay) and to me it seems like the keyboard sometimes drops inputs when trying to move in CS:GO. I've got a recording of this happening so I know it isn't to do with rapid trigger disabling the keys.

First part of the recording shows the D key not registering to strafe properly and 2nd part shows the spacebar repeatedly not registering despite pressing it past actuation multiple times.

I recorded the video with my typing profile activated, which doesn't happen rapid trigger on and all keys' actuation point at 1.4mm (tachyon mode on). However the issue persists across all profiles I've tried with a multitude of different settings.

Quite frustrating when this happens in a game, as it occurs frequently enough to cause problems. If anyone has any suggestions on how to fix this I would greatly appreciate it :), it would be a perfect keyboard without this.

sturdy sapphire
#

Hmm.. I wonder if CS:GO has debounce problems where it will not update the input if it was pressed/released within one frame

#

The keyboard overlay is definitely indicating the keys are being pressed, so the issue is way more likely to be laying in the game's code

#

this overlay could also be used to get more information out of the sequence of your keys

#

more intended towards osu players, but could definitely help discover if the key was released for a few frames which may not be caught on DjCrqss's overlay

atomic helm
sturdy sapphire
#

In the worst case, there are definitely firmware solutions such as adding artificial debounce, as some kind of 'compatibility' setting for older games like CS:GO @pearl path
But it would be better if we can know for sure that that would resolve the problem before trying to resort to firmware changes

atomic helm
#

here's the issue being replicated with the other overlay. I'm not too sure what I should be looking for but I've noticed for every occurrence of the problem both keys seem to have been pressed simultaneously (at least in 60fps).

I tried replicating the issue both by holding down a key and lightly pressing and releasing but the issue happens when doing both.

sturdy sapphire
#

Well at least your keyboard is working great but maybe too well for CS:GO

#

Maybe we need to gather this information and ask their support team for details

#

I am kind of out of ideas right now

ornate garden
#

I'll just add some input I've played quite a few hours of csgo movement gamemodes like surf, bhop and kz as well as mm since I got my 2he and haven't noticed any issues like this so might not be a csgo localized issue

harsh plank
#

I have no solution but I just wanted to say I have 60HE and play quite a lot of CS:GO and this has never happened to me on this keyboard.

pearl path
#

Are you using nKRO on the keyboard?

#

also which keyboard model?

atomic helm
#

I’ve got a 2HE and I’m fairly sure nKRO was enabled for the tests I did

atomic helm
ornate garden
#

yeah no problem here's the profile code

#

i didnt really touch too much other then turning off angle adjustment and tachyon as i heard tachyon sometimes causes low actuation to not be accurate to what you set it, also haven't turned off gamepad or anything

fickle skiff
#

Just wanted to say that I got my 2HE a few days ago. Didn't change any settings except all keys to 0.8mm, enabled rappid trigger and tachyon. Works perfect so far and I love it. ❤️

untold bay
#

As mentioned before it could be a problem with csgo and perfect inputs being pressed on a perfect 1frame time span. This happened to me before but it eventually stopped I’m not sure if it was human error or csgo error, how long have you had your Wooting for?

atomic helm
#

Had it for about a month and a half now, the issue felt a lot more obvious to start with and I assumed it was just human error but I guess not :(

#

I’ve been travelling the past few days so I haven’t really tried a lot of things I could have

atomic helm
#

kinda want to revive this thread with an update: tried toggling nearly every option I could find in the wootility on and off; some seem to make the effect better, but the difference is so small it may just be random error.

#

I thought the issue was only present in csgo, however I've recently played rust and I've faced issues with keys sticking down despite not being pressed, I haven't tested this thoroughly but this (and many people saying this isn't a problem for them) is starting to make me think that this could be a keyboard problem instead of a game problem?

#

any advice I could use to troubleshoot would be great. I'm also going to try to use it on another computer and see if I can replicate the issue

sturdy sapphire
#

Again, if the inputs show correctly on the overlay it cannot be a problem originating from the keyboard as the keyboard displayed to operate correctly. Rather something between the keyboard and your game isn't.
Think of things such as operating system, Steam input, GeForce NOW, reWASD, InputMapper, Wootomation, Razer software/services. Anything that influences input devices.

small ridge
# atomic helm I've had this issue for a while, but I've finally done some investigating on whe...

I have found an issue where when I press down shift and drag my finger to the side the key stops giving input and have found this issue to be caused by a low actuation point. This only happens for the shift key, could this be similar to what is happening with your "d" key?

I wish they would allow for separate up/downstroke sensitivity for every key as currently it seems as if I can only set this for a group of keys if I want to use the rapid trigger function for multiple buttons. Similar as to how you can set multiple actuation points for keys at the moment.

atomic helm
small ridge
atomic helm
small ridge
atomic helm
#

i actually never got around to trying it on a different computer but i might do that today

atomic helm
#

Reviving this thread to say that I've tried this on a different computer, and the issue was not present

#

Any advice to try to get this to work with my current system?

ornate garden
#

easiest bet is to probably reinstall windows assuming it's something installed on the PC causing issues

atomic helm
#

anyone know if it could be a motherboard problem?

#

and if it could be then could a bios update fix it?

#

I'll try reinstalling windows in the meantime

atomic helm
#

just reinstalled windows and I think it's fixed? Hopefully this can help anyone else having this problem :).
I reset windows with the setting to keep data, tested it in game for a bit and I think everything works as intended '

wheat juniper
#

Were you getting drops in FPS? cl_cmdrate (number of packets sent to the server per second) is tied to your frame rate. For example, if your FPS dips below the server's tickrate (and your cl_cmdrate), the number of packets sent to the server will match your frame rate.

Also:

"The client creates user commands from sampling input devices with the same tick rate that the server is running with. A user command is basically a snapshot of the current keyboard and mouse state. But instead of sending a new packet to the server for each user command, the client sends command packets at a certain rate of packets per second (usually 30). This means two or more user commands are transmitted within the same packet. Clients can increase the command rate with cl_cmdrate. This will increase responsiveness but requires more outgoing bandwidth, too."

atomic helm
#

no drops in FPS before or after, averaging around 290 FPS, but it's an interesting possibility

alpine plover
atomic helm
#

windows reset isn’t that bad though, you can just move all your important files onto another drive and put them back after

alpine plover
#

hmm okay, i might have to try that then. I thought my keyboard was defective but i recorded a video with an overlay and clearly shows the key presses. Thank you for getting back to me, this problem was driving me crazy