#Feedback/Request: Arbitrary SOCD handling configuration.

1 messages · Page 1 of 1 (latest)

fading garnet
#

So, as a preface, with Rappy Snappy as it exists now, and Razer's Snap Tap, they're both just different ways of doing SOCD resolution. We've been dealing with this in the FGC for the better part of 20 years now, and it's cool to see it come to general purpose keyboards, however, there's a bit more to explore.

Rappy Snappy is, essentially, most-pressure-wins SOCD resolution. The key that is pressed down the furthest is the one that is active whenever there's a conflict along a specific axis. (W/D for instance.)
Razer's Snap Tap is latest-input-wins SOCD resolution. The key that is pressed down last is the one that is active.

What I'd like to propose, assuming we get latest-input-wins in Wooting at all, is not limit us to these two scenarios. Sure, there should be presets for those who just want to activate those specific features by name, however, there is not much to lose by making the feature more customizable.

For instance, in some FGC rulesets, it is required that two opposing inputs are entirely cancelled out. As in, pressing W and D, will cancel both inputs, and do nothing. It would be cool to also have this option built into Wootility, as this would lead to more complete SOCD handling. Maybe whenever someone chooses two (or more, even!) keys, just have a drop-down to define the SOCD behavior of that specific key group, whether it is most-pressure-wins (Rappy Snappy), latest-input-wins (Snap Tap), or no input.

dapper geyser
#

Hard agree, I'd love to be able to set mine up so it's latest input wins but uses the reverting mechanic of rappy snappy in combination with rapid trigger so that it acts the same as snap tap for the most part except if i start lifting up D and A is below it's actuation point the input switches to A

#

i think they just need to make very clear in what games it's been allowed or not

#

maybe have a little lookup table where you can see what features have been allowed/disallowed by specific games such as any rappy snappy for osu

fading garnet
dapper geyser
#

oh damn i didnt know dks was bannable as well

#

yeah maybe just a single note when any of these features are enabled to make sure you check if the games allow it

fading garnet
tall yacht
#

I think this would be great but many Wooting team member have voiced their opinion that it should be separated. Some even disagree that RS is a form of SOCD handling and wouldn’t call it SOCD at all! I would love to see this but I fear that it won’t. :/

ocean geyser
#

boi have i got news for you guys.... check the beta wootility web

tall yacht
#

Neat.

#

Very

dapper geyser
#

making it so that it acts as last input priority except that when you have both keys held down and you start to release one the other becomes active

tall yacht
ocean geyser
dapper geyser
ocean geyser
#

so rapid trigger. the key deactuates at whatever sensititvy when you move up

dapper geyser
ocean geyser
#

yes its still active

dapper geyser
#

oh shit thats perfect

#

and then if you like press D half down, press A a little down, then start pressing D down more without first resetting it D activates after A does?

tall yacht
#

That’s with both SOCD and RS.

dapper geyser
#

awesome

#

yeah i'm sold

#

after i financially recover from my pc i'm buying 80he zinc alloy with jades

fading garnet
spice obsidian
#

honestly, IMHO Rappy Snappy is just a SOCD resolution, so I would just merge them into the Rappy Snappy Feature and put 'Depth Based' as the first Option on the SOCD selection box

tall yacht
#

Objectively, Rappy Snappy uses first input priority when both keys are at the same depth. If that were to be removed, one could still argue that because RS uses information from two keys and it overrides a game’s SOCD handling that it is SOCD. So, at the moment it objectively partially is, and subjectivity(?) could or could not be. To me, RS is depth based SOCD and that’s it.

ocean geyser
#

the issue is that if both keys are pressed to the same depth you still sort of need some socd handling

tall yacht
#

I’ve used RS w/o SOCD handling at the same depth, it’s not that bad. It’s worse for sure but if you don’t want to call RS SOCD, that’s what you’d have to do imo.

spice obsidian
#

changed verbatim above to project your inputs. All this to try to simplify interface. KISS