v4.5.5 Stable Branch - Feedback

[final yarrow]

[floral oar]

its ok

[weak haven]

[normal plinth]

[calm coral]

would it be possible to edit the keys for focus mode?

rather than the predetermined

[pliant lance]

🌚

[compact dock]

Will the beta version automatically be updated to the new stable branch?

[crisp sundial]

How fast is it now ? 😃

[amber current]

yo i can just go to my wootility and update it and it will work right?

[final yarrow]

No, they are separate branches so you'll need to install the stable or switch to stable wootility web

[amber dagger]

so theres a more stable version than the default versioN?

[final yarrow]

The layout of the focus keys are fixed based on the design of the hardware, so it's not possible to have arbitrary keys focused. Although, there are some possible configurations that weren't included due to being messy, so it's possible there could still be a possible configuration added if you have some specific requirements

[final yarrow]

Yeah :)

[final yarrow]

Not sure what you mean, this is the latest stable build

[calm coral]

got it, thanks

[amber dagger]

Sry i thought "stable" was referring to some extra thing since my wootility wasnt showing an upgrade.. but i got it now

[amber current]

i got the wooting 60he and i cant find the "tachyon focussed mode where is it"

[final yarrow]

The focused mode is only for Two HE and Lekker Edition, 60HE is already 2fast2quick

[amber current]

wait 60he is the fastest?

[final yarrow]

60he is a speed demon

[amber current]

W

[weak haven]

[agile abyss]

W

[slender granite]

Device found Wooting 60he arm then suddenly Device init failed over and over for a week now. anytime I try to use the Wootility software or the web version.

how can I update if this keeps happening?

[rocky atlas]

Uh what?

[slender granite]

error communication with device timed out

[brittle cedar]

still remains for me too

[final yarrow]

One workaround you can do is to do the restore process. That should get you the updated firmware, but it will reset your settings

[final yarrow]

that's an interesting false positive

[rocky atlas]

Yeah I reported it as safe page not sure what to do else then giving an heads up

[slender granite]

Uninstall the wootlity and install new updated one fixed it. I did reinstalls like that last week before the update but didn't do anything. Update must've fixed something with my system

[arctic mason]

Can't I turn on the wasd and arrow direction keys at the same time in focus mode?

[weak haven]

Sadly not possible to get both WASD and all 4 arrow keys
Best alternative that could be done would be WASD area (minus spacebar) and Numpad area

[fervent dock]

@final yarrow It only updated the wootility desktop version for me. Not the firmware.

Previously i was on the beta release. My current firmware is Firmware v2.6.19. Is that ok ?

[arctic mason]

Is there an update scheduled later that uses both wasd and arrow rudder in focus mode?

[rocky atlas]

It might be a hardware limitation

[weak haven]

Actually, it may be possible with some weird looking configuration. I'd need confirmation from Simon as there may still be other limitations preventing that

Would still not include spacebar though

[arctic mason]

Please update it so that users can specify the key they want, if possible

I hope so

[steady gyro]

Hello Simon/Darren,

Is it at all possible to find out which features are being worked on for next version(s)? I submitted 3 enhancements on github a week ago.

Obviously not every github request becomes a feature, and those that do will take some time - I'd just love to know which ones I should start looking for alternative solutions to.

The "Disable active toggles" request is by far the most important, since currently there's not really a workaround

Also I'm pretty handy with code. Is this the type of thing I could just do for myself with the SDK I wonder..? Learning new languages isn't an issue

[final yarrow]

Yeah that's the latest firmware, so you're already on the latest for the stable

[final yarrow]

The Wootility schedule is in a bit of limbo now that I've got most of the things I'd been working on out the door. So the scope for the next release hasn't been strictly defined yet.

I can have a look over your ideas now to see if I can give you a better estimate of when you'd potentially see them

[final yarrow]

The toggles one I don't think you'd be able to get very far with using the SDK

[final yarrow]

The keys that you can focus on are a property of the hardware, they are in groups of 16, so only certain combinations are possible. I'll have a look to see what possible configurations could include both key sets you mentioned

[final yarrow]

You want to have a binding to toggle off all Toggle Key bindings? It should be pretty easy to make, I can add it to the scope for v4.6. (Might be a while before it arrives tho)

[steady gyro]

That would be really great.

Ideally it would also toggle off any fnLock keys currently active

[final yarrow]

Hmmm, that feels like a bit too much behaviour to put in a single binding (as then you'd be unable to only toggle off toggle keys). A better set-up would be to have separate bindings for those behaviours and use dks to activate them together on one key

[steady gyro]

Agreed. More modular is definitely better, just don’t want to ask for too much. Either way the toggle-off binding will be great to have thanks a lot!

[tardy veldt]

Is this update for the 60HE? It seems focused on the other keyboards

[final yarrow]

The update is also for the 60HE, the big change (Tachyon Focus mode) doesn't apply to 60HE. But there are other changes that apply to the 60HE as well

[final yarrow]

Just had a look into it, there aren't any possible configurations that would cover both wasd and arrow keys at the same time sadly :(

[fervent dock]

Please @final yarrow give the possibility to set the DKS actuation point for bottoming out the key at 4mm (instead of the current 3.6mm)

[final yarrow]

You can add to this same request on GitHub if ye want https://github.com/WootingKb/wootility-issues/issues/205

[fervent dock]

Done!

[glossy fern]

Is it possible rollback this update?

I can't hold down a key anymore without constant input from that key. And i've got a lot more double spaces

[weak haven]

@final yarrow

[final yarrow]

Hmmm, there's not an easy way to rollback. I suspect the issue you are having is the same one I've been digging into the past few days. do you have RGB sleep mode disabled? (If so, try enabling it, for some reason that changes the behavior with the issue I'm investigating)

One way you could try rolling back is to direct download v4.5.0 (or older) and do a restore. That should get you on the older firmware

[glossy fern]

I disabled tachyron mode and that worked well enough for now

Appreciate your help

[final yarrow]

@glossy fern Glad you got a workaround going. I'll let you know when I've got a build to fix the issue I've been looking into, hopefully sorts it for you as well

[glossy fern]

Thank you

[final yarrow]

@glossy fern The v2.6.20 firmware fixes the issue in case you haven't seen already

[glossy fern]

I'll make sure to update today. Thank you

[forest burrow]

the 2.6.20 firmware is only for AVR model?

[final yarrow]

It was primarily intended to fix AVR. However, I had to temporarily remove it as it introduced some other issues. I've got a follow-up firmware ready (v2.6.21), but I'm at a family wedding so it'll be a few days before I fully push it out

[forest burrow]

ok i understand and the .21 will be for ARM too?

[final yarrow]

Yes, usually any firmware build is for all models. Although it can depend if there are actual changes on that model. At least in this case, it will apply to ARM as well 🤠

[forest burrow]

ok thanks for explanation.great day to you 😉

[glossy fern]

Like what? I've not noticed any issues.

[final yarrow]

The issues appear to be on the Two HE AVR side, 60HE AVR seems to be solid on 2.6.20

[glossy fern]

Thanks for sharing!

[fervent dock]

Bug Fn1 not respecting Hold Duration Override.

New bug discovered https://github.com/WootingKb/wootility-issues/issues/219

@final yarrow

[final yarrow]

Sounds like you're running into the "Just in time" behaviour, where the hold key activates immediately when another key is pressed. This applies for modifier keys & Fn keys

[fervent dock]

Can you make it so as that behaviour can be activated/deactivated?

Because, if not, i don't see the point on knowing when the FN1 is activated due to the RGB layer of it, since i can still spam the arrow keys before showing the rbg display.

[final yarrow]

I should be able to control that behaviour, potentially I could make it a 3-way option, where you can completely disable it, only modifiers/fn and all the time

prob a nice thing to have

[fervent dock]

Plus, it certainly messes up while writing a document, whenever i press Caps and A sometimes while tapping, it thinks im holding it and it presses the arrow key

[fervent dock]

Also if you see the video, it's like when entering that behaviour also the rgb layer of the FN 1 blinks lol

[fervent dock]

Sure, for instance, for me, i would like to control the hold duration for all the keys and not having it activated on the fly while pressing another key. Hopefully this can be added. Thank you very much

[final yarrow]

It would be helpful if you could open an issue/edit this issue for controlling the just in time behaviour

[fervent dock]

will do

Gonna edit it as a feature/request

Done. Closed the other.

Opened this one:

https://github.com/WootingKb/wootility-issues/issues/220

Thank you @final yarrow

[prime saffron]

My Wootilty app is stuck in this state, but appears to be still saving things as I make changes. Anyone know if it's a known bug?

[final yarrow]

Hmmm, I think I've seen that happen if the device disconnects mid save. If you reload the app it should be fine

[prime saffron]

Yeah, I was worred about losing my changes but I think it was fine. I realised it kept disconnecting so I changed USB ports and seems solid now.

[civic pecan]

I have a question about the Num Lock indicator behavior in MacOS.

In the description it said select the Regular Behavior to hide the indicator in MacOS, but shouldn't it select Inverted to hide the indicator?

[final yarrow]

Because MacOS doesn't have num lock, it will always be considered turned off in the keyboard. So if you have regular behaviour that means no indicator, if you have inverted behaviour it will mean that the indicator will always be on

I realise that that isn't consistent with the text explanation, but that's only applicable to cases where num lock exists

[past flame]

Okay, Wootility 4.5.5 really does NOT work with my Wooting One. First try, it said it wanted to update the firmware, which got stuck at trying to detect it after restart, and never detected it again. After carefully uninstalling everything per the guide for undetected keyboards, I managed to get it to pass that step, but then Wootility got into a loop saying it couldn't set some property, and never loaded settings correctly. Worse, it left the keyboard with an alien mapping, e.g. d on tab and enter on backspace. Luckily, reinstalling wootility 3 and manually using restore mode got it back to working.

[civic pecan]

Yeah, I see. So in MacOS, Regular mode means input the number when the indicator is off.

[final yarrow]

Was this all when you were trying to do the first-time update to Wootility v4? After it updates the firmware it takes a while to turn back on as it has to rewrite the entire configuration memory, did it not come back at all?

[past flame]

first time, it sped through the firmware loading part, then left the keyboard fully operational except wootility couldn't detect it (left wootility sitting at least fifteen minutes at the end of firmware update, waiting for keyboard to reappear). Second time, it returned and was detected nearly instantly, wootility started generating errors and reconnecting, and the keymap was messed up. So with wootility v4 I had either working keyboard with no wootility connection, or messed up keyboard with broken wootility connection. There was never a notable while to rewrite configuration memory.

I suppose one might guess it somehow thought it had a v4 configuration, failed to parse it and never reset it?

[chilly flicker]

I am unable to update to the new firmware (2.6.21) from my current version of 2.6.20. I keep getting an Unknown Error ID.

So on the 4th try it got past where it was stuck (Reset Device to Update Mode) and it installed the firmware but then gave me the same error when the progress bar reached 100%

I clicked done and now its says its all good but i'm not convinced

[final yarrow]

Hmmm, seems like you were hitting some communication issues during the update. If the keyboard works, shows up in Wootility and has the updated version in the bottom left then it should be all good now 👌

[final yarrow]

Yeah, that theory seems pretty plausible. The first time it must've messed it up where it didn't perform the initial configuration stuff the second time. Now that you've went back to v3 it should be in a state where it can do the migration again, although the on-board serial number will be messed up (which is a consequence of returning to v3 after attempting v4 upgrade) but that's not the end of the world

[past flame]

third time went into same loop as second time. did a manual restore, though, and now it's working with 4.5.5, but the wootility is showing the wrong colours on a handful of keys (l-shift, the key between that and z, backslash above r-shift, and enter)

[fervent dock]

@final yarrow is it normal that when i have all my keys with black colour, whenever I put the Caps activated with white colour the led turns red instead of white ? It's a bug. The solution was given to me here: https://discord.com/channels/167181566978555904/1131304226585317426

[plain zodiac]

Is it possible to rebind a key to a specific uppercase key?

[plain zodiac]

An other question I would like to do a rapidfire "macro" (what I mean is maintain a key press and the key down/up is send repeatedly to not have to spam some QTE on games)

?

[final yarrow]

You can theoretically achieve it by binding the base key and Shift into a DKS binding on that key

[final yarrow]

The only pathway that's happening is via wootimation, it won't be something we'll do onboard anytime soon

[plain zodiac]

Can you be more specifi I don't see what I should do.