I'm quite certain the rapid trigger on / is because of you are using ANSI layout and the imported profile is from ISO layout board. I believe both Jinggg and derke uses ISO layout boards.
I hope the next fireware update it fixes the issue with the 60he spamming random keys. The only way i fixed it was to go back to 2.7.2 anything past that would just bug out the keyboard
@@Wooting Yaay! Extra features! They are always welcome. Not the other way around where companies take away features. Anyways I hope the best for your growth! ❤️
What are your recommendations for advanced options on rapid trigger, or is it just recommended to be off for valorant? I know its personal preference, but I would like to know your opinion.
@@Wooting Still dont understand how it works completely, as ive tested on the 'Test your keybinds' tab, and it has yet to show any difference between it being on or off. Im really trying to understand this setting and how it can be beneficial
I set my movement keys to 0.6/7 I have rapid trigger on; on both press and Release(custom sliders for both). When I am moving around In apex legends sometimes I just stop moving until I press a movement key again. Is this because pressing WASD pretty fast cancels out the last pressed key or is my keyboard defective?. Thank you ! Love the keyboard 🔥
Could be rapid trigger sensitivity being too low. Lowest sensitivity of 0,15mm can be too sensitive. Try something like 0,30-0,50mm if you haven't yet! :)
I had a similar issue while playing Team Fortress 2, and I fixed it by increasing the 'release' Rapid Trigger setting to around 0.5mm. This, alongside the SOCD setting they just released in the beta version, allows me to get super quick response every time I press a strafe key, but without accidentally stopping my movement every time I slightly release my WASD key. I had incorrectly assumed that my movement errors were related to "fat-fingering" a second key, but in reality I was releasing one of my movement keys very slightly, and rapid trigger was de-activating that key. Like the Wooting rep mentioned, I would increase the rapid trigger 'release' setting to something like 0.5-1mm and check if you still run into the problem. If not, then that was your problem. If your problem persists, then you'll have to do some more troubleshooting.
I don't fully understand the L-Shift on 2.8 explanation, how does that give a shorter deactivation? Would enabling Rapid Trigger on that key not achieve an even better result?
Across the board, you don't go wrong with either really. 1.2mm is just a tad bit faster on the actuation and is still far enough to not really fat finger it.
It is on the list I want to address. I don't know any specifics on Fortnite, but I will make sure to do several interviews with pro's and advanced players to understand what would make a good profile.
Is there any way to set up your keyboard to work like a controller thumbstick? where the farther the actuation point, the faster you move? Like .1 is walking slow and 4.0 is sprinting?
@@coemgensclips So, a little clarification, I use the default racing analog profile, which is basically only trying to replicate a controller thumbstick by itself. But if you want to replicate sprinting with using only a single key (which will be replicating your thumbstick fully pushed in a single direction, PLUS pressing the sprint button), you'll have to use the DKS feature. Wooting has a tutorial for it on this channel, just search for "How to Use Dynamic Keystroke/DKS" and you'll see it.
This software is doing its absolute best to stretch the definition of 1=1 input and i think it's a bad play to make in the competitive scene. I dont want to see who has the best keyboard settings, I want to see who is the best player.
