v4.5.4-beta

[pure flower]

v4.5.4-beta

[ebon herald]

W

[polar stirrup]

Nice

[viral brook]

Nice

[nova jackal]

yoooo

[eager pecan]

Give me the BETAS

[soft stirrup]

is there going to be a way to set tachyon focus mode for specific keys instead of it being split into 3 sections or is this what to expect for the stable release

[drifting thorn]

though you are met with this when installing the beta

works fine tho, i believe

[manic ibex]

Since im on a 60 HE i guess the numlock indicator doesn't apply to me, right ? @pure flower

Neither the Tachyon Focused mode

I activated Tachyon on new beta update and i didn't get the prompt of the focus

[shy marlin]

tachyon focus mode is really unstable its lets my wooting two he crash every 2 min,

[pure flower]

do you have an original 2HE or a 2HE ARM?

[pure flower]

Yes, Num lock indicator is only relevant for when you have num lock bound (i.e. Two HE) and Tachyon Focus mode is only applicable to full size boards as well

[pure flower]

Hmmm, that's strange, never seen it pop up like that before

[pure flower]

The set of keys you can focus on is a property of the hardware design, so in general the groups are going to stay like that. There are some group combinations that exist that are not present there, but they were ones that didn't seem particularly useful compared to the ones we selected

[shy marlin]

I have the original

[pure flower]

Ah, so you're probably running into the same issue that was appearing on the Lekker Edition that I added a warning about. I'm still trying to get to the bottom of that crash, any updates I have on it I'll share here

[eager pecan]

installing rn

[silk nimbus]

Is the 4MS scan rate for the other sections of the keyboard on focus mode a hard limit? Or is it just an estimation of the average speed, because I've enabled focus mode, and hit a bunch of keys on the right side of my keyboard, and I was able to get estimations of scan rate below 4ms on this website: https://blog.seethis.link/scan-rate-estimator/

focus mode does seem to be working, since it's faster on the left side of the keyboard

[drifting thorn]

on a fresh install of windows 22h2 with nothing installed or settings being altered, is strange...

but installs and works fine when i hit cancel

no noticeable crashes and what not

[trail field]

Guys if i were to download the new beta version of wootility do i delete the old one?

[pure flower]

Yeah, it's very much an estimate. To give you some background, the way it works is that every scanning cycle (the cycle which aims to be within the 1ms window) it will scan all the focused keys. Then the remaining keys it will swap in and out each cycle, which results in the non-focused keys being scanned every 4 cycles (hence the ~4ms estimation). So the ~4ms estimation is very conservative, as each cycle takes about ~0.7ms baseline (it can vary a bit, so I try and bring down the baseline as much as I can to ensure it will hit the 1ms target). So in practice the latency for the non-focused keys will be a bit better than that estimation, best case scenario those keys will be scanned every ~3ms, so depending on how your press/release aligns with the scanning/polling cycles it can be better overall latency

[silk nimbus]

Right, that makes sense, thanks for the explanation

[pure flower]

You don't necessarily need to delete the old one, once this beta makes it to stable you should be able to just switch back to using the stable build

[silk nimbus]

Any chance for more focus mode options? In fighting games for instance it's common to put movement on wasd or asd + spacebar, but then put the actual action buttons on numpad or somewhere else on the right side of the keyboard.

[cunning merlin]

hey, sorry if this is the wrong place to ask; but by downloading this version for windows, am I supposed to disregard/uninstall the older version of wootility that I previously installed?(last update i believe is 3/22, I downloaded on 4/8, this current beta is just recently downloaded 4/28) I'm under the impression that I was supposed to use the beta software and update the firmware on my keyboard, but do I need to keep using the beta version for new features?

[spice stream]

I very much appreciate you having implemented the eagerly awaited inverted num-lock feature! keep up the good work! 😍

where is this actually located? as to my understanding it should be a firmware thing entirely, isn't it?

[pure flower]

There are other options that can be added, but the grouping sometimes isn't ideal. I'll have a look to see if there's a group that captures all of the keys you mentioned

[pure flower]

While this release is in beta and you're using the updated firmware you should use the Beta build. Stable will probably work, but may clear some of the new settings when saving. When this beta makes it to stable you can go back to using the stable version

[pure flower]

It's available in Settings -> Keyboard settings, it's a global setting rather than a per profile one :)

[spice stream]

I know already. My question was as to where the code needs to be; I now assume it has to be both: firmware and software. The latter for being able to pass this setting over to the keyboard firmware. When is it actually saved when it is not in the profile? immediately?

[pure flower]

Oh okay, I see. The setting gets set immediately on change, but then auto saved after 5 seconds or whenever the window is closed. It has a bit of a buffer to not spam save (so flash rewriting) when toggling it back and forth

The RGB sleep setting does the same logic, it's technically part of the same 'GlobalSettings' object that the num lock inverted setting was added to

[cunning merlin]

thanks so much for clearing this up for me, couldn't find out anywhere on the faq site and didn't want to make a whole support post

[simple bronze]

For some unexplainable reason my W two HE seems to not work when i cold boot or restart my pc until i replug the keyboard with the newest firmware + beta 4.5.4.
But aside from this, everything works like a charm.

Also a question to focus mode, how far can the latency brought up for non-focus keys?

Was there a reason that it was set to aprox. 4ms or can it be set even higher like 10ms if the focused keys gain a benefit from it?

[pure flower]

I think what you're seeing is related to the focus mode crash that I've been fixing. I've got some changes I'm aiming to push today which should hopefully sort it.

Re: Focus mode latency, I gave a bit more of a detailed explanation on how it works further up in the thread.
Re: bringing up non-focus keys, there wouldn't really be a benefit to scanning the non-focused keys slower. Theoretically, there are scanning architectures you could do which would have slower non-focused keys and possibly slightly better focused, but I'd expect the improvement to be minimal compared to the significant loss you'd have on the non-focused keys

[pure flower]

@simple bronze @shy marlin I just pushed firmware v2.6.18 which I hope should fix the crashes yous were facing :)

[shy marlin]

Nice, i gonna give you Feedback if it works or still makes some issues, when i try it later

[simple bronze]

eyy excellent, thanks for the answers, and I'm thrilled to try the fix out today. thanks for the hard work

[shy marlin]

yeah seems like you fixed the crashes, no crash after a few hours

[simple bronze]

After the reboot my W two HE was working as intended

So I think its fixed now, thanks a ton <3

[pure flower]

Awesome, thanks for the feedback :)

If you're able to confirm that it's still working fine with v2.6.19 then that'd be great, as I noticed that the fix I did introduced a bug with flaretech boards & 60HE. Should still be good, but always helpful to double check 😁 @simple bronze @shy marlin

[simple bronze]

hmhm, gonna check if it still works

[shy marlin]

Yes i gonna check too if Still works

[last dagger]

Feature request: "Override hold duration" option for toggle keys (currently only available for mod-tap)

[manic ibex]

So if im on 60He should i update ?

[pure flower]

Yeah, you should update to the latest

[pure flower]

Good idea, any chance you could post it on here https://github.com/WootingKb/wootility-issues/issues ?

[pure flower]

btw, I'm pushing a fresh Wootility beta build. Nothing major changed, primarily just translation fixes

[last dagger]

done - along with another toggle-key related feature request. Thanks!

[trail field]

just where do i get the link to download the beta version

i clicked on the link in #📰│wootility_updates i doesnt show any buttons for download

[boreal rain]

Title post for the thread has the links

#📰│wootility_updates message

[spice stream]

no download link for now

[boreal rain]

So it seems.. I'll mention it to Simon tomorrow

[pure flower]

Oh whoops, the page got messed up when I copied it to start working on the changelog for stable push. Should be good now @trail field @spice stream

[pure flower]

@simple bronze @shy marlin still all good on your end with the latest firmware?

[spice stream]

this is the old one. I thought you pushed 4.5.5-beta?

[pure flower]

Oh, links are still old, but Wootility should update itself to the latest

can also edit the url if you need direct link

[spice stream]

I see

we cannot - it's a secret hash 😉

would have liked to review the change log beforehand

[pure flower]

not the changelog url, but the download urls. You can change the wootility version in the url if you need direct download

there isn't much of a changelog, because all it is, is what I already said in this thread: it was just some fixes to facilitate translations, as there were some areas that were missing localisation support. So not really going to see anything different as a User unless you have a different language setting that already has the new parts translated.

[simple bronze]

I got the new version yesterday, and I'll see if the keyboard goes bye bye when I start my PC

[simple bronze]

new firmware works fine, thanks for the hard work!

[pure flower]

Great, thanks for the confirmation ☺️

[sand finch]

I've been using the new beta since it came out, and I've noticed a weird problem ever since: once I boot up my pc, sometimes it just freezes before it loads the login screen and the screen just stays black. the keyboard blinks a few times before that and then the lights just shut down. hard rebooting once or sometimes twice helps

[pure flower]

That's bizarre, I can't imagine how the keyboard could cause that kind of behaviour on your PC. Does it happen when you don't have the keyboard plugged in?

[earnest pagoda]

on the beta wootility i see you put a soft limit on rgb when tachyon enabled.can we still put the rgb at 100 percent or it's locked at 70?

[pure flower]

It's not hard locked, you can unlock it to increase it if you're confident your cable/hub/etc can handle it

The main intention of it is to make sure people don't have their keyboard freaking out from bad power as soon as tachyon mode is enabled

[earnest pagoda]

ok i understand thanks for explanation.last thing have you progress or info about the tachyon mode actuation point not accurate we speak in my support post ?

[pure flower]

I'm still actively working on the Tachyon mode actuation point stuff, I've already got some improvements ready for the analog signal e.g. higher precision and lower noise, which was my foundation for dealing with this issue. I hope to be able to get the actuation stuff improved soon :)

[earnest pagoda]

ok perfect im happy to ear this.but the problem happen only when tachyon on.we don't use analog stuff but maybe i don't really understand how work the tachyon ecetera.you will update my support post like we discuss some month ago when this will be ready to fix right?

[pure flower]

Yeah, I'll update the support post when I've got something for people to try out :)

[earnest pagoda]

ok perfect thanks for your job have a nice day