#"A" button is glitching in every FPS games (firmware 2.9.1 beta only)

1 messages · Page 1 of 1 (latest)

storm pelican
#

Problem: Character in games randomly strafe to the left even tho im not touching "A" button, i tested in Valorant, CS2, OW2, and lately Apex, also tested on keyboard testers online and no sign of button stuck or any of that. I'm 100% sure i dont have this problem when i use firmware 2.7.2.

Specifics : Wootility v4.7.1-beta (Web), OS: Windows, Device: Wooting 60HE, v2.9.1-beta.0, with SOCD and rapid trigger + tachyon on, not sure it they are related or not but want to give out the most info.

I have already tried: Hard reset the keyboard on the website, clean the keyboard physically in case it's too dirty (but it's not), use another USB port on my mainboard, switching cables, revert firmware back to 2.7.2 (this one trick fix everything) but i love SOCD so i go back to the 2.9.1, trying to adapt the glitch.

#

@twilit bear i made a post, thanks for helping me out man

#

im not sure if you guys can see it or not, but in this clip my character strafe to the left a damn lot so i have to adapt it, and by far the only clip that i remember to record, it happens randomly for about 2 seconds so sometimes im just too locked in during the game that i forgot to record.

#

And also in this one, the moment where i jumped while reloading the gun when another guy is shooting at me. I have to jump because my character keeps hugging the wall so hard that i had to played with it. Super frustrated during the match but turns out a good highlight (?).

twilit bear
#

What is your actuation point setting?

twilit bear
#

@storm pelican

#

@thorny oak btw

storm pelican
#

0.1 all the time for all versions, but it didnt glitch before 2.9.1, im actually back to 2.7.2 now and it's currently going smooth in cs2/vlr. About to test OW2 now.

#

Sorry for late respond, i was in a game.

#

it also have the same problem in 2.8, before the 2.9.1 update. But it doesnt have SOCD so it didnt really bother me that much to create a post lol

twilit bear
#

In v2.8 we introduced a big overhaul to how the keys are scanned. This made the 0.1mm setting significantly more sensitive than before

#

One thing that I would make sure, is that you aren't accidentally resting your finger on the key, as that could cause it to stay input for longer than you intend

#

If that is not the case, then it could be something not ideal with the calibration or your keys not returning to an identical resting position.

For this one, you can try something like this: https://w3c.github.io/uievents/tools/key-event-viewer.html
And just press the keys normally (ensuring you fully release) and see if you see the release of the key on the page at the same moment that you have fully released the key

This potential issue in particular I normally only observe on keys that have stabilisers, as that can cause some inconsistency in the resting position of the key

storm pelican
# twilit bear One thing that I would make sure, is that you aren't accidentally resting your f...

yes i ensure to you that i dont put my finger on the "A" button, i usually lift my finger to the "Q" button above it, but the character just casually move to the left itself so randomly, even sometimes where my finger is not even on the keyboard. For your information, i noticed one thing when using the event viewer, my key is working normal, i fully released it and there's no delay or key keep pressing down, BUT when i open the game and get into a match, somehow just a small vibration on my A button would make it become like this (this is where i open the game AFTER i already tested the event viewer on 2.9.1 but let the game run in the back ground and reply my test to you)

"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaadddddddddddddddaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaadddddddddddddaaaaaaaaaaadaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"

On the text above, i hovered both my finger on A and D at the same time, and the A button is SUPER SENSITIVE, but the D button needs more force to take a command.

I also noticed that it's only MORE sensitive when a game is open, i don't know how to put it into words, but my "D" button have the same setting on rapid trigger and SOCD as my "A", and i hovered both my fingers on both of them to see why is my "A" button taking more commands from hovering than pressing hard compared to my "D" button while in SOCD mode but only when i'm in a game. After the "A" key goes for 10 times, i stopped pressing down the A key, not hovering on it, fully released to make sure of my test but it keeps on going until i pressed "D" or pressed "A" again.

One more thing to point out, where im in the lobby of the game (that means it doesn't have anything to do with the "character movement system" i suppose), the key just casually becomes normal. But if i open up the game and boot into a match, or even in practice range, where i can actually move the character, the problem happens again. I hope my information is useful because im currently lost of words, i know this sounds crazy but please take a look into it, i promise im not tripping, i even flip the keyboard for the test to make sure my ring finger pressed the same force to the "D" button but it's not taking any command that looks like a long press or hold, just a single "D" and it stops.

#

Not to mention, before the update, version 2.7.2 works fine, I never ran into this problem, if it's sensitive, then it should be the whole keyboard, not one button, i have a clip to prove now, but it's me typing to you guys while Valorant is running in the background

#

I recorded from the beginning so yall can see my typing progress, it happens randomly, just like i said

#

I zoomed in for you guys

thorny oak
#

hmm you can try out the "Wooting analog Monitor" software to see how the switch is being proccsed might help show the issue with the firmware

  1. you can Download the software from #1196768306602983494 message.
  2. Once downloaded click on “wooting-analog-monitor.exe”
  • If you receive a notification that you are missing the "Wooting Analog SDK," you can download and install this software from our GitHub:
    https://github.com/WootingKb/wooting-analog-sdk/releases
    For Windows users, this will require the installation of wooting_analog_sdk-0.7.5-x86_64.msi
     
    Once installed try running the “wooting-analog-monitor.exe” again.
  1. Once the monitor software is running can you check for the behavior below and press the [Save Plot] to take Screenshots.
GitHub

Native support for Analog Keyboards #WootDev. Contribute to WootingKb/wooting-analog-sdk development by creating an account on GitHub.

storm pelican
#

Thanks, i got the proofs now, @thorny oak, please check your DM

thorny oak
#

#note provided video of the "wooting-analog-Monitor"

hmm there was one point that seemed off.

storm pelican
#

What's off ? Can i do anything to clear it for you ?

thorny oak
#

had to crop the picture
looks like the switch is not returning to the resting position Just slightly above it

#

do you have any keyboard modifications
switch pads
foam
etc?

storm pelican
#

Like this ? It's where i didnt fully release it. I test on both scenarios : 1. Fully release at first in the video 2 : released only half of it and pressed again. I want it to trigger the problem so i went on doing both

storm pelican
thorny oak
#

oh if you did not release it fully then i am overly thinking the data i shown above

storm pelican
#

Yes, i just want to trigger the glitch again, i also sent you a video where i tested one more to clear things up.

#

If my theory is right, it has something to do with the movement mechanics of the game, and because i mainly play FPS, i havent test it on other genres yet (im thinking about testing it in LoL where A button is for auto attack but im not sure if i could trigger the glitch there) but i ensure that if there is a movement mechanic of a game that's running in the background, the glitch pop up again.

thorny oak
#

got to say you are very consistent on not fully releasing the key tried to mimic this an failed horrible

storm pelican
#

okay i'll take it as a compliment

#

But i wasnt trying to mimic it tho, i want to create a scenario where i would rapidly tapping the button to jiggle peek, or just slowly strafing to see if the glitch is triggered or not

#

The weird thing is, on my typing video (the one that i recorded on my phone), it keeps going for like 10 seconds, that's scary to witness

thorny oak
#

just checking did rasing the keyboard fix it or did you press A aswell ?

storm pelican
#

i have to press A again to stop it from the glitch

#

eventho i love SOCD, i have to get back to 2.7.2

#

This glitch made me lost so many games today, i deranked 😢

storm pelican
thorny oak
#

ahh tought it could of been related to external factors when i saw that video

but yea i suppose till the issue is address in the next patch

storm pelican
#

thank you so much for your help ❤️ If SOCD is in 2.7.2 it would be the best but i guess i have to wait for the next patch then

#

Okay, hear me out, this might be a problem, somehow when i make a revert back to 2.7 now, my A key is disabled.... I cant type or use it, but update it back to 2.9 it works magically fine again

#

But still with the glitch

storm pelican
#

Hope it helps !

near timber
#

i got the issue in league of legends aswell playing swarm game mode..

#

so the A key is running on its own..

#

when will they patch this?

storm pelican
near timber
#

can we fix this issue?? pls wooting

faint furnace
storm pelican
#

it was already there when i install Discord so im not sure