Best Wooting 80HE and 60HE Settings for CS2: Rapid Trigger and Actuation

The Wooting 80HE and 60HE let you set the actuation point anywhere from 0.1 to 4.0 mm on every key, so the temptation is obvious: type 0.1 everywhere and own the fastest keyboard possible. Wooting itself advises something different. Its own CS2 guide gives a starting point of 0.7 mm on WASD, 1.5 mm for the rest of the keyboard and a Rapid Trigger sensitivity of 0.5 mm, and says that 0.15 mm sounds optimal but for many players it is not. Below is the whole setup step by step in Wootility, the ranges worth tuning within, and the rule you need to know before queuing: since August 2024 Valve kicks players from the match for hardware that resolves opposing movement keys.

Wooting's own starting settings

These are the values from Wooting's official CS2 guide, aimed at people who are just starting out on an analog keyboard. Treat them as a base for your own tweaks.

Wooting describes Tachyon Mode as turning off RGB effects, lowering the backlight brightness and putting input speed first. On the 60HE v2 and the 80HE it also enables true 8K polling. We covered the keyboards themselves in our reviews of the Wooting 80HE and the Wooting 60HE v2, so here we stay with the settings.

How to set it up in Wootility

Wooting explains that Rapid Trigger sensitivity is how far you have to let the key up for it to reset: the higher the value, the less finger movement is enough. Continuous Rapid Trigger keeps the mechanism working until the key is fully released, not only down to the actuation point, but at a 0.1 mm actuation Wooting calls it largely redundant.

Why not 0.1 mm on everything

Wooting recommends starting at 0.4 to 0.7 mm on WASD and 0.2 to 0.5 mm of Rapid Trigger sensitivity, depending on how steady your fingers are. The note on 0.15 mm is clear in that guide: it sounds optimal, but for many players it is not. At very low values a key reacts to minimal finger movement, so the risk of unintended inputs grows.

That is why it pays to go down in small steps. Start at a sensitivity of 0.5 mm, lower it by 0.1 mm after a few days and judge whether stopping after you release a key is better while movement stays predictable. If you start making unintended side steps, go back one step.

Wooting's profile and the pro profiles

The quickest way to see what Wooting set is to import its profile. In Wootility open My Profiles, choose Import profile, paste the code and click Import. Wooting publishes codes for its own 80HE and 60HE profiles and for pro profiles: according to the guide Twistzz (FaZe), Yekindar (Furia) and jks (FlyQuest), all on the 80HE. The guide does not list the values inside those profiles, so to learn them you have to import and inspect them in Wootility. The codes are in Wooting's guide, and more profiles sit at profiles.wooting.io.

We have the pros' mouse, crosshair and video settings collected in our report on CS2 pro settings, and full setups of the best players in the crosshair database.

Snappy Tappy and Rappy Snappy: turn them off before queuing

The same update tidied up binds: Valve ignores by default any bind that combines more than one movement or shooting command, so null binds and the classic jump-throw bind no longer work. The details, and the command that brings such binds back in practice with cheats, are in our CS2 commands list. We did not check FACEIT or tournament rules, so read their current regulations before playing there.

How to test it in game

The simplest way is to load a practice map with bots and practise stopping after releasing a key and switching direction from A to D. The cl_showpos command draws current position data at the top of the screen, and a ready command set for practice (bots, a long round, buying anywhere) is in the practice section of the same list. Change one thing at a time and give each change a few days, otherwise you will not know what worked.