#Remove the 0.3mm actuation point compensation

1 messages · Page 1 of 1 (latest)

verbal shore
#

I noticed this as an issue when I played around with the settings in Wootility. If you de-activate rapid trigger and fully rely on the actuation point to be your pointer and set it to 1.2mm for example. If you push down the key to 1.2mm, it will activate, but then if you let go of the key beyond 1.2mm it will still be count as pressed down until 0.89mm. This behavior remains independent of what you set the actuation point to - there is always a 0.3mm actuation point compensation. You set the actuation point to 2mm, it will only reset your input at 1.69mm and so on.

I first thought there was a problem with my unit, but in a customer service ticket I had it confirmed that this was an intended feature meant to compensate for end-users so that a keypress wasn't accidentally let go off.

This to me is very annoying as a user, and I would really like you to give us the option to turn this compensation off, so that the key activates and resets at the same actuation point.

As a consumer I feel kind of misled by your marketing. I want to recall this being mentioned as a feature plenty of times (meaning; having NO compensation for actuation points). In this video for example: https://youtu.be/eZENx1T7OLw?t=127 you really make it seem like we can put the actuation point to be any value, and have the key press be reset if the key is let go beyond that set value, without having to rely on rapid-trigger.

YouTube
Wooting
What is Rapid Trigger & Actuation Point? (and how to use it)

What is Rapid Trigger? What is Actuation point? In this video, we explain Rapid Trigger, a Wooting feature designed to make your movements faster than ever. Before diving into how it works, it’s helpful to first understand what an actuation point is and what it does.

We’ll also show you how to apply Rapid Trigger to your 60HE or Two HE keyboar...

▶ Play video
fast shuttle
#

Interesting. This is, presumably, a bug. I don’t see why a deadzone that big would be necessary throughout the stroke as it isn’t necessary with RT enabled.

sharp summit
verbal shore
verbal shore
dawn steppe
#

Maybe ask to add a toggle to this feature. Then the feature isn‘t forced or at least users can opt-out or opt-in. Depending on wootings preferences

sharp summit
short raven
#

This is something that is due some changes, as this behaviour is something from back in the Flaretech days and hasn't really been changed since. It has nothing to do with calibration btw.

The biggest challenge we have with this is UX. As this has been the behaviour for a long time, it's not something we can just change for everyone, as some people may rely on the current behaviour. So ideally then you'd want it as a setting, but presumably you'd want it on a per key basis per profile, which then brings out the trickiness of it.

This topic had kinda escape my mind, so I will make a push internally to try and get UI/UX figured out for this. There are various bits we're working towards with Switch configuration, so it would be good if we can tackle this as well :)

#

It'd be helpful if those interested in changing this. What exactly are you looking to do, so we can shape around those use cases.

e.g. Just want to make it lower/removed, or maybe you want to have it different on different keys, would you care about it being per profile etc

#

The simpler we can make it the sooner it can be shipped

verbal shore
#

For me personally it would be enough with an "on/off" option (maybe called deadzone) for **all **keys. If set to "off" then the actuation point acts as both the activation and deactivation for the keypress/input. If it's considered an "easy" fix to just add the on/off option for all keys, I think that's a great start. The default value could be set to "on" so that the behavior remains unchanged for users, unless they actively decide to change it.

I personally cannot see a use-case for configuring individual keys to behave differently, and/or to adjust what millimeter the key activates/deactivates. I personally feel that this need is satisfied through rapid-trigger. But maybe some other users are interested in this as a feature.

fast shuttle
# verbal shore For me personally it would be enough with an "on/off" option (maybe called deadz...

I really don’t understand why a deadzone this big exists or is necessary. For RT, it’s 0.15mm (throughout the stroke) rather than 0.3mm. It should be changed to 0.15mm as that is the “accuracy” Woot’s HE boards can offer. I don’t see how people could be relying on a 0.3mm deadzone that much that they’d be hindered by the normal 0.15mm deadzone. When Woot offers higher accuracy, then there could be an option to lower the overall deadzone but not before. I agree, I don’t think per-key adjustability for this is necessary either.

fast shuttle
#

The threads in #📰│wootility_updates are more for bug reports though, but something like this fits as well (even though it might not be a bug).

verbal shore
wispy pumice
# short raven It'd be helpful if those interested in changing this. What exactly are you looki...

I think a toggle option would be amazing for those who dont want a dead zone and for those who would like a deadzone, and down the future you can add the ability to change the dead zone distance.

Per profile would be amazing and different keys too. im really surprised you guys havent experimented with the idea of dead zones, since almost every other HE keyboard has the ability to change their keys dead zone.

#

and im super glad someone also pointed this out, since i was wonder why the Wooting has a slight delay in key presses while using RT

short raven
#

Thanks for the feedback all!

short raven
#

The only reason I wouldn't just change it is if people have ended up relying on how it has been behaving
xkcd: https://xkcd.com/1172/

xkcd: Workflow
There are probably children out there holding down spacebar to stay warm in the winter! YOUR UPDATE MURDERS CHILDREN.
#

But I am tempted to just change it for a beta release and see if anyone notices, if not, then my concern would probably be invalidated and we can just go ahead

wispy pumice
fast shuttle
short raven
short raven
#

Ultimately, whatever the reset point is relative to your actuation is mainly just to avoid issues caused by noise, i.e. if you were to hold the key at actuation and noise causes it to fluctuate between the reset and actuation point. At least on ARM boards, it's pretty obvious that it's pretty much a non-issue as the noise filtering we have since the big scanning update last year is pretty good

wispy pumice
#

or i could just be stupid

verbal shore
#

Let me know if it does end up in a beta-release!

short raven
verbal shore