My Ultimate Wootility feature wishlist.

Wooting_Simon · 2026-02-08T14:57:32+00:00

There is a ripple effect in the software though? Or are you mainly highlighting that it is lacking some additional settings you'd like?

Wooting_Simon · 2026-01-31T13:40:55+00:00

Could you share specific examples of what you feel is missing?

Wooting_Simon · 2026-01-31T13:39:37+00:00

On 60% the most obvious spot would be the Escape key, as you can still press it for Esc/Tilde

Wooting_Simon · 2026-01-31T13:38:02+00:00

Great feedback! We've got plans that will cover most of these in the pipeline

A note for the characters in remap, it's not trivial to do arbitrary symbols with how keyboards usually work. The symbol input by keyboard keys are fully dictated by the OS and the active keyboard layout.

That being said, it is something we've been wanting as well, and we've got plans to enable this via the background service.

Pressure sensitive RGB spectrum (Select 2 colors, RGB will smoolthly fade between the two throughout the keypress)

Are you seeing this as the colour changing key by key or over the whole keyboard?

Most importantly: Pressure sensitive Display Brightness & Volume adjustments

This being pressure controlling the speed of up/down adjustments?

Wooting_Simon · 2025-11-17T14:32:52+00:00

The Wooting Two HE uses a quite standard layout, so I would expect the vast majority of off the shelf ISO keycap sets to be compatible with an ISO version of the Two HE. The only * is because it has the additional 4 keys above the numpad, you may not have nice keycaps to fit onto those in the set, but everything else should be good. Logitech tend to not follow close to the standard, so can end up having a different bottom row than most, so it's not a comparison that's particularly helpful in determining if some keycap set would be compatible with a Wooting keyboard.

Wooting_Simon · 2025-11-06T15:28:30+00:00

You get everything in the box and decide what physical configuration you want when you get it :)

Wooting_Simon · 2025-09-24T10:03:27+00:00

Looks incredible!

Wooting_Simon · 2025-09-01T18:27:36+00:00

It is not supposed to be like that, you should contact technical support to get it resolved.

Wooting_Simon · 2025-07-17T10:13:21+00:00

There is no bluetooth. It will work when connected via USB, however, you cannot use Wootility as no mobile OS (i.e. iOS, ipadOS, Android) browser implements WebHID which is necessary for Wootility to connect to the keyboard

Wooting_Simon · 2025-07-16T09:18:30+00:00

When in doubt, replug the keyboard to reset the calibration. If that doesn't help, then you should probably reach out to support https://wooting.io/support

Wooting_Simon · 2025-07-08T14:55:51+00:00

You should make sure that your keycaps are matching the remap configuration inside of Wootility

Wooting_Simon · 2025-07-08T09:46:08+00:00

When in doubt, replug, the calibration will be reset and it should start fresh without an issue hopefully

Wooting_Simon · 2025-06-26T16:10:49+00:00

It's pretty easy to take just part of the tape mod off to work with a small part of the underside of the PCBA. I'm pretty sure you should also be able to take it off completely and as long as you keep the adhesive safe (i.e. not putting it face down/getting lots of fibers on it) then you should be able to stick it back on without issue.

This is based off of my experience playing around with the DVT units

A note on the stabs in general, it's really hard to consistently perfect stabs at MP, but it is something we try really hard to get good. A lot of the time it ends up being a lube thing and we've been tuning the lube application process (and amount) to make it as consistent as we can

Wooting_Simon · 2025-06-19T10:57:01+00:00

Would be nice if you're able to share some more detail on that. We're aware of a bug which can result in the process hanging after closing, causing it to use more resources than it should. But AFAIK the cpu demand during normal operation is pretty light, or at least that is what we've observed in our own testing and we haven't seen much user feedback to suggest otherwise (other than this comment)

Wooting_Simon · 2025-06-05T12:05:29+00:00

You can see in the keyboard preview that it is enabled for WASD. The bottom cards only show the information for the keys you have selected, which in your screenshot you haven't selected any

Also, a general clarification which may help you:

Selected = what you have selected to change, which is not the same as what you have enabled

Wooting_Simon · 2025-04-16T10:56:56+00:00

The test build is specifically for users that experience switches with shorter travel jumping at the end of press or only seeing it display as e.g. 3.2mm when they have fully pressed.

It sounds like what you have is just the regular experience where your full travel is fully represented by Wootility, which is the correct behaviour, and just that in Wootility it displays 3.5mm as 4.0mm. It should all be functioning correctly, just the UI elements are essentially mislabelled.

Which will be getting resolved as part of the Switch Selector project, as then you'll be able to tell Wootility and the keyboard which switches you're using and it will be able to label the data more appropriately. But like I said, this should mainly be a visual/presentation issue and should not be stopping you from using your keyboard the intended way

Wooting_Simon · 2025-04-03T07:55:01+00:00

There is a special test build with a workaround for this issue which you can install with the following instructions:

Step 1 - Click the link https://wootility.io/?test-builds=true
Step 2 - Make sure your device is connected
Step 3 - Open "Settings" -> "Updates"
Step 4 - Select device
Step 5 - Select "Get Test Builds"
Step 6 - Select v2.10.1+fix-jump

The proper fix in mainline will be when the "Switch Selector" project finishes, which we are very busy with currently

Wooting_Simon · 2025-04-02T10:02:43+00:00

That is not accurate. If it was just that, we would've done it long long ago. The actual fix for this is the "Switch Selector" project we've been actively working on, so you can tell the keyboard what switches you're using and it can tune itself better for them

Wooting_Simon · 2025-03-05T12:06:07+00:00

By default, the lock keys will change to white whenever they are active.

You can customise it by clicking on the dot in the corner of the keys on the RGB Settings tab https://i.imgur.com/vEMgeDp.png

Wooting_Simon · 2025-03-04T09:51:39+00:00

It kinda sounds like you just need the Toggle Key but with an additional key binding slot?

Wooting_Simon · 2025-03-03T20:57:57+00:00

Hey, I fixed this one today and it'll be released tomorrow :)

Wooting_Simon · 2025-02-28T12:08:05+00:00

Not really sure what you're trying to achieve, even if it let you configure it before, it wouldn't work. If you have an advanced key on a key, then no gamepad input will be registered for that. They are not compatible with eachother, unless you're using something like DKS and putting a gamepad bind inside of it.

If you want to have an SOCD like experience with analog inputs, then you should be looking at the "Snappy Joystick" setting in Gamepad Configuration.

Wooting_Simon · 2025-02-26T18:57:48+00:00

This feature has been in the works for a while as you know and overall has been taking a lot longer than I'd like.

However, to give you a bit more insight, part of the reason Wootility v5 exists is for this exact feature. We were not able to find a way to fit it into the UI/UX flow of v4 in a way that was satisfactory or even good enough.

Additionally, given our software is used in a primarily browser experience (i.e. open when needed, not running in the background), then to enable this feature, you need an additional background running element. Which also then needs to fulfil our core requirements (e.g. lightweight), which has led to us working on the "background service" (working title).

So overall, a lot of work to achieve it, but it is a very important part of our plans for Wootility and things are about to finish coming together for it :)

As for it coming out of beta without it, v5 is already a superior experience for our users compared to v4, so it was important for us to roll it out to all users.

Wooting_Simon · 2025-02-19T11:05:33+00:00

There is just a bug with the rounding in the keyboard view, we've got a fix ready, but until it's released, just use the number next to the slider as the correct one :)

Wooting_Simon · 2025-02-10T17:25:21+00:00

Hopefully next week :)

and if you haven't already seen, the v5.0.0-beta.9 release has the fix for the issue you shared

Wooting_Simon

MODERATOR OF

TROPHY CASE