Wootility v5.1.0 Feedback

[silent grove]

[vocal glacier]

[silent grove]

Wootility v5.1.0 Feedback

[subtle plank]

noice

[sage rain]

Hi simon

[jagged umbra]

🛂

[sage rain]

Hows switch selector going

[silent grove]

It's going 😜

[wise furnace]

I thought switch selector ffs

[split heart]

[sage rain]

Oh wait... arent you are going to release it with 60hev2 dont u

[lunar parcel]

[wise furnace]

the changelog site crashes on movile for me

[simple mirage]

Crunch selector when

[silent grove]

ish, aiming to have it out before, 60HE v2 is more of a hard deadline for it to be ready for stable

[upper ocean]

[silver crypt]

Good shit

[wise furnace]

seems like something loads and that causes it to crash

[sage rain]

Ok, i'am still waiting for gamepad upgrade.

[lunar parcel]

Something round

[silent grove]

oof, not able to replicate it locally, any other details you can find?

Also, Android or iPhone?

[upper ocean]

big moves

[placid crest]

Is light mode there yet?

[upper ocean]

no

[echo grove]

whats new?

[silent grove]

Sometime™

[lunar parcel]

Have the same issue on iPhone xd

[sage rain]

Definetly 2nd analogue curve would help me with scandinavian flicks

[simple mirage]

I will wait patiently for crunch mode

[wise furnace]

iPhone of course

[echo grove]

whats new with this update

[lunar parcel]

Literally same

[subtle plank]

i can't even open wootility on iPhone
it's saying my device isn't supportet

[wise furnace]

you had to scroll over the announcement and changelog to get to this thread, cmon man

[echo grove]

yea sorry i saw it now thx

[wise furnace]

it’s not wootility that crashes but the changelog page

wootility doesn’t work on iOS or Android :)

[vocal glacier]

we're looking into it, it's working on our side on both platforms :/

[wise furnace]

classic

[silent grove]

Works on my machine™

[strange canopy]

cant wait for switch selector

[wise furnace]

we’ll have to

[silent grove]

Same

[wise furnace]

[silent grove]

Soon™™

[strange canopy]

I just dont want wootility to lie, it's 3.4mm damnit!!!

[knotty scarab]

will switch selector be like a list of switches, or an adjustable bottom-out distance?

[silent grove]

You will be selecting the model/family of switch you are using

[knotty scarab]

sweet

feels more personalized that way

[silent grove]

The make the switches perform as good as possible, they need dedicated linearisation curves based on collected data from that Switch. So first beta release will be focused on switches we have a decent amount of data for already, and if one you have isn't listed, it should be fine enough to use a switch with similar travel

[knotty scarab]

thorough as always 🙏

[west root]

@silent grove, for the key bounce issues I've always experienced on my Two HE, do I need to:

• stay on my current build v2.11.0-beta.0?
• upgrade to the current stable build v2.11.0?
• switch to one of the test builds v2.11.0-beta.2+debounce.3/v2.11.0-beta.2+debounce.4?
  

[silent grove]

If you've been using the Debounce filter integrated into v2.11.0-beta, then you should update to this latest firmware and continue following updates, you shouldn't need to make use of older versions or test builds anymore :)

[silent grove]

Can you check if it's still happening for you?

[wise furnace]

:/

🤷‍♂️

I thought that it could be that apple website protection or whatever, but I have it off

request desktop website doesn’t help

[hexed rose]

what does the [ARM] tag mean in the changelog?

[vocal glacier]

it means it's for ARM devices only. if you have an older AVR based model, it won't be supported

[hexed rose]

ahh, thats for the keyboard right? guessing you dont mean arm on pc's

[vocal glacier]

yeah. the newer keyboards are all ARM but if you have an old keyboard it might be avr

[hexed rose]

ahh alr

also it says it added rgb preview, does that only work if you have a keyboard? bc it doesnt work in the demo. i ordered one but its not here yet so im just figuring out wootility for when it arrives

[vocal glacier]

yeah it needs a keyboard connected

[hexed rose]

alrr ty

[fallen agate]

it crashed mine I had to reboot the keyboard to connect it back

[wise furnace]

Not sure if it’s been asked before, but can a “Recalibrate” button be added? It’s rather cumbersome having to unplug and replug tens of times when testing switch compatibility.

[lunar parcel]

I have a similar issue only on the changelogs page and on the Tofu TKL page, which is strange and suspicious

[wise furnace]

yes lmao, it happens there too

[lunar parcel]

XDD

[wise furnace]

clearly this confirms that woot has been bought out by kbd

[vivid trail]

So basically nothing for avr?

[vocal glacier]

We try as much as we can to keep it up to date but the hardware just can't handle any new features :(

[scenic onyx]

My keyboard gets disconnected from wootility after changing rgbs and after that I must restart my pc to get it reconnect

I use 80 he

I posted a video about it on community support too

[gaunt nimbus]

I assume auto matic game profile switching is still on the list of things to add to wootility? is there any sort of timeline for that?

[wise furnace]

“Soon™™”

[fringe nimbus]

tbh -- I'm not super enthused about that feature, I imagine it's gotta add an OS-level hook to be able to see running apps which makes the tool heavier and more of an impact on background running resources; I hope if they do that then they also maintain a "wootility lite" version that doesn't have that stuff and just does the awesome job of configuring the kb that it does now

[vocal glacier]

this is what will happen. The background service that provides this functionality is and always will be an optional add-on that will work alongside wootility, but you can skip it if you don't want anything running.

I'll also say that it will consume <10mb of memory and basically no cpu usage, so if you do want these features it won't take up significant system resources.

[gaunt nimbus]

I can see where you are coming from to some extent because we are used to apps like the ones Logitech and Razer bring us and this used to be a “pointless feature” I never used.

With the wooting I use dks for jump throw binds in cs. When I’m in game and tab out to chat with someone on discord I have to remember to change profiles then I have to remember to change again before I tab back in. When you want to type a single sentence or less it feels pretty clunky. Even worse when you forget to change profiles and now you try to type one letter and it puts two letters a symbol and hits enter

[heavy stump]

I wrote a c++ program that I use personally for automatic profile switching depending on foreground window, and i've noticed that the time to change the keyboard profile index went from ~100ms on keyboard firmware 2.9.1 to 250-350ms (!!) on the newest 2.11.0 firmware. this is particularly impactful when tabbing out of a game and the slow profile index switching time means that the keyboard isn't ready to type as quickly on the newer firmware. this generally results in missed inputs and/or lost letters when quickly switching between apps and typing in text fields.

Within my program, I only call ACTIVATE_PROFILE, WOOT_DEV_RESET_ALL, and REFRESH_RGB_COLORS. There is another program that also called RELOAD_PROFILE but I found that to be unnecessary for simple profile switching. I can't seem to reduce the switching time below 250ms when using 2.11.0, so I've had to stay on the older 2.9.1 to keep the usability of the faster profile swaps.

Is there any way that firmware 2.9.1 would be still available/functional on this newer wootility version when the magic profile switching is released? alternatively, would there be a way to optimize the profile switching speed below the current 250-350ms on firmware 2.11.0?

[vocal glacier]

do you know which of those calls takes the most time?

also, which keyboard are you experiencing this with?

[heavy stump]

Not certain right now since I was timing my personal method which included the 3 calls to wooting_usb_send_feature. I will verify and report back. Keyboard is a 60HE

[vocal glacier]

which variant of 60HE is important, ARM or AVR chip?

[heavy stump]

ARM

[vocal glacier]

I'm testing on my 80HE which is faster to do this sort of operation (mostly because of usb high speed)

and it takes up to ~10ms or so. I'll test on one of my 60HEs as well for good measure

[heavy stump]

on 2.9.1 firmware: ACTIVATE_PROFILE and REFRESH_RGB_COLORS complete in approx 15ms (14-16ms) but WOOT_DEV_RESET_ALL takes around 80ms when changing to index1 and 60ms when going to index0

[vocal glacier]

are you also controlling rgb? you shouldnt need the last commands if you're just changing profile

[heavy stump]

which one? WOOT_DEV_RESET_ALL?

[vocal glacier]

you should only really need ACTIVATE_PROFILE

[heavy stump]

that's interesting. I had some issues with rgb not updating when calling only ACTIVATE_PROFILE

[vocal glacier]

that might be a bug :p

[heavy stump]

will try with just that right now

yeah I'm running only ACTIVATE_PROFILE and the other 2 were commented out. Brightness changes, but RGB stays the same as the profile before the call

I added in WOOT_DEV_RESET_ALL and the RGB seems to change correctly

still have REFRESH_RGB_COLORS commented out at this point but behavior seems normal

[vocal glacier]

do you have signal rgb or similar rgb software running?

[heavy stump]

i have zero rgb software running

[vocal glacier]

you can add me if you want to dig into this more, but I don't want to pollute this thread anymore and certainly not today :p

I do find this weird though and want to investigate

[heavy stump]

will do, thanks

[upbeat skiff]

is it somehow possible to set the inital state of the windows keys for the gaming mode ? i can disable windows keys but i dont know how to disable them in advanced for switching keyboard mode to gaming

[upper ocean]

i mean id just remove it entirely from gaming

[upbeat skiff]

thanks actualy you gave me the idee i just put them on absolut 100% press instead

so they work but only at 4mm

[limber cargo]

I hope that next stable release will include MACROS!!!

[upbeat skiff]

than yopu hope wiothopuit result

thats simply what a software like this cant do

if you want macros get AHK and make them happen

[wooden ether]

5.2 wen

[wooden ether]

5.2 wenn

[silent grove]

Soon™

[wooden ether]

https://tenor.com/view/stan-twitter-monkey-sad-depressed-bored-gif-14632661802414689947

[gleaming canyon]

would be cool if debounce filter toggle was a profile specific setting

[lost fjord]

I have a suggestion for the RGB effects, one is letting people Who use Tachyon Mode put RGB effects as you did with letting us increase keyboard's bright, and second one is making an effect that when theres music on the background, the keyboard reacts to It.

[upper ocean]

the first is just not possible

[lost fjord]

😭

[upper ocean]

how tachyon works is just removing everything else that takes computational power

which is rgb effects

[lost fjord]

But if I can play with It and 100% brightness why isnt It possible with RGB effects?

Or is just too much for the cable?

[upper ocean]

brightness is just power

no need for the brain to compute anything

its lowkey a botched explaination

but there is data and power

data is the limit here

[lost fjord]

Damn

Thanks for the info!