So, I recently got my Wooting 2HE and I only had it for 3 days now. Since first day that I got the keyboard, I have this weird problem while playing Valorant. While moving, sometimes my WASD won't work properly. There were times where I am pressing W and it won't register, I had to press it multiple times just to move forward but even then it doesn't work all the time. It is getting frustrating. I have tried all the extra cables that I brought, tried the usb c adapter, tried just the default but nothing fixed it. It is still the same. Any help would be appreciated.
#Wooting 2HE
1 messages · Page 1 of 1 (latest)
Discord
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
you are editing an inactive profile, move the profile to the top most position on the left
can you try using the rapid trigger display rgb effect and see if the switch works correctly?
No. I have tried everything the other guy told me on my other post and it is still happening.
I will try to do that later.
I have and it does.
Maybe Valorant doesn't play nice with the emulated controller driver that's enabled by default. You could try disabling that?
Settings -> Keyboard Settings -> Gamepad Mode
I’ll try it. I did a test earlier when I booted up my pc. I went straight to valo and just ran around the map. It seemed ok in the first 10-15 mins but it started doing again after. Idk what to do.
your rapidtrigger sensitivity is set too low my friend
Yeah, the thing is I tried changing that too, but it is still happening. 💁
Have you tried checking if any Language typing support software like Unikey or Windows is enabled?
i just got twoHE also and its working fine with me.
or u can try to use this profile :
78c98d47a9e93ddd39815616f73bf16df915
@lapis coralwhat firmware versions did you try?
I am not sure, I bought a new different keyboard already. But I’m assuming it would be whatever it install with after updating for the first time.
New keyboard aside, I would still love it if the issue could be fixed.
thats why im asking what firmware version
sounds like the update might fix your exact issue
i was about to recommend the latest beta because our firmware dev is trying to get all those edge cases where the analog signal gets misinterpreted briefly
I updated the firmware. Hopefully this fixes the problem. I will be doing some tests to see if it still happens.
please do tests and if not please report back so i can get the firmware devs involved if needed
this is stuff we wanna fix before the next stable firmware
Will do thanks!
After playing for more more than 8 hours for two days, I'd say the keyboard has been working fine now.