#DKS issue: keys stay activate after full release, or same key double active.

1 messages · Page 1 of 1 (latest)

ornate valveBOT
#

Thanks for posting your support request!

Please note, the support center is only for community-based support with technical troubleshooting and general questions.

For official Wooting Customer Support, please use the Contact Us button on the Wooting Hub or email your request to social@wooting.io
note: use the email address associated with your order for fastest resolution

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, change/confirm your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it On Hold via the Wooting Hub!
https://hub.wooting.io/login

reef mason
#

DKS issue: keys stay activate after full release, or same key double active.

hoary glade
#

Is this active or not?

reef mason
#

Sorry, I tried to delete the post, but kinda failed.

It seems the problem was solved by configuring the DKS keys differently

#

@hoary glade can I ask you a question about DKS configuration? related to the issue I had?

#

I have it set up like this now, without keys getting stuck etc. so working ok

image.png
hoary glade
reef mason
#

But ideally, I'd like to have it like this. So that the 2nd key activates sooner, when I start to release. The problem, I discovered, was that when half-releasing D, and repressing it. D would not activate again. That would be ideal, do you know how to get that result? Rapid trigger seems disabled for DKS keys.

image.png
hoary glade
#

Why not add another binding for D between point 2 and 3?

reef mason
#

Like this? will try

image.png
hoary glade
#

Yes...

reef mason
#

whoah, it seems to work. I woulda never thought of that

#

I doesnt make sense to me, but it works like madgic

#

thank you 🥲

hoary glade
# reef mason I doesnt make sense to me, but it works like madgic

The holds are continuous and 1 & 4 and 2 & 3 dependent to each other. Meaning 1 can only be triggered if the key was fully lifted before, like it happen when you reach 4. Because they are continuous if you have it on 1 to 3 like in your example the registration can't reenter the activation state in-between on 2 and you need to reach 4 again. By creating two sections with 1 & 2 and 2 & 3 you can mitigate the continuous limitation.

#

This would be the clean approach for what you want:

image.png
reef mason
#

I see, with the explanation it makes sense why it's made like that

hoary glade
#

I totally forgot that this is possible these days. Back in the day the UI didn't allow that and would just make a continuous hold and so combine the two sections. Luckily these days this is possible.

#

Back in the days you need to do this to get around the UI limitation and this is basically the same as I recommended before.

image.png
reef mason
#

Yes indeed. Not sure if it's documented somewhere, and I missed it? the content I found was more general, didnt go into the details like this

hoary glade
#

For the example here it doesn't matter if 1 only goes to 2 or 3 because of the second part of D in the firth row the result would be the same.

reef mason
#

Yes indeed, the D actually has 2 seperate actions, it just split into 2 lines (or not)

hoary glade
#

Think of it in an event based manner. The keyboard basically only see the events happen at the four points.

#

For a hold only the start and end matters, so can't jump in-between. This is intended and if you want that you only need to split them up into their sections.

reef mason
#

got it!