#Rapid DKS
1 messages · Page 1 of 1 (latest)
This is interesting.
It didn’t make much sense before but since the secondary actuation point of DKS has now been made adjustable, it makes a whole lot more sense and can actually be quite an improvement. 😊
Just trying to think how this will be useful and not end up in a spaghetti mess of inputs . DKS essentially is a linear input that has 2 layers. Once you enter the 2nd, you can’t go back.
This setup would just trigger 4 moments over a shorter range and allow you to easier spam it.
It’ll be will impossible to control other than physical movement as current DKS but near impassible not to immediately actuate start and end.
All my explanations end up long af 😭
TLDR: For me, it would be far from impossible to control.
The benefits of Rapid Trigger translate directly to Rapid DKS.
Bigger DKS “ranges” benefit from Rapid DKS as much.
It can be used to spam or it can be used regularly (user dependent as it is currently as well).
For me personally, this would be far from impossible to control. The DKS “range” I used in the example can be bigger (3mm range: 0.1mm act, 3mm scnd act) or smaller (1mm range: 0.1mm act, 1mm scnd act). The main advantage of this is that the moment you release the key slightly, the secondary “release” actuation is triggered. It’s pretty funny, but yes, this setup would make spamming faster, especially with a range of 0.2mm. However, a range of 0.2mm as is currently, without Rapid DKS, is uncontrollable and can be used to spam. Or, it can be used for utility purposes and make them easier as you aren’t forced to bottom out the key.
I think the exact scenario that made me think of this was: Someone wanted DKS with a range of 1mm and had something bound to first “press” actuation (0.1mm) and to secondary “release” actuation (1mm). When he used it, it didn’t have his desired effect as he was unable to accurately press a key to 1mm and not further. He tried various DKS ranges but the issue was human inaccuracy. When using 0.2mm; he would press too far and the secondary “release”actuation would activate too slowly. When using 3mm; he wouldn’t press far enough, thus not triggering the secondary “release” actuation. 👍
DKS for crouch on 3.6mm down on a rappy snappy pair
But do you have a specific purpose for it?
And you you repeat DKS from action 1 to 4 after retracting triggering release or would last release trigger never trigger until you release entire key?
So then it’d effectively just be RT for the 2 middle actions, end of press and release of end of press.
Everything I (and most others as well) do with DKS would benefit from Rapid DKS. It’s more of a QoL thing really. With RT, the actuation point has no “thickness/range” it’s just on/off. DKS does, so how Rapid DKS would work is it’d treat the set DKS range as the actuation point.
Example, your total DKS range is 2mm (0.1 act, 2mm scnd act) and you press it to a depth of 3mm. When you release it by 0.1mm, the secondary “release” actuation point activates. Then when released >1.9mm, the first “release” actuation point activates.
It doesn’t function as DKS with Rapid Trigger, so take the previous example but instead of activating the secondary “release” actuation point when released by 0.1mm, it’d deactivate the key entirely. That is not what I’m suggesting. 🙂
Hi
Allow me to chime in. I hope this is not considered hijacking, but I'm actually trying to justify this feature.
basically, imagine combining Rappy Snappy with DKS using the examples attached
In this scenario, I would expect Rappy Snappy to work correctly, but as soon as the key passes the 3.6mm actuation down, it would trigger L-Shift
This is a good example perhaps, but you need to connect shift to the next action or it only triggers once, so This is still the 2 state key setup. It can alternate, for example, between walking and sprinting.
With rapid trigger this will make it much more responsive.
In this example we would be crouching in the extreme ends of A and D