Wootility v4.6.12-beta Feedback

[thick flare]

[wispy ether]

uau

[thick flare]

Wootility v4.6.12-beta Feedback

[proper salmon]

wooting shit

[queen jackal]

nice
time to play around w it

[pure token]

> improvements to Analog Signal Processing

i pogged

[gray hornet]

Same, been waiting to finally get off of the 2.7.1 test,signal build

One step closer to finally going to the stable build, then I can stop seeing the Update New icon

[scenic parrot]

w

[celest pelican]

yooooo, finally

[zenith island]

Is it web based only or can i download it?

[hollow fog]

so i started to update my keyboard and my computer had a stroke

[ancient oasis]

*There is no better time to release an update than on Friday night right before Christmas. 🤣 *

Looks like the releases are published later and later the day. I hope you aren't doing overtime.

[hollow fog]

it spams what im assuming is the entire f row and holds alt, shift, ctrl and caps down

if i plug it in it continues to do that

what do lol

[thick flare]

You'll need to do a restore

What is your first profile configured to?

[zenith island]

is it only web based? i dont see a download link for the beta version?

[thick flare]

You can see the context in the notion, but only Linux build is available at the moment. We are having some difficulties with our signing keys

[zenith island]

ah ok. ty

[hollow fog]

The typing profile

[thick flare]

I mean, what settings do you have on it. Like tachyon mode, brightness, actuation, rapid trigger

[hollow fog]

Oh, rapid trigger, full brightness, .2? Actuation I think

[thick flare]

Do you have tachyon on?

[hollow fog]

No

[thick flare]

Also, for restoring, refer to Settings -> Troubleshoot. Do it on the stable build if you want to go back to that

[civic condor]

well, after the beta update it feels like when i press my shift key it holds it

[hollow fog]

I'd love to but it spams buttons and opens a bunch of programs and tabs

[thick flare]

If you go to the Troubleshoot section it'll make sense. You need to put it into the restore mode which means it won't be able to input keys

[thick flare]

Keyboard model? Does it still happen after leaving your keyboard untouched for a few minutes?

[civic condor]

60he

ah man

resetting device made my profiles go away RIP

[hollow fog]

rip my profiles too

[next bane]

That's why I always keep backups of my profiles in Google Keep.

[civic condor]

luckily i mainly use the FPS rapid profile and i sent that to a friend when he got his woot so i got saved

[next bane]

https://tenor.com/view/spongebob-squarepants-nickelodeon-sigh-phew-gif-5752975

[pure cliff]

I am not able to download the beta for windows

[orchid crystal]

erm

technical difficulties

[brittle spruce]

same thing happened to me

whole cumputer had a stroke tried to open everything

[pure cliff]

[brittle spruce]

Something is def borked

[hollow fog]

save your profiles before you restore

still setting up my shit from 30 minutes ago

[brittle spruce]

did u manage to install it without PC crapping itself?

[hollow fog]

nope

just using the non beta

not even gonna try again

[brittle spruce]

Oke same, tried 2 times. Didn't work with setting tachyon off and rapid trigger off

[thick flare]

@Dag @hollow fog what keyboard model do you have?

[brittle spruce]

@thick flare 60HE ARM ISO

[thick flare]

It freaked out immediately? Do you know if you have first batch or later?

[brittle spruce]

I have one of first shipped ARM's, so prob 1st batch. And yeah freaked out immediately. Started spam opening my whole office suite

[hollow fog]

arm 60he

i think 2nd arm batch

[thick flare]

Okay, I have a feeling I know what happens to you then. I have one I can check with

[brittle spruce]

That'd be great, cheers

I didn't have this issue before, btw. On the alpha firmware

[thick flare]

I can't check tonight and I'm busy the next few days (as you can imagine), so won't be able to check it yet

[brittle spruce]

Yeah thats fine Im away for christmas anyway. 🙂 Have a good christmas and new year

[thick flare]

Thanks, and to you too!

[opaque crest]

After updating to the beta version all of my keys on the far right seem to use a very deep actuation point (about 2-3mm) and no settings change it the [ button is fine, but ] and further all have this problem. Switching profiles also seems to lag the keyboard for moment - rgb effect pauses and after a visible delay it's switched to the effect from the second profile. I'm using Wooting Two HE ARM

And updating the actuation point doesn't work most of the time

[thick flare]

You should leave your keyboard to be idle for a while for it to do deep calibration. It happens automatically now while the keyboard is idle. Once it's done, just switch profile and it should remember the calibration

[molten musk]

Are there any improvements to avr boards?

[meager brook]

I have an issue with the test build occurring lately, sometimes I cant enter my pin when I want to sign into my pc. I'd have to unplug and replug the keyboard or use the on-screen keyboard from the accessibility menu if replugging the keyboard doesn't work.
and I also notice lately i get more frequent ghost inputs

[thick flare]

When you refer to the test build are you talking about test.signal.0 or 2.7.3-beta.0

[thick flare]

Not yet, with the limited memory of the AVR boards, we decided to focus on the ARM side to develop our techniques and processing strategies. Once we have it in a solid place, we can see what improvements we're able to bring over and fit into the memory of AVR

A note about calibration
The firmware will continuously learn while it is powered on and it is idle. In this build, it will save the profiles' learned parameters when you switch profiles. So when you have learned once on a profile and it has saved, it will load it immediately every time that profile is loaded. But it will still do it continuously when it's idle to ensure that it has the most accurate calibration for all keys.

However, if you change tachyon mode on the profile, it will reset it and have to learn from scratch again. (Which is a fairly normal thing to do, so I need to make that quicker to respond and not fully reset)

So for best results, you should not change tachyon mode repeatedly, as you will just keep resetting the calibration. You should keep your profile configuration and let it learn, then switch profiles to ensure it saves it for next time

[meager brook]

Yes, the strange thing is it also occurred on v2.7.1.

After installation of the firmware it's working fine, but after a few restarts it will occur.

[opaque crest]

I've tried leaving it idle for > 1 hour with my pc turned on, but it didn't help. Keys on the right side of the keyboard seem to have a minimum actuation point because setting 4mm actuation point works, but low actuations (0.1mm, 0.2mm) activate at about 2mm

And switching modes still lags the keyboard, which was instant before the beta update

[thick flare]

Hmmm, there must be some key in the middle of the keyboard which is blocking the learning for some reason. I'll need to get some more diagnostic stuff set-up to be able to get some more insight into your board in particular

[opaque crest]

ok

[thick flare]

@meager brook Do you have any issues with inputting the pin when you're in your OS?

[opaque crest]

I've just tried v2.7.1-test.signal.0 and both issues seem to be fixed

[pure token]

2.7.3-beta.0 has been feeling a bit weird - even had one instance where fully bottomed out shift would count as "not a press". Using 60he ARM, yellow switches, 0.1 act, 0.15 rapid trigger both ways, tachyon off

Anyways, gonna revert to stable for now

[nimble glade]

you have same problem with tachyon on?

[thick flare]

@brittle spruce @hollow fog I found a lil moment of time to have a look at your issue, I was able to confirm the issue on my early batch 60HE ARM. I have pushed out v2.7.3-beta.1 with a fix for it, no other changes for anyone else yet

[pure token]

i think tachyon felt even more inconsistent so i turned that off after a few min

[nimble glade]

ok i need more in depth testing about 2.7.3 to see if it's better than 2.7.1 signal test firmware

[thick flare]

The main thing that has changed with 2.7.3 which I think is resulting in some of the issues that have appeared, is that we completely scrapped the boot time calibration in favour of our new deep progressive calibration process that runs when the keyboard is idle. This means that when there is no calibration, it's put into a "safe" setting, which will be observed as a deep actuation, until it has learned that key. The calibration with this build needs to be done for every profile and will get reset if the Tachyon setting changes. The calibration will be saved for a profile when you switch away.

I need to have a think on the best hybird approach, to get the calibration 90-95% of the way there immediately and let it reach the 100% calibration through the longer-running learning process

(Aside, the keyboard will learn the keys from roughly left to right, which explains why keys on the right of the keyboard has deeper actuation for a longer period and may get stuck like that if the learning process gets stuck and hasn't reached them)

Okay, I'm going to head off for Christmas for real this time. I hope the build is able to work well, but remember, it's still in development, so it's not going to be perfect

[nimble glade]

merry christmas 😉

[hollow fog]

Merry Christmas, thanks for the quick fix!

[sleek lark]

You guys are absolutely amazing, delivered my 60he 20 days earlier than expected

[abstract peak]

im stuck in 4 6 6 cant updtate

2 7 2

any linj to DL new one

[meager brook]

I'm on windows 11 and everything is updated, I can still input my pin using the on-screen keyboard if my Wooting 60HE doesn't work. Mine is an ARM. When it doesn't work, no matter what keys I spam, it won't work, even if I have a spare keyboard attached, that keyboard won't work if the pc was booted up with the wooting plugged in beforehand. I'd have to unplug my wooting and replug it in order to input my pin using the number keys. After signing in everything works perfectly. Just that during the sign-in screen everything is buggy. The caps-lock button would turn on and off if I were to press any key, but still no text or numbers would appear on the text box.

[meager brook]

I see, thanks for the info! Merry Christmas!

[lost fjord]

I will come back with information after I raid, but with the beta firmware I am having problems with .1 mm actuation point. I have it on my shift key and it will now randomly actuation without my finger being anywhere near it. I noticed this while playing some granblue earlier. I would randomly dodge while back stepping. Went into training mode and every few moments of backstepping I would evade which means a shift actuation in my keybind setup. I had rapid trigger and tachyon enabled, can do more testing later.

Even while typing this out I was having some issues with the shift key, though a system reset seems to have fixed that. I'll monitor it through the night. (and thats with 2mm actuation and no rapid but tachyon enabled)

[vale wharf]

Shift key seems to be pressing randomly when I press other keys (rapid trigger on 0.15, global actuation point 0.1mm, tachyon mode on). The problem seems to be gone when actuation point is set to 0.2mm or higher (with Tachyon on). Had to revert to stable.

Not sure if upping the actuation point actually fixes the issue though, only tested for about a minute or two before reverting.

[celest pelican]

its literaly my problem lol, but idk, i feel more responsive the key, like, real 0.01mm of actuation key, idk is a simply my mind or real, but yeah the shift press randomly sometimes

[nimble glade]

can you tell me a scenario when this happen typicaly?

[celest pelican]

when i play mc

i shifted without intention

[alpine current]

what would be considered an early 60HE arm keyboard?

[zenith island]

my firmware updated fine on the webbased version to 2.7.3-beta1

[night meteor]

Hey how do I go back to the non-beta firmware? I can't find the option in wootility. I am getting random characters being injected when I type now and then. (oh maybe it's too much brightness on this USB hub hmmm....)

Ok I will try it on this powered USB hub first...

But would like to know how to go back to the non-beta firmware just in case. I couldn't find any instructions.

[nimble glade]

If i remember you can use restore mode and you will be back at the last non beta firmware the 2.7.2.but you will loose your profile if you dont save them somewhere

[normal estuary]

Updated fine here using beta web based application

But uhh i dont see/feel any differences in analog behavior

NOTE: Changing Tachyon mode will reset your calibration, so at this time, your actuation will be deep until it is able to learn it again. This will be improved in a future build. In general, your keyboard will take a bit of time to learn the exact properties of your keyboard’s signals, so it is best to give it some time to do that, after switching profiles, it will remember the calibration for the next time the profile is loaded

Can you please elaborate on any of this? I cannot find any documentation about any of the changes or how the processing is supposed to be improved (As I currently am reflecting no change in my personal experience).

How and where is my keyboard learning the exact details and properties of my keyboard, lol?

[nimble glade]

@normal estuary With the old firmware you need to wait 5 to 15 + or - sec (without key press)for the keyboard when you plug in or power on your computer to calibrate the actuation point ecetera.if you change tachyon mode on to off or off to on the calibration is already done.if you press key in this 5-15 second laps time your calibration can be poorly made and you can have some random key press and some other problem and you need to restart the calibration.with this new firmware if you change tachyon mode from on to off for exemple you need like 15 seconds(with no key press) for the calibration to be done entirely in this laps time your actuation point is not accurate for exemple 0.1 mm actuation is more like 2mm.but if you dont touch your keyboard or idle your actuation point will be accurate after some seconds.you dont need to unplug him for re-calibration he learn progressively the signal for every key . It's just a different way to calibrate keyboard . from my understanding .and this maybe give some improvements.feel free to complete my explanation or correct me.

[normal estuary]

Ohhhh wow I didnt know any of that

Ive probably ruined my calibration so bad so many times

Without realizing it

Would be good to get the details on this timeframe specifically as I and the people i know didnt even realize this was even a thing

I plug and unplug my Wooting all the time and immediately start pressing my buttons to swap profiles

[brittle spruce]

Worked! no more issues. Thanks!

[covert acorn]

not sure if answered yet, but is there any changes on initial startup of the keyboard?

not sure if bug or feature, but upon turning my pc on or just (unplugging and) plugging in my keyboard, it seems that my fn key is locked on and i can't do anything unless i select a profile

^this is also happening after performing a restore, and not sure if it's due to my profile only(im about to do a test right now with a new profile

[next bane]

[obtuse cloak]

When will the signing keys be fixed for windows and Mac versions?

[mellow totem]

Edge hates this beta version for some reason, constantly disconnects and reconnects the keyboard throwing error 255

wack

Works fine in any other browser. Edge version: 121.0.2277.4

[nimble glade]

feedback : fn toggle work now but the rgb on the toggle fn key is white and not in the color i set (the little circle like the caps lock key)

[thick flare]

Windows desktop build is live now, going to sort out the Mac build now

I've also got some follow-up changes I'm going to be working on for the firmware to tackle some of the issues that people have been facing

[thick flare]

I've had a similar problem on my board and got a fix lined up already

[rich inlet]

Hi i have two questions before testing this Beta:

1. Is the new calibration system slower?

2)Isn't it a drawback to have it recalibrate when in Tachyon mode?

@thick flare if you could please, futher explain these topics i will be glad

[nimble glade]

in the future will we be able to set all actuation points to dks points as the total pressure of 3.6 is sometimes too high to register?

[nimble glade]

double click on my keys and in majority on the space key since the update of 2.7.3 firmware i roll back to 2.7.1 signal test buildsame problem and after to 2.6.21 and the problem disapear.it's seem related to rapid trigger functionality

[nimble glade]

2.7.2 build work too

[thick flare]

@everyone I've just pushed out a new beta firmware. v2.7.3-beta.2.
This new build aims to get the best of both worlds from the previous test build and the last beta.
The start-up calibration flow has returned in a more advanced form, getting you that ~95% calibration immediately and your keyboard will automatically calibrate towards 100% while it’s idle.

This should tackle some of the major user experience issues and some of the bugs from the previous beta, but there are still more fixes and tweaks to come

Please let me know how you get on using this version

@rich inlet the new build kinda changes your questions, so let me know if you have new questions based on this latest build

[vale wharf]

Is this bug fixed?

[thick flare]

I suspect that your issue is caused by the calibration being too sensitive, I haven't made any adjustments in this build to how it interprets the results of the deep* calibration when your board is idle. So it may still be calibrating too tight for you

Although, this version is a lot safer, as it won't remember the calibration across power cycles, so it's a lot easier to reset the calibration if it ends up bad

[orchid crystal]

ty ily

[thick flare]

Currently the expectations for deep calibration timings should be:

• It will start learning key by key 5 seconds after the last key press (this is pretty fast and will be increased later)
• It will take a minute or two to complete a single learning pass on every key
• When switching profiles, it will remember what the calibration that had been learned for that profile (only for this time it's powered on)

So if you are getting any issues, it would be helpful to know if it happens immediately when the keyboard powers on (before it has done deep calibration) or later on (after doing deep calibration)

Also, all desktop builds should be available now :)

[orchid crystal]

ive never really had issues with any of them ngl

wdym by (only for this time it's powered on)

[next bane]

So it does a brief calibration at initial power on and then a longer, thorough calibration whenever the keyboard is idle for ≥60 seconds?

[orchid crystal]

do i have to leave my pc on overnight

for it to not reset

[nimble glade]

did this fix the double click issue i encounter ?#1187862357720977530 message

more detailled herehttps://discord.com/channels/167181566978555904/1192553429604761651

[next bane]

@thick flare, are you able to please help me zoom back out on the newest desktop beta build? I zoomed out initially by pressing ctrl + - but I can't zoom back in with the equivalent ctrl + + key combo

[thick flare]

You'll just have to try and see

[thick flare]

Hmmmm, I think Ctrl+0 should reset the zoom? Otherwise you can try to wipe the app settings through it's files (if you open the log location, delete the folder above it)

[next bane]

ctrl + 0 didn't work, suck

[next bane]

So %APPDATA%\wootility-lekker-beta?

[thick flare]

Yeah, should be it

[nimble glade]

ok i will do that can you give me a link to rollback easily to a 2.7.2 build cause for the moment it's the only build i have no double click issue please.

[thick flare]

Easiest way atm would be to use the 2.7.2-test.usb-boot.0 test build. Then you dont need to do a restore

[next bane]

@thick flare, you won't believe this... I opened this file:

%APPDATA%\wootility-lekker-beta\Preferences

And found that it contained this:

{"partition":{"per_host_zoom_levels":{"5285986755082284524":{"file:///C:/Users/Main/AppData/Local/Programs/wootility-lekker-beta/resources/app.asar/dist/index.html":-5.5}}},"spellcheck":{"dictionaries":["en-US"],"dictionary":""}}

So I closed Wootility Beta, changed the -5.5 to 0.0, saved the file, relaunched the application, and it worked perfectly!

[nimble glade]

(2.7.2-test.usb-boot.0 test build)it's exactly the same at the last 2.7.2 stable build?

[thick flare]

Pretty much yeah, it has some other patches on top of 2.7.2 which are unrelated to analog signal

[orchid crystal]

well now im curious'

tell

[nimble glade]

ok thanks i will try your new firmware and wait 1MN before do the test then the calibration will be done properly to be sure and feedback here if it's fix the doubelick issue cause actually i loose all the improvement you make on actuation accuracy following my support post. but double click is unplayable

[next bane]

So it does a brief calibration at initial power on and then a longer, thorough calibration whenever the keyboard is idle for ≥60 seconds?

[rustic wave]

as far as i understood, at startup it does the normal calibration that it always did on every firmware, but only after idle now it does the new calibration to get it more precise

[nimble glade]

in my case ,double key on space bar is worst then ever with the 2.7.3 beta 2 for me particulary on spacebar key and it's related to rapid trigger

[thick flare]

Yes pretty much, but the startup calibration is a bit improved compared to the existing one

[thick flare]

Do you have tachyon on or off? What is your actuation and rapid trigger settings. Does it happen straight away before deep calibration or both

[rustic wave]

awesome 🥰 big thank you btw for all these mega mind ideas for improving this! calling it mega mind i guess, since i doubt any other keeb has stuff this complicated

[nimble glade]

i already open a support about this with all details i link you in my previous message look like you didn't see but i can repeat here

1.tachyon on or off no difference
2.brightness to zero no difference
3.different usb cable and usb port no difference
4.different computer no difference
5.try all actuation points no difference
6.firmware and wootility up to date (beta build) i roll back to 2.7.1 test signal build no difference
7.replacement switch no difference
8.all rapid trigger range tested no difference but double click reduced a little at 2.35mm rapid trigger 9. happen straight away before deep calibration and after deep calibration (no difference) double click reduced a little but still a lot here when rapid trigger is off on 2.7.3 build. Only old build like2.7.2 or older stop double click issue no matter the settings

https://discord.com/channels/167181566978555904/1192553429604761651

it's not related to calibration cause that's happen on 2.7.1 signal test build too before you add the new calibration system .but after testing more i think it's more related with upstroke.high or low downstroke same doubleclick issue

[rich inlet]

Guess now i will have to test it.

Good call on being hybrid calibration.

2 questions:
1)Does it still recalibrates when switching to Tachyon mode?
2) What if i deactivates the RGB Sleep Mode in Keyboard Settings on Wootility.
Will that affect the keyboard to not be in an IDLE state hence, not learning the 5% calibration?

@thick flare

[proud ibex]

There is some issue with Tachyon mode in MW3 where when you type in game and it just crashes. I switched off Tachyon and so far I've not had any crashes it's weird I've been having this peculiar issue with mw3 and typing in lobbies where it will just crash the game for the last few firmware builds.

Oddly during gameplay it's fine.

[nimble glade]

on this website when i press space bar with 2.7.2 firmware my key press is register only when i release the key(normal thing).when i do the same with 2.7.1 signal test build or 2.7.3 beta 0 or 2 sometimes the space bar key press register when i press the key (1 count) AND when i release the key(2count) it's the double click problem im speaking .so it's obvious something change with the rapid trigger system or become too sensitive with the last build .it's look like my upstroke rt is counted as downstroke rt so that make the double click https://skill-test.net/spacebar-counter

[thick flare]

I highly doubt that tachyon mode is the reason your game is crashing. The only thing Tachyon mode changes is the way and rate that the keyboard scans the keys on your keyboard. The only real way I could imagine it could possibly cause your game to crash would be if you're pressing your keys really quickly and the game can't handle key presses with a really short duration

[proud ibex]

Thanks for the reply Simon. Yes I type fast in lobby and that's when it usually crashes.

In game, I have no issues when gaming with the keyboard it's so weird. But switching off Tachyon eliminates this for me. It's only for MW3.

[thick flare]

1. When you switch tachyon mode on or off, it will revert to the calibration it made at start-up and then when it becomes idle again, it will do a deep calibration pass.
2. RGB Sleep mode has no direct connection to the deep calibration process, they track the keyboard being idle independently.
   Although, I do need to do something with regards to RGB Sleep mode, as if you have a profile that has high noise (i.e. Tachyon mode + really high RGB brightness) then having it learn when the RGB is sleeping isn't going to be very helpful as the noise will be different

[thick flare]

Very strange, I'm surprised the game isn't able to handle rapid inputs when typing. If you wanted to confirm it even more, then you could potentially configure a key with DKS and set one input to be a single dot (so it will input once). Then if you do the advanced setting and change the Tick rate option to no tick, then the DKS binding will always input the key only for a couple of miliseconds. If it is the case that fast input is causing it to crash, then that should theoretically cause it to crash everytime

[proud ibex]

It's fine Simon I thought the board or something was faulty but other games have absolutely no issues. So I'll just leave it for now. Thanks for your assistance anyway.

[gray hornet]

Had somebody report this over in #💬│general seems to be a problem with the software itself they had no issues with web based Wootility

[thick flare]

Looks like their system configuration is resulting in it not being able to update, in general, can manually install the newest version

[nocturne skiff]

Anyone know how I can back to the 2.7.2 pls ?

Because 2.7.3 feel weird 😦

[nimble glade]

yes my way to roll back is this one

1.go here #1075339050011074620 message

2.when you are at step 5 select old firmware build like 2.6.21

3.after you instal the frmware from the same menu you will see update your firmware to 2.7.2

@nocturne skiffit's ok for you?

[nocturne skiff]

Sound good thank you so much I will try and let you know, btw the 2.7.2 was so good and I love it idk why I updated it to 2.7.3

[nimble glade]

2.7.3 improve the accuracy of the actuation point when tachyon is enable but it can introduce some problem or weird feeling depend on case i imagine.in my case i have double click issue with 2.7.3 you can follow the progress about that on my support thread herehttps://discord.com/channels/167181566978555904/1075339050011074620

[nimble glade]

np if that can help 😉

[nocturne skiff]

I play with analog and and I forgot wish version is lol

The beta was perfect for analog that why I’m here asking for it

[nocturne skiff]

I don’t remember wish beta is so I will use all

But I think is the v2.7.3-beta.0 was perfect for me

I don’t have options to get to 😦

[vale wharf]

@thick flare v2.7.3-beta.2 fixed the bug that was causing shift to actuate randomly while I pressed other keys. last night I had another issue: spacebar would not actuate when pressed at random times (it simply didn't do anything when pressed about 20% of the time). at first, I thought it was a problem with my keyboard specifically (related to key chatter), but I don't think hall effect keyboards chatter at all, so I decided to rollback to v.2.7.2, and didn't have any problems since then.

maybe it's also related to calibration, since I was using v2.7.3-beta.2 for about a week, and only had this issue last night. i'll stick to v.2.7.2 for now.

[ancient oasis]

There is an input issue on the beta with Fn1 when Tachyon is enabled.
For example, when the left Win key is pressed and hold and when Fn1 is pressed and release the keyboard will send a key up and down event for the left Win key breaking the hold and causing multiple inputs. If a second Fn1 key is bound (for example on caps lock) that works as expected. Downgrading to the stable firmware fixes it.
#1194918755021623448 message

[nimble glade]

in my case with 2.7.3 i have double or triple click issue on my space bar whgen i rollback to 2.7.2 problem fixed.you can follow problem related here Simon post something about it#1075339050011074620 message

[tired rock]

hi all, I just update the beta fw and I have question about the improve performance about tachyon mode. Will it affect the digital profile or just affect analog profile? Thanks!

[ember kettle]

all profiles.

[tired rock]

Thanks!

So far it works smooth, more sensitive. Later I will try osu! to test.

[thick flare]

I have a feeling I know what happened to you and it should hopefully be covered by further improvements I'm going to be working on

At the moment, calibration will never completely stop.

• If you press a key when the 5 second key idle calibration timer happens, it will cancel the calibration and reset the timer
• If your keyboard is left idle for a few minutes, then you can expect that it should have finished one complete deep calibration cycle for the profile you are using. It will retain that until the next power cycle, but it will currently continue to deep calibrate next time it becomes idle.
• Calibration covers the resting position of the switch and the noise of the analog signal. The calibration of the end of press happens more passively and doesn't get changed by the calibration process

@nocturne skiff What issue were you having with the beta firmware?

[tired rock]

beta 2 for me I got shift click itself. And a few double clicks.

I have rollbacked to 2.7.2 stable. Wait for the next stable update I think.

[fleet portal]

@thick flare seems quite uncommon to me to do some kind of "continuous calibration". if you press a key while the keyboard "boots", the calibration will be f**, that's for sure, but why calibrate after a successfull startup? there shouldn't be any "drift" while the kbd is idle, should it?

[thick flare]

Yeah, right now, the process is very overkill, it's not necessary for it to run so continuously.
There are a few different factors that can impact the signal that we get, but the vast majority of them are not very common in regular usage. The only one that could be common, which I need to do some digging into, are the resting position of keys changing. So far I've observed it on a spacebar key I was testing with earlier, I suspect it could be something to do with the stabiliser, but I gotta dig into it a bit more.
Although, an important thing to note, is that the "continuous calibration" is very cheap and has minimal impact on the keyboard, so it's not really much of an issue to keep doing it

Overall, the processes we have in this beta firmware are not final and I'm trying to continuously refine it to get the best balance

[thick flare]

My concern is that calibration might run when you are applying just a slight amount of pressure to a key and change the registered resting position more than intended.
In general, the idea is that the calibration should never be running when you're actively using the board (which still needs some tuning as it activates very quickly currently). The process works on one key at a time and has a mechanism for determining if a key has moved during the calibration and to then cancel the calibration and reset the timer if so.

Sometimes mid-play some keys have stopped working for me for a period of time. I don't press the keys all the way down so I don't know if it was in failsafe mode, but it lasted several seconds. I didn't know if this was due to calibration or something else.
This bit, I have a feeling is similar to the issue mouse had above which I think is separate from the calibration. But I'll let you know when I have put in my improvements for this aspect, then you can see if you still experience it then

[next bane]

@thick flare, in response to this question of yours from the other day #1075339050011074620 message:

So it would be very helpful if people are able to tell me that they are using the latest beta v2.7.3-beta.2 and if it is all working fine or if they are experiencing some issues
I've been using that build since the day after you released it. I still occasionally experience double-presses on some keys, most frequently on spacebar, irrespective of which profile I'm using.

[nimble glade]

I have same problem of double click (space bar majority )Simon have a tool to analyse the problem and can maybe find whats wrong with this build

[thick flare]

It'd be helpful if you're able to try using this tool I made in this thread #1196768306602983494 message and replicate the issue you're experiencing and give me a screenshot of how it looks

[next bane]

How's this?

I was able to replicate a couple different double-presses of the spacebar, even though I was just doing single spaces.

[thick flare]

Were you focused on something else when doing this? It should display the key presses in the chart if you're focused on the window

[next bane]

Yeah, I was focused on VSCodium to I could see each time that it would register a double-press since it shows which column number I'm on as I hit spacebar.

[next bane]

Is this better?

Here's a more zoomed in view of that same plot:

[thick flare]

@next bane Yeah that's better thanks. Do you only see this happening on the spacebar? How are you pressing the key? Does it happen more often if you press the key in a certain way?

[next bane]

It happens with other keys on occasion as well. And it seems to happen no matter which way I might press the keys.

[thick flare]

Could you demonstrate it on another key than spacebar for me please?

Might be good to move this to DM to not fill up this thread too much

[mystic lotus]

i havent had issues in my BIOS before but i upgraded to 2.06.AS03 [Beta] on my AMD B650E Taichi and when i went to change settings in my UEFI screen i was not able to enter any numbers with my Wooting 60HE

has anyone reported issues in their BIOS with the Wootility beta or is this maybe related to my new BIOS version? i didnt think to check really before updating my BIOS unfortunately

or i suppose i should try downgrading my keyboard's firmware and seeing if i am able to input values in my BIOS after that

[mystic lotus]

also how does the calibration handle having multiple devices connected? like if i have the Z key bound on both my 60HE and my UwU, is the calibration coded in a way where the Z key on one might accidentally calibrate the other?

this is not an actual issue i saw i am just bringing it up since its been on the front of my mind as a potential problem ever since the calibration was added

[ember kettle]

individual calibration on different devices and also on different profiles

[mystic lotus]

appreciate the info very much

[formal horizon]

Hey I installed the beta today on my new 2HE to fix an issue regarding the profile switching keys I was having on stable, thing was outright borked out of the box (update:hard reset/reflash didn't work but installing the beta fixed everything) should I just... leave it on the beta and call it a day? How does it work for when there will be a newer stable version of the software that is out, how will i go back to it Just install the newest version and flash it over my beta one im guessing?

[thick flare]

There is a test build which has some patches which improve compatibility in pre-OS environments. If you use this link https://wootility.io/?test-builds=true then in the Updates part of settings, you'll be able to select "Get Test firmware" for your device, select the one called v2.7.1-test.usb-boot.0. This won't include any of the changes from the beta btw

[thick flare]

I would stick to the beta firmware, you can continue to use the stable or beta wootility and once the next stable firmware release comes out, you'll be able to just do a regular firmware update to that version. If you stay on the beta wootility, you'll be able to get further beta firmware updates as well as the stable one when that comes out

[formal horizon]

Thanks i'll stick to beta as it works perfectly 🙂

I have no clue what caused my issue in the first place but at least the beta fixes it and that's an easy fix if others ever experience it

[thick flare]

The latest of batch should be using the beta firmware right now for best performance, I'm going to push an update to stable Wootility which will automatically give beta firmware updates to Two HE's from the latest batch

[hybrid bane]

Hi, while using the v2.7.3-beta.2 version pressing the fn button turns all rgb off, is this expected?

[thick flare]

Do you have RGB layers configured?

e.g.

[hybrid bane]

I'm dumb, sorry, didn't notice it added the layer when i copied the profiles

[thick flare]

No worries :) The UX for that feature isn't the best, so it's very easy to miss

[formal horizon]

Sounds good, will make their out of the box experience better

[hybrid bane]

Hi not sure if this is relevant, but i have a 60he+ module, have been having some weird glitches while pressing the d key where it would sometimes "release" and not register when fully pressed (about 2/3 times a night for a few seconds and using rapid trigger (i tried different values from .4mm and .15mm) and tachyon mode), with todays release of the sdk update, i looked at the graph and found some interesting data points
I attach here 2 pics: first one using 2.7.2 and second using 2.7.3
Both times i was trying to press as close to fully press as possible
While using 2.7.2 it seems to jump from 3.6mm to 4mm (it even spikes vertically instead of a diagonal) while 2.7.3 seems to have normal behavior and i can press pretty much 3.9mm
I will try to use 2.7.3 to game some more and check if the problem happens anytime, but i would guess what the graphs show is probably the cause of the problem
Sry if this info is not relevant
Hope this helps with development

[mossy valve]

so is 2.7.3 more stable

[hybrid bane]

I would say so, at least more logic, and as far I can sense (its hard to feel 1/10 of a milimeter) feels more logic, the 2.7.2 just felt off, what felt like half of a press wouldn't represent like that on the graph, but could be very placebo

But would love some insight with somebody with some more knowledge

Some keys I tested I couldn't get the input to be within 3.2mm and 4mm, it was either under 3.2 or full press, which I find very weird

[nimble glade]

for me and some people 2.7.2 is more stable it's people dependant

[polar ember]

Where are the release notes for Wootility Web v4.6.13-beta?

i dont see the annoucement

[rich inlet]

Recently updated to 4.6.13 wootility beta. Do you have the changelog @thick flare or can give me info about it?

[nimble glade]

the fn toggle still not work like intented (i try fn and fn lock)sometime the key is count as pressed sometime not (if i press fast and not deep the fn toggle work if i press slow not)the fn key work with the analog monitor tool. second thing the color i choose is not what i have.i put blue and i have white same thing on 4. 6.12 and 4.6.13

[thick flare]

https://wooting-technologies.notion.site/v4-6-13-beta-f018cb1aaef3451fa99132fdfe52077c?pvs=4 This is the changelog v4.6.13. Mainly just fixing up some firmware update things that I also pushed to stable

[nimble glade]

when fn toggle is press only the color change but the keyboard is not in fn 1 mode with arrowp up down ecetera

[celest pelican]

Thx for all ur time fr

[hasty star]

There's not a great place place to create and track ideas for Wootility in this sever. So I opened an idea on the wootility-issues GitHub repository.

TLDR; IMO the distinction between profiles & layers limits capability & creativity.

With the current system I feel the need/desire to create duplicate layers per profile, as opposed to hitting 3-4 keys to access a layer on a different profile, and another 2-3 keys to jump back to the profile I was originally on.

possible solutions

1. Allow for profiles to jump directly to and from layers on a different profile (I'm guessing this would be technologically difficult.)
2. Allow for one on-board profile with 12 (preferably name-able) layers.
3. Allow for 12 on-board profiles (no layers) with keys that toggle or hold to access said profiles.

See aforementioned idea on GitHub for more details. Thoughts?

[celest pelican]

asd

[mystic lotus]

i feel as though #1019755933959733258 would be better so you could make a thread instead of having it so people have to maybe join this beta thread?

community support being appropriate to me since the github issue is aimed at the devs, while discussing it here feels more focused at getting community feedback from more people (a lot of people dont look at github issues)

someone can correct me if that wouldnt be the place for it, but i feel like thats definitely better than in this wootility beta thread lmao

[thick flare]

In general, GitHub is the ideal place for bits like these, but they've already done that so that's good :)

[nocturne skiff]

For me too

[nimble glade]

the next firmware will probably fix majority of the problems

[tired rock]

When will the next stable fw release? Can't wait for it.

[nocturne skiff]

Okey hope so

[celest pelican]

x2

[mossy valve]

Honestly tired of these unstable beta updates lmao

Shoulda just refunded my shet

[formal horizon]

Or run the non beta?

Its called a beta for a reason

[mossy valve]

Non beta doesnt feel good either

[thick flare]

@mossy valve What board do you have? I'm going to be releasing another beta likely start of next week which should resolve many issues

[mossy valve]

The NA batch of last year october

Arm

60he

Or late september

[thick flare]

What issues have you been having and when did they start? @mossy valve

[mossy valve]

Performing worse in game, played better on my old logitech

Feels not smooth

Sometimes i cant stop to shoot

Even tho im used to the sensitivity

[rustic wave]

ngl sounds like ur just coping or not used to settings

[mossy valve]

I didnt spend almost 200 to get a subpar experience

I had it for a few months

[thick flare]

I have followed up in DM

[nocturne skiff]

The new beta will drop today if yes do you know what time ? Thanks

[thick flare]

It is live now :)

It's something I would like to do, but I want to do more testing before I do that

[nocturne skiff]

Omg

[nocturne skiff]

Where ?? Ilv thanks you

[thick flare]

It'll show up as an available update in the Beta Wootility

[nocturne skiff]

Okey thank you

[azure iron]

The Notion is missing the changelog for Firmware v2.7.3-beta.3. 🙏

[thick flare]

Good point, I'll get it added :)

[hybrid bane]

Can someone share the link for the notion change log 😁

[mystic lotus]

here is the changelog from the wootility page at least @hybrid bane

[azure iron]

https://wooting-technologies.notion.site/v4-6-12-beta-789d1bc7d70a4fc1877087d538f3a167

[thick flare]

Could you elaborate?

It showing up as 4mm when pressed is somewhat expected, the new end of press calibration learns where your bottom out is and treats that as the 4mm point

You aren't able to get it to give you any in-between value? That's fairly odd, but with how much you've reduced the travel, it could make sense, as it's linearising it on the basis of it being 4mm travel

I don't have any o rings or things like that to be able to truly test it myself, but to fully support that kind of scenario, I was thinking of adding an option to Wootility to allow you to specify if you're using something to reduce the travel, then it would adjust accordingly

I'll follow up with you in DM

[meager brook]

where can you download this

is that an official software from wooting?

[meager brook]

ok thanks

[dreamy hawk]

Soooo it's 4.6.15 official now and who knows what in beta, but I found a bug and I'm unsure where to download new beta from (not that I think it will be fixed, but the rules are we report using the beta, right?). Where do I get it from? Where is the discussion thread for it?

[nimble glade]

what bug?

[dreamy hawk]

#🔌│tech message

"Test your bindings" should show "DABCD" (because it's reversed and the actual inputs go right to left, so "DCBAD") on the first screenshot. In ANY case, the screenshots, since they're showing different bind order, should have different "test your bindings" results because they have different key order at slots 3 and 4.

I argue they should be evaluated top-down if equal, not "whichever scancode comes first" or what method is used right now.

[gloomy thicket]

I vaguely remember noticing that too. It should indeed be top down. Although it’s just a visual bug, it’s a bug nonetheless.

[thick flare]

Yea that ain't a visual bug, it's to do with how the inputs get handled

The dots that are on the same column, they get input on the same tick, so both get added to the keyboard report at the exact same time

So then it comes down to the OS' handling of ordering, which will be "whichever scancode comes first"

Although, it could be that the behaviour may be different if you disable nKRO, as the 6KRO report will be ordered based on execution order

whereas NKRO reports are ordered on scancode

The only way to properly change this behaviour would be to artificially add a delay between input events to make sure that the dot on the bottom row inputs on the next report after the one above is input

[gloomy thicket]

https://media.discordapp.net/attachments/989302877254205560/1006091229823500308/Wdks.PNG?ex=66011df9&is=65eea8f9&hm=428c568efe36704223f482266d44b243eaaec3663fffdfc0a0410ba3fa9437f4&

🥹 It’s a scuffed suggestion but you get the point. (scuffed as in my execution, could be refined a lot more, it can be much more compact as have the actuation points mentioned don’t have to be there, just start and end per key within DKS)

[dreamy hawk]

@gloomy thicket That would be actually awesome, no artificial delays, you can be sure of the order and you can tweak it to your heart’s content! Though I don’t know if the keyboard has any memory for those additional structures left.

@thick flare Thanks for the explanation - if it's OS then truly not much can be done for most users. I guess the edge usecase for this is not enough to warrant a checkbox "add delays to make sure the keys are input top to bottom", wouldn’t be the most elegant solution either.

I remember you guys more or less committing to custom trigger depths in DKS, so maybe that way lay a solution.

Any chance for getting a link to newest beta and a thread about the newest beta?

[gloomy thicket]

That I really wonder; how much memory is available currently, can memory optimization be done and how impactful would that be. There are so many features left unexplored, maybe because the keyboard isn’t capable of handeling more which would be very concerning to me. After all, most if not all people purchased a Wooting keyboard not for the hardware but for the firmware and features it offers. It has been stale for quite a while now, feature wise that is. What was once a head start is now a close lead with OEMs offering the main features sometimes even with a significant improvement in build quality (except for PCBA) and price. None are there yet but I doubt that would be their goal. 🤷‍♂️

[dreamy hawk]

They opted for more memory but it turned out not to be that much more after all given all the features they're pushing into the keyboard ;). The development feels like it slowed down (but that may not be the case/fair, I just haven't been reading the git lately) and the features planned/creeped got pruned after a consideration (or lost in the development hell).

I am still waiting for easier mass import/export and fixing the alt-tab-during-waiting-for-export bug...

[gloomy thicket]

I believe Simon stated previously that the memory is not the bottleneck but the chip’s RAM is. That was in context of the increased advanced keys, 40 compared to AVR’s 20 (IIRC).

[dreamy hawk]

Well, RAM is a memory, I may have conflated the two together for the sake of simplicity

But yes

I did ask for the advanced keys limit as well, I remember the letdown xD

NGL for my first mechanical keyboard I am very happy with it how it is right now and cannot wait for more updates. I would only like less holes in the outer shell (loooong gash under the space key) but it's just paranoia (afraid I'll spill something and ruin a 250$ keyboard though I never damaged a keyboard by spilling anything in 31 years of using keyboards).

[gloomy thicket]

Haha, I asked for them to just switch over to screw-in stabilizers for the 60HE+ instead of keeping the plate mounts alive (plate mounted stabilizers require that cutout below the spacebar) but they stated it was more costly (which doesn’t apply to the 80HE for some reason). Wooting’s boards are also coated so if you do spill something it has a better chance of survival than others. It’s definitely the most innovation we’ve seen in a keyboard since a long while, that’s why I love Wooting. But, a market that gets more competitive by the minute does worry me. 😂

[dreamy hawk]

Nobody can imitate the analog yet, so no contenders here. I'm not a mechanical "spend 1000h customising a keyboard" or "spend 5000$ on custom keycaps" guy, so all this is below interest threshold to me. Usability, basic look, robustness - all of those are great for now :). I know about the spill resistancy, but I'd still like that huge gash under the space filled, it seems like it doesn't serve a purpose different than sucking particles and hair inside the keyboard :P.

[gloomy thicket]

Analog and gamepad remapping not yet, advanced keys however.. The cutout below the spacebar is for the plate mounted stabilizers, that’s why I mentioned it. You don’t have that cut out with PCB mounted stabilizers. 😄

[dreamy hawk]

Ah, so it serves a function... just in direct opposition to my own needs.

Well, at least someone is happy about it xD. I'll consider stuffing that slot with something so it feels more watertight, but I'm slow on modding so that will probably happen in the next never.

[gloomy thicket]

Oh believe me, nobody is happy about it, never has been. The hate plate mounted stabilizers get is crazy, but justified.

[rich inlet]

I already used the analog app to register the signal on the other thread.

Quick question:

I tried to not press the key but move my finger horizontally on the key and my analog value still gets register. The actuation point is higher so i get no input and that is fine.

But why it regidters analog value if i dont press the key? i mean i only move my finger horizontally without pressing on the key. Just having a low contact and analog value get registered.

Is that what people say about "wobbling" ?

[mossy valve]

Why does the new beta update feel worse for me

[thick flare]

In what way?

[rustic wave]

Just a small feedback, tested 2.7.3 beta for a bit. When playing osu I tend to touch/tap capslock a tiny bit when tapping, after a while of playing noticed that my caps lock basically started double clicking(or even more clicks idk) on every single click, so I assume it's the fault of the new calibration learning implementation, so yeah still not perfect. Didn't take a look at what the signal was reading before reverting to 2.7.2 tho, could do that sometime if it would help

[thick flare]

Showing what the signal was doing in that situation would be very helpful. Without data it's hard for me to do a lot

[mossy valve]

Same as the guy below

[gloomy thicket]

Simon, if you care to read it, maybe start with the last part as there might be limitations I have no knowledge off: https://discord.com/channels/167181566978555904/1218711184925134869

👍

[polar ember]

Where is the feedback thread for Firmware: v2.7.3-beta.3?

trying to perform calibration on my jade switches

not sure where I could find further info on this

[nimble glade]

The calibration is done automaticly

Just plug your keyboard or reboot your pc don't hit key about 5 or 10 seconds and everything is ok

[thick flare]

Then I'll ask for the same thing, I need data for me to be able to do anything. If all I get is "I have double clicks", there's not much for me to go off of.
I need:

• Your performance settings, i.e. Tachyon mode, Actuation, Rapid trigger
• Affected keys and frequency
• Ideally a screenshot or video of you using the analog monitor tool showing the issue happening so I can see what is actually going on with the signal (<#1196768306602983494 message>)

[thick flare]

FYI, Once RGB comes on, calibration should have finished

[nimble glade]

ok nice that's a good thing

[rustic wave]

Sure, I'll try to recreate this when I have some free time 🫡

[thick flare]

btw, I just released v2.7.3-beta.4, changelog:

• Finished fixing up Tachyon Focus Mode on the Two HE
• Fix for crashes on the Two HE (AVR) and Lekker Edition
• When an o-ring is detected, the firmware will revert to stable firmware behaviour to ensure consistent results without deeper support for them

[pure token]

Here's my feedback: you should expose some of these controls on the UI as a toggle (like o-ring detection) which don't leave the end-user guessing whether it was detected or not, like so: Yes | No | Auto

Maybe could also work with the upcoming polarity, and an learning based ongoing calibration toggle

[gloomy thicket]

“When an o-ring is detected, the firmware will revert to stable firmware behaviour to ensure consistent results without deeper support for them.” what does this mean exactly?

[gloomy thicket]

If I understand it correctly, “detection” would not be the right word for it, as it “assumes” until proven otherwise.

[violet skiff]

One of the recent betas' changes, with the changes to how calibration works, if i'm understanding that correctly, it seems to be designed to negate the effects of how stronger magnets like in raptor switches work?

If that's the case, could we get an option to disable that/make it behave as it did before? I specifically got my raptor switches BECAUSE of those stronger magnets. I want that tighter RT/shorter actuation.

[gloomy thicket]

If you wanted the tightest RT and shortest actuation you should’ve gotten the Jades. Those are 0.0875mm per 0.1mm set in Wootility. 😉

[hybrid bane]

Any way to roll back to 2.7.3 beta 3?

[hybrid bane]

2.7.3 beta.4 gives me the same issues i have with the stable version the input is either full or way less, in this case around 3.4 but varies on key

[thick flare]

What switches are you using?

[hybrid bane]

L60

[thick flare]

Hmmm, I see

Give me a min, I'm going to check some things and I'll maybe make a test build for you to try @hybrid bane

[hybrid bane]

Ok, if you need me to try something or send some data, feel free to ask

[thick flare]

Try this build out, I think it should fix it for you, it would be good if you are able to check it works across the keys on your board:

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 2.7.2-test.beta5.0
6. Install update

You'll also be able to see the 2.7.2-test.beta.3.2 build there, which is pretty similar to v2.7.3-beta.3.

[hybrid bane]

5.0 seems ok in the debugger, will do some gaming later if anything weird happens I'll give you an update, will keep the debugger open, thanks for the quick reply

[thick flare]

Alright, cool, let me know how you get on with further testing. Thanks!

[thick flare]

If you're able to give me a firmer confirmation that it behaves well on your end, then I can release it as a new bets firmware

[hybrid bane]

I'll test it in a few hours, and I'll test it for a few hours, after that I'll say something here

[thick flare]

Perfect, thanks

[hybrid bane]

Have played a few games, this feels great so far

Have checked a bit the debugger too and seems to correlate really well

[meager brook]

I just want to say that this build also fixed my issue where if I press down a key on my keyboard and wobble it around it'll deactivate, to fix that I had to increase the release point of my rapid trigger settings. This issue started when I updated to v2.7.3-beta.4, before that it was fine. I'm currently using my Wooting module with l45s and a tofu redux case.

[sour iris]

2.7.2-test.beta5 seem to work stable at my wooting 2 HE, tachyon on, focus mode off. Playing cs2 feeling good so far rapid trigger on GJ 🙂

anything i need to keep in mind with the new beta ?

[flat dust]

I wish we had a way to save custom color presets and move them across different profiles

like Miami FPS etc. but custom

[thick flare]

@hybrid bane @meager brook @sour iris Thanks for the feedback, I'm going to release this as a full beta 👌

[thick flare]

It's released as v2.7.3-beta.5

[sour iris]

2.7.2 beta 5: done 5h testing on cs2 no problems so far, gonna update to the 2.7.3beta 5

there was a error when trying to upgrade the firmware, needed to restart wootility but firmware was already updated ^^. this is my profil for gaming focus mode still disable.

any recommend settings for further testing? Like focus mode etc. ?

[thick flare]

It would be helpful if you're able to test out focus mode. It should be working well now, but needs some more testing

[sour iris]

👌 , anything i should looking for ?

wish you all a nice eastern, gonna give you feedback after my cs2 elo grind 😄

[empty stratus]

was looking into trying it out and noticed the scaling of elements breaks when using an ultrawidescreen lol I think nothing else gets covered and making the window smaller does show everything without overlapping images

[sour iris]

for now everything feels smooth, no errors so far. But im not sure if i can feel a difference between focus modus on and off

i have some question about the calibration
"The firmware will continuously learn while it is powered on and it is idle. In this build, it will save the profiles' learned parameters when you switch profiles. So when you have learned once on a profile and it has saved, it will load it immediately every time that profile is loaded. But it will still do it continuously when it's idle to ensure that it has the most accurate calibration for all keys."

1. is there a way i can see the progress of calibration?
2. what do you mean with " idle" ; idle = power on, not using keys or power on using my keyboard regular.
3. the reason i ask: i have your wristrest, when i put my keyboard away i put it on the rest , sometimes i put the keyboard feet down or switch the angle of it when i use it for regular porpuse. Could all this different positions while the keyboard is on idle make the calibration progress less precise?

sorry for asking that late just seen that pinned message above

[hybrid bane]

Has the beta been released to the main version? is it suposed to appear as beta there?

[sour iris]

2.7.3-beta.5 on this settings working good so far. No problems with Focus mode either👌 gj

[nimble glade]

feedback about the fn toggle not working correctly in the past. now on 4.6.16 beta wootility and 2.7.3 beta 5 it work like intended but the color i choose (in the little circle) is not what i want .i put blue and i have white .i know toggle overide the color in the little circle by white color but that can be great if we can have the colour we choose for fn toggle like caps lock do.

[thick flare]

Beta firmware is rolled out to certain users on Wootility stable

[thick flare]

This is something we have in mind, but likely won't have the capacity to sort for a bit

[thick flare]

1. There is no way to inspect the progress currently
2. Idle means that the keyboard is plugged in, but keys have not been pressed for some time. Currently, that is 5 seconds, but I intend to tweak the timings a bit on that, as 5 seconds was more intended for testing
3. I wouldn't expect it to make a massive difference to the calibration, either way, after some time it'll do another calibration pass and adjust it if needed
   .

Firmware v2.7.3-beta.6
The core changes of this beta release are focused on getting it ready for a stable release with some improvements.

• Refined how key press detection works to make it more reliable and sensitive
• Updated how calibration is preserved across different profiles

[nimble glade]

ok i understand

[nocturne skiff]

Is available now ?

😍

[normal estuary]

No issues since release here

[nocturne skiff]

Holy moly the new beta omg omg is wow 🥵 analog is just perfect I love it crazy beta holy shit

[normal estuary]

I cant wait to test rappy snappy

Thats gonna be such a game changer

[sour iris]

@thick flare thanks for the answer! Already running on beta 6, very smooth so far good work !

[nocturne skiff]

Same here holy shit game changer right here holy cow

[nocturne skiff]

So ? Did you tested it ?

[normal estuary]

No, i am excited for the feature

[nocturne skiff]

For real bro I thought is gonna be normal beta but holy I swear I see the difference

[normal estuary]

I cannot wait to test it

[nocturne skiff]

You will see bro is just crazy

You play analog too?

[normal estuary]

Yeah I use analog!

So will be great!

[nocturne skiff]

Yes perfect

You will love it

[normal estuary]

I check here every day 🙏 hoping to see the rappy snappy beta lol

[nocturne skiff]

What is that ? Sorry I didn’t get it 😭 rappy snappy ?

I talk about this beta the newest one v2.7.3 beta 6

[normal estuary]

I did not get it either, I just read about it a few months ago

I am just waiting to test it

[flat dust]

whet we get rappy snappy in 60he?

[nocturne skiff]

Thank you to sharing that i didn’t know they will add this, is crazy they do great stuff

[nocturne skiff]

I hope so maybe only a arm 60he

[orchid crystal]

bro its crazy

keyboard feels so smooth on beta 6

[nocturne skiff]

You see that 😭the keyboard connected to my brain lol is so fucking insane

[normal estuary]

Will the beta be getting rappy snappy soon?

[next bane]

@thick flare, any idea when the double-input issue will be fixed? It's been an issue for me since at least December.

[zenith island]

anyway to try Firmware v2.7.3-beta.6?

[nimble glade]

#1187862357720977530 message

[thick flare]

Just to confirm, you are facing double input when the key releases and the signal bounces?

[thick flare]

Hopefully soon, just quite busy with various things

[thick flare]

You just need to use Wootility Beta (e.g. https://beta.wootility.io) to get prompted to update to it

[next bane]

I guess it does seem like the second input happens upon key release but I'm not sure what signal bounce is.

[next bane]

I just saw that there's a new beta update that I haven't checked for. Does this beta build address the double input issue?

[nimble glade]

No this update not fix that i have double click on spacebar and this one not improve at all.Simon is working on a fix or improvements

[next bane]

[normal estuary]

Hey Simon, I love your work and the wooting is incredible. I have zero issues personally with the latest beta and the analog performance has been Tier 1. Wooting is the only brand Ill buy keyboards from ever again

[normal estuary]

Is there anyway you could consider at a feature request?

In the Wootility app we can adjust analog diagonal degrees, I would really love if we could adjust forward, back, left, and right. The same way we do diagonal angle adjustment, but for the 0, 90, 180, 270 degree angles. I hope that it would be a low effort nice win addition to the gamepad tab of Wootility.

Thank you!

[normal estuary]

Also if anyone here knows, is snappy joystick the same as rappy smappy?

[gloomy thicket]

It is but not for keys. Just for joystick output.

[normal estuary]

So for the analog movement keys or bound controller keys?

[gloomy thicket]

I think movement only, just going by the name as it’s been a while since I tested this.

[wheat spindle]

I also agree with having the ability to set individual diagonals on joystick keys, and also if possible the ability to have different analog response settings for different keys.

I’d like to have A/D on a far faster curve than I would W/S for walking / running purposes, and strafing purposes.

Having the ability to set individual diagonals would allow us to replicate somewhat single key strafing.

[normal estuary]

Oohhh, I didn't even think about that. Im Unreal in Build and Zero Build and that would be huge in build battles

[normal estuary]

That would be so cool being able to set individual curves for each analog binding

[normal estuary]

@dawn ore

[gloomy thicket]

How beneficial if at all would a temperature sensor(s) be for calibration purposes?

[shy mountain]

Latest beta firmware breaks my setup with toggle keys on Fn Layer:

[thick flare]

This is something we've had on the list for a while. Although, I'm currently not sure when we'll get around to it

[thick flare]

For us, I don't think it's particularly relevant. AFAIK, temperatures that would occur under normal usage shouldn't have any impact on the results of the sensors

[thick flare]

Thanks for the report, I can replicate your behaviour in the latest beta and have made a fix for it. The behaviour will match what you described for the "earlier v2.7.3 beta" as that's what is intended. Is that alright for you?

[shy mountain]

Yes, that sounds good

Thanks

[thick flare]

v2.8.0 firmware which I've released now has the fix 👌

#📰│wootility_updates message v4.6.19 Wootility and v2.8.0 firmware superseeds the builds from this thread

[normal estuary]

@thick flare Thank you for the response Simon! I know an entire community of people who are looking forward to this feature, we talk about it all the time

[normal estuary]

I can ask several beta testers for another product to provide feedback to this adjustable analog feature when you guys do add it, looking forward it :). Ill ask them kindly to come in the specific beta feedback thread here and give you guys their testing results as they are all looking forward to when this is added

[normal estuary]

Do you have list of priorities in development ahead of this analog feature? I would love to keep track of it. Cant wait to test Rappy Snappy. Looking forward to the next beta

[orchid crystal]

W

W

W

[gloomy thicket]

Interesting, I read that slight change of temperature gradually (but consistently) affects the magnet’s force. Probably not much of a difference during use but more so from winter to summer. What is the major con to manual calibration by the way? I can’t think of any that outweigh the numerous benefits.

[thick flare]

~~Didn't you just mention a con yourself? 😜

For end of press calibration, I can see merits to manual calibration.

But for the start of the press, I don't see any good reason. The key is in that position 99% of the time the keyboard is on, so it's super quick and easy to calibrate the current resting position of the signal. With manual calibration, you're somewhat locked into the calibration being used, so it's much easier for it to mismatch the current behaviour.
In one of the beta builds, we had the calibration saving across power cycles, and it was just not good.

To properly utilise manual calibration (for the start of press), you have to do so much work to make sure that the value is still valid, that it just doesn't make sense to do it when it's so quick and easy to calibrate it at runtime.
Automatic calibration is also fairly invisible to the user, whereas manual calibration, by definition, requires people to do something, so I'd say that's also a pretty big con. I find it really hard to imagine a manual calibration system producing better results than our automatic process. So you as a user have to go through additional effort for virtually no gain?

What are these "numerous benefits" you speak of? ~~

Reading the thread you made before about calibration gives me a bit more insight into your thinking, so I'll throw some stuff over there. (I immediately lost it after viewing and had to hunt for it again, Discord's thread system annoys me so much sometimes)

[thick flare]

What is the use case for this community? Is it a specific game?

[thick flare]

We don't really have a priority list, things tend to be quite dynamic as a lot of our software development is centered around products, so that tends to take center stage and we try to get other bits in when we can.

Ideally, we'd track this on github, then it's easy to keep track of the discussion around this and any updates to the development https://github.com/WootingKb/wootility-issues/issues

[normal estuary]

Any games that we can use it on honestly. Being able to customize normal 0, 90, 180, 270 angles like diagonal movement and be able to customize analog curves for individual directions would be incredible.

Take for example the right angle peek, I would prefer using an a slow analog curve for right strafe to make sure I dont overpeek my free shot, and an instantaneous curve for left strafe when Im taking a risky left angle peek or vice versa. Hard to tell what an optimal setting would be for either yet but thats a combo I'd like. Lots of different curve analog possibilities and I love the curve customization where can build our own. This feature adds a lot to our build crafting

[thick flare]

Could you be more specific? Ideally a more concrete use case with a specific game would be helpful for prioritising this

[next bane]

@thick flare, it doesn't look like you saw my response to you that day:

I guess it does seem like the second input happens upon key release but I'm not sure what signal bounce is.

• I am still experiencing double-input issues.
• Latest builds of Wootility and Wootility Beta are installed.
• My 2HE is on the latest firmware available through Wootility Beta.

[next bane]

@thick flare

[gloomy thicket]

He’s on vacation now I believe.

[thick flare]

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

@next bane

and ye, I was out for a few weeks, so wasn't able to work on this until now

[next bane]

Thank you, @thick flare. I installed firmeware v2.8.1-test.debounce.1 and just finished testing it out. As you can see by the below gif, I'm, unfortunately, still experiencing the issue (albeit about half as frequently as before).

[thick flare]

Can you show me in the analog monitor tool? That gives me a lot more to go off of when it comes to tweaking it

[next bane]

@thick flare, here's a video of the issue happening as well. It happens more often with spacebar compared to any other key.

[thick flare]

I see, thanks for the data. I assume this is without using Tachyon mode? I think I need to do some more testing and adjustments for the Two HE specifically, due to the slower scan rate (compared to 60HE), there are less data points I can use

I imagine if you enable Tachyon mode, you'd probably see less coming through

[next bane]

Yeah, this is without Tachyon mode. Although, part way through my video there I did switch to one of my profiles that has Tachyon mode enabled and then switched back to the digital profile shortly thereafter for the remainder of the video.

[molten musk]

i am going to assume test build 2 is a version with more bug fixes.

[molten musk]

is the avr not the same mcu as the two he. Granted there are less keys to scan overall.

[next bane]

@thick flare, I just installed firmware v2.8.1-test.debounce.2 and tested it with the Analog Monitor Tool again.

• At ~42 second mark is when I switched to an analog profile that has Tachyon Mode enabled.
• At ~77 second mark is when I switched it back to my default Desktop profile that has Tachyon Mode disabled.

[molten musk]

what switches are being used for this?

I get the same thing with 3 switches tested: Jades, ks-20 dual rail, l60. Will test my geon raw he switches on saturday when i receive them.

[next bane]

Default

[molten musk]

wooting switches do have a dead zone due to the magnet not being strong enough however

i wonder if sticky rice also have this issue

[next bane]

I just expect the default keycaps/switches to allow the keyboard to not register any key-presses that were not intended.

[molten musk]

Yeah still happens on raw he. Although the switch is quite a bit more muted than jades

[next bane]

@thick flare, as I already shared above, I do still experience the key bounce.
Will your next test build be based on the current v2.9.1-beta.0?

[flat dust]

will it ever be possible to set different rapid trigger per key?

rn you can only disable/enable it per key but not configure it per key

[next bane]

@thick flare, this #1187862357720977530 message is still an ongoing issue for me even after upgrading to the latest available test build:

2.10.0-test.keyboard.2.1

[thick flare]

You can do that in Wootility v5 now

[flat dust]

Awesome

[thick flare]

For debouncing things, you should be using this build currently, although it hasn't really changed much since the previous debounce builds

I need to find some more time to try and get it into a better place, it's not as good it as it can be. It works well for most people, but you have quite an extreme case of this issue

[thick flare]

what are you talking about lol.

The issue here is entirely around the switch physically bouncing when it returns to resting position. Which is made worse by lighter springs and/or heavier keycaps (which can be influenced by the stabs). That's why spacebar tends to be the worst effected

[next bane]

I'm not seeing that build listed when I go to https://beta.wootility.io/?test-builds=true

[nimble glade]

v5.wootility.io/?test-builds=true

[next bane]

https://tenor.com/view/kevin-office-thank-thank-you-thanks-gif-25386923

[nimble glade]

you welcome

[nocturne skiff]

Thank you so much ilv

[nimble glade]

no problem if that can help

[nocturne skiff]

OFC this help me so much

Thank you so much