Wootility v4.6.19 Feedback

[mortal fractal]

[lethal holly]

w

WS

is it more optimized than v2.7.3-beta.6 or just the same in stable?

[mortal fractal]

v2.8.0 is the same as v2.7.3-beta.6 except for a fix for an issue with the Toggle Key that was mentioned #1187862357720977530 message

[frail ermine]

[topaz viper]

[tacit canyon]

im cooked

[safe spire]

idk if this thread connected to Firmware: v2.8.0 or not
but i'm on the 60he
had v2.7.2 before, everything good
as soon as i updated and started playing there was alot of mis inputs / multiple inputs happening
i mainly play brawlhalla and it has an eac idk if there is a problem with that but i reverted to v2.7.2 and everything is back to normal

[frail ermine]

Can you test with this tool and post results here

[safe spire]

this is before the update ( consistent with no input issues ) v2.7.2

this is after the update ( i tried so hard to get the most consistant inputs ( there was still input issues ) v2.8.0

[safe spire]

this is also one of the results

[frail ermine]

This is so confusing xD can you press keys slowly and see if you get double inputs?

dont spam like this

[safe spire]

i played a game and noticied some inputs like this were i didn't take the action or put my fingers close to the button at all

[frail ermine]

You sure you havent touched that key accidentally?

if you have 0.1 actuation its even more sensitive now and could be the case

[tacit canyon]

try to limit yourself to one key and turn on actuation indicators

this is what cooked looks like on this new firmware:

#1196768306602983494 message

[sacred perch]

im actually surprised how big of a difference it is on my 2he, need to re learn and get used to it all over again

[frail ermine]

Yea I also noticed the difference especially in osu, 0.1 actuation is almost unusable

[lethal holly]

feels normal to me tbh

ive been playing 0.3 global and 0.1 on wasd on beta/test firmware basically since i got the wooting

[sacred perch]

Well then you just got used to it

[frail ermine]

yea its normal thats how it should be

[lethal holly]

what do you use global?

[sacred perch]

I got global at 2 it’s the 0.1 that’s messing with me now that I updated

On wasd and ctrl

[lethal holly]

o

[lethal holly]

why ctrl

isnt that a button youd NEVER want to fat finger

[sacred perch]

Yeah well in cs I wanted to have crouch more responsive

[frail ermine]

u may also need to disable rt on ctrl if you have it enabled

[lethal holly]

also #1047723220662485044 message

[sacred perch]

Yeah might change ctrl all together to something sane

[frail ermine]

[fluid reef]

Same issue here, I updated and went right into a game and was having input issues... had to revert back to 2.7.2

[nocturne wadi]

How do I save this thread?

Nevermind I just have to type in it

[thorn fern]

new fw for me is more stable for osu mania.

so far so good.

[lethal holly]

a

[wicked pier]

this is good but input is better than the 2.8.0

[lethal holly]

what

we are on 2.8.0

wait nvm im dumb

they silent updated

[visual bobcat]

I had to rollback 2.8.0 due to double inputs etc has it been fixed yet

[tacit canyon]

no they thought it was acceptable :/ but double inputs also happen to be hardware side a lot

[thorn fern]

new fw comes out?

[visual bobcat]

boo

[mint sapphire]

only 2.7.2 have no double click on spacebar for me

[lethal holly]

i have no double clicking issues, are you using tachyon mode perchance? if so did you check if you had double clicking issues without it

[languid jay]

latest uwu frimware has A LOT of doubletaps (look at the inputs especially the top one)

settings

[tacit canyon]

the shit ton of red on the bottom left tells me its the same issue

@mortal fractal we need that small filter option

if key is released to 4.0 then ignore inputs for .1ms 🙌🏻

[languid jay]

what I tought the reset point could be dynamically changed, so instead of rapid trigger (from current calculation) make a static actuation reset field
for example it activates after 1.3mm and deactivates between 0.7-1.3mm. Pressing and releasing between those a reset thresholds could be set to apply rapid trigger between that field or not. Sometimes when I have to tap fast I only press the switches down to those 2points and mot all the way down, but for maps that accuracy and precision is key, rapid trigger is not really good (for me)
And when I combine a fast map with precision inside I either fingerlock without rapidtrigger or miss entire precision part with rapid trigger

[tacit canyon]

I mean increasing the actuation point to above .4 works to remove the double taps

its just a weird timing where its registering the bounce

[odd sun]

Hey Simon, is it true that the keyboard recognized my o-rings now?

[tacit canyon]

Firmware firmcooked

[lethal holly]

what

what happened

[tacit canyon]

they never did anything with the double bouncey

[lethal holly]

idk its fine for me

is it an rgb bug?

or tachyon

[tacit canyon]

its a physical thing but it happens even on default wooting

[lethal holly]

weird

[mortal fractal]

The keyboard can handle o-rings fine currently, but there's plans to handle them better down the road

[mortal fractal]

I got a little something something for you. I was out for the past few weeks so wasn't able to make any progress until now

New test build for helping with the switch bouncing on release issue

1. Enable access to test builds by going to https://wootility.io/?test-builds=true (or https://beta.wootility.io/?test-builds=true)
2. Make sure your keyboard is connected
3. Go to Settings -> Updates
4. Under your device, press "Get Test firmware"
5. Once it loads, select v2.8.1-test.debounce.1
6. Install update

[tacit canyon]

Yay testing tonight!

[lethal holly]

theres a test debounce 2 now

cool

[undone wolf]

So is better ?

[lethal holly]

it should be

[tacit canyon]

So debounce 1 helps a lot using the analog monitor i barely get any and i’m trying to force it out instead of just normal full presses

like 1/25

[tacit canyon]

what is the difference between debounce 1 aznd 2

[mortal fractal]

There's some minor improvements to the logic on 2. Primarily to eliminate some false positives, I wouldn't expect it to change the behaviour much of filtering out true bounces

[mortal fractal]

Could you show me the cases where it still comes through?

[tacit canyon]

regardless its so much better than the 2.8.0

this is debouncce 2

[ornate garden]

what is the name of the program?

[ornate garden]

Thanks

[little saffron]

my wooting is not working after the update unplugged it and plugged it in it is not detecting my wooting

[tough spade]

i had same issue @little saffron did u get it figured out?

[mortal fractal]

Have you tried going through the troubleshoot flow to restore your board?

[tacit canyon]

@sinful fog

[wicked pier]

I cant update my woot60he with the new firware

[frail ermine]

why

[wicked pier]

IDK I did it with my wooting2he

I cant even fet the browers to see the keyvaord

keyboard

[frail ermine]

which browser are you using?

[normal grotto]

#💬│general message odd edge case malfunction discovered with mod-tap;

in short trying to build "home row modifiers" is not really doable on wooting boards due to this functionality being forced on with mod-tap settings

if you want to make your A key Ctrl on hold, trying to type normally is kinda impossible with any keysequence of A followed by anything else, as normal overlapping keystrokes when typing activates the Ctrl instead of the intended action, which is simply outputting A

suggested fix is to simply have the override as a toggle you can turn off, whereby the delay you can set would apply strictly, all the time

the "Permissive hold" section in the article describes the functionality and its up- and downsides https://precondition.github.io/home-row-mods#permissive-hold, we simply need a toggle to turn it on/off 😉

ah, in fact there's even more nuance to it in QMK, Permissive hold deals with sequences of "Hold mod, press and release a key, release mod" and Hold on other key press deals with sequences of "hold mod, press another key (regardless of release order)"

it's all in the article, perhaps if you look into it you can try making it as robust as possible

[normal grotto]

tagging @mortal fractal to make sure this feedback is seen since it's an old thread and no indication was given that anyone saw this haha

[split bone]

I'm bumping this too. Home row modifier keys are becoming more popular, i'm recently on this bandwagon and I want to give this a go on the Wooting 80HE, but can't atm.

[mortal fractal]

Essentially just need to have the option to turn off the "Just in time" behaviour? like this https://github.com/WootingKb/wootility-issues/issues/309

@normal grotto

That has been on my personal list for a while, I'll see if I can sneak it in soon 👀

[normal grotto]

disable toggle would go a long way, but if possible I'd rather see the full suite of functionality:

• hold key, press-and-release another (permissive hold)
• hold key, press another (current functionality)
• default functionality (i.e. no additional logic past hold term)

or explained in other words in the qmk docs: https://docs.qmk.fm/tap_hold#tap-or-hold-decision-modes

[normal haven]

Not sure I understand this properly, but basically

there should be an option to not make the mod key activate automatically and instead only after a delay.

[normal grotto]

yeah that's what we want to see, for one

there are more handling schemes that could be beneficial

[normal haven]

Any update on this?

[mortal fractal]

Soon™️

[mortal fractal]

Checkout the latest beta :) #📰│wootility_updates message

[normal haven]

noice will test it at home 💪

[urban tiger]

I’m experiencing the same delay mentioned above. I have for instance “s” mod tap bound to:

Hold = PG DN
Tap = s

I have disabled JIT, and raised my press delay to 500ms and still experiencing input delay issues. For example when typing the word, “simon”, the input delay causes the word to be “ismon”.

Has this been addressed? I’d love to be able to setup a whole set of home row mod tap functions.

Thank you!