Wootility v5.0.0 Feedback

[dawn ledge]

[vagrant iris]

1st

[dawn ledge]

Wootility v5.0.0 Feedback

[sinful fable]

[tranquil breach]

wow

[shrewd dragon]

Ok

[placid cobalt]

https://tenor.com/view/oh-my-god-its-happening-ok-stay-calm-the-office-gif-6091046

[random terrace]

[calm mauve]

[silver pollen]

[tacit harbor]

woo and stable firmware version

[void nest]

do i have to update it manually or does it happen automatically ?

[shrewd palm]

first (nooo i was afk for the ping)

[placid cobalt]

it will provid you a prompt

[void nest]

am sorry am a bit new to this stuff so kinda hard to understand lol

[bright matrix]

why is this window popping up?

after being v5 user

also first firmware update failed for me, had to unplug to get it to work

first time that happened

but everything seems to work now on wootility.io

[frozen basin]

80he, same with Jons, first update bricked my 80he and web browser(edge), removing and replugging worked

[bright matrix]

80he also

this never happened on beta releases, had atleast 3 versions of fm updated since i got it. first time happened.

[frozen basin]

and background service when?

[granite thicket]

#1337401502058283008 message

[frozen basin]

ye stable so ༼ つ ◕◕ ༽つ༼ つ ◕◕ ༽つ

[granite thicket]

It was just released

[shrewd palm]

we spent the last 2 months pretty much cleaning up as much as possible so we could now start focusing on features without building up as much tech debt :D

that's the point of "stable"

[near roost]

Are there any functional changes between the v5 beta10 and 5.0?

[frozen basin]

and switch selector or manual calibrator smth

many more to come to this stable version lol

[abstract cypress]

👀

[granite thicket]

Well that would be next version

[near roost]

Changelog is the full delta from v4, so it's hard to tell

[dawn ledge]

You need to make sure to update your wootility.io, it's still got v4 cached

[abstract cypress]

Monthly check for 0.1rt and switch selector

[dawn ledge]

Not really, other than a couple of small bug fixes, like the RT sensitivity rounding issue

[dawn ledge]

Soon™️

I'll be shifting my focus towards it after v5.0 stable has settled :)

[abstract cypress]

Nice

[bright matrix]

by that comment what i think happened. v4 cached, while being v5 user already with 12 profiles, 4 on keyboard. Did it try to flash beta with same version but different name and something went wrong ? Just a headsup, if all of the 80he users are going thru that. Would need someone who hasnt used v5 before and only used wootility

[errant hedge]

Praise Simon 🙌🏼

[bright matrix]

Or if there is something you guys can do to not get error first time

wish i took screenshot of the error but while windows+shift+s clipscreenshot not working, didnt go thru the hoops to get clipper from windows startmenu

[fallow nebula]

Hello I’ve been using an 80HE for a few months now and now that migration to v5 will I be able to move all my 60HE profiles over?

[dawn ledge]

Did it try to flash beta with same version but different name and something went wrong?
Don't think so, the popup you shared was just from it detecting the 80HE and giving the prompt to use v5.

Unfortunately there's not a whole lot we can do to skip the cached v4. We just have to rely on users that have it cached to get it to update to v5 to complete the migration

[abstract cypress]

You were able to do that before

[fallow nebula]

Oh how

[abstract cypress]

youll be missing some keys when you import your 60HE profile, all you need to do is go in remap and click Default

[bright matrix]

been using v5 site since i got the keyboard, the firmware gave error when flashing, the site error is just another thing, but firmware got bricked until took the usb out of keyboard and replugged in.

and reflashed

[dawn ledge]

If you were using your 60HE on wootility.io, then they will be there and when you migrate your v5 instance to it, then it'll add your 80HE profiles to the profiles on wootility.io

[slim agate]

omg stable wootility v5🎉

[fallow nebula]

I used the wootility lekker desktop app

The web app never worked for me

[bright matrix]

But just gave my info how the migration went for me, so you know some of the 80he users will go thru the same flashing errors and everyone has to replug the keyboard on reflashing. Not sure if user didnt ever use the betas

[shrewd palm]

Added migration stuff
Some minor very safe fixes only (RapidTrigger rounding bug and some text/padding fixes)

[dawn ledge]

In the coming days, v4 Wootility desktop users will get an update which will assist them moving to Wootility v5
This is the relevant bit for you then :)

Although if you're using v5 desktop, then you'll need to share your profiles and import them in v5 instead. As the desktop migration can only move over the v4 stuff and overwrite v5

[dawn ledge]

When you were updating to v2.10.1 firmware on v5 stable that is?

Were you able to follow the instructions it gives you to recover the keyboard when an update fails?

[fallow nebula]

Thank you yes I am using v5 desktop app so ill do that thanks

[bright matrix]

yeah, it gave prompt to replug the keyboard and press button, it worked fine.

[dawn ledge]

Ah okay, so you were able to go through the whole update flow, just that it failed in the middle and had to restart?

[bright matrix]

yeap

and also the another dude right after my comment went thru it also

so im guessing we have both used v5 site, and started using wootility just now ( i have opened the site when i got the keyboard), and it gave error.

[dawn ledge]

I see, unfortunately that just happens sometimes, we've already implemented some improvements to reduce the error rate, but we've also got some more bits for it.

Luckily we have the recovery flow inside the update process, so for most users it's just a little annoyance, rather than you having to restore and lose your profiles

[bright matrix]

yep yep, all good for me. Just a headsup for you guys if you get users having errors like me and it doesnt go aswell for them.

no clue why it wouldnt be go fine for them aswell. Just a info beta tester things 😛

[sharp gulch]

[sinful fable]

[near roost]

Something about this line tickles me:

Visualize arbitrary information with the 80HE’s Light Indicator
I would like to visualize the twitter firehose via lightbar 🙂

[placid cobalt]

https://tenor.com/view/nootcoinada-noot-noot-noot-pingu-wearenoot-gif-10262976141602962406

[frozen basin]

recovery popup didnt showed up for me, whole browser was stuck. using edge

[sage orchid]

Wootility v5.0.0
Analog SDK v0.8.0
Wooting 60HE+ (firmware v2.10.1, ARM)

I found a visual bug in the Snappy Tappy tester:

1. set up a pair of keys
2. turn on "Alternative fully pressed behavior"
3. fully press key 1, fully press key 2, release key 2
4. continue holding key 1 until a duplicate of key 1 appears

result: key 1 and its duplicates will continue to be displayed in the "Pressed Keys" box, disappearing a few seconds later

expected result: with both keys fully released, nothing should be shown in the "Pressed Keys" box

[dawn ledge]

Not sure what you mean exactly

[near roost]

Here's a weird one that's somewhat related: https://wooting.io/wootility/changelogs pegs my CPU on firefox 🤔

[frozen basin]

this one

[shrewd palm]

Looks like video decoding... the changelog for 5.0.0 has like 10 videos playing simultaneously and they're all high res 60fps

[near roost]

Seemed worth pointing out cause I'm on a 7800x3D and it brought my system to a crawl 😆

[shrewd palm]

bruh why is firefox rendering the videos when offscreen 😭

[sinful fable]

dude im on a 9800x3d and

firefox is such a horrible browser

[near roost]

It's certainly got its warts

[stone elk]

tf

[ruby musk]

google prop right here

[graceful spoke]

@dawn ledge, have you been able to make any additional progress on the key bounce issues? (I'm still on v2.10.1-beta.4+debounce.2)

[dawn ledge]

We're going to be doing another push on it once the dust has settled with this release. I can create a fresh test build based off of the stable firmware for you to use now :)

[graceful spoke]

Ok, thank you. Please let me know when that's available.

[dawn ledge]

Released it as v2.10.1-beta.9+debounce.2, v2.10.1-beta.9 is equivalent to v2.10.1, I found some problems making test builds off of the stable version I gotta sort later 😅

[humble pivot]

Sorry, is there some finnicy nonsense I'll have to do to update my desktop app, or is it just a normal update? The wording used here is a bit confusing on if this is just a normal update.

[sinful fable]

If you were already on a beta v5 desktop version, you let it auto update and that should be it

[strange kernel]

I'd really miss the good old "Her serial number is". It was more... you know, personal.

I understand it's not that important, but... any chances to bring it back?

[silver pollen]

I would like this

[granite thicket]

I never noticed it said that until now

[arctic wasp]

good evening, is the analog jump from 3.25mm to 4mm a known bug?

searching the discord for words like "3.25mm" I see various reports even from several months ago about the new firmware, but maybe a report has never been formally made and you are not aware of it.

[slate atlas]

Yay

[sharp vale]

So now you can use the wooting application for the 80he?

[near roost]

You've been able to before as well, just had to get the v5 beta. Now you don't have to get a beta version 🙂

[boreal iron]

It is. I believe it got fixed numerous times already but it makes it way back every time 😅. Are you experiencing it with Raw HEs or Jades? Or some other switch?

Which board and firmware version is important too.

[arctic wasp]

lekker v2 on 60he, latest stable firmware

[boreal iron]

It should not and has never happened with Lekkers.

Did you shorten the travel of it in anyway and are all switches affected?

[arctic wasp]

all switches are affected, but is quite random

[boreal iron]

Quite random?

[arctic wasp]

in the sense that after pressing it a few times it starts working correctly again

the next day maybe other keys will have the same problem

[boreal iron]

Interesting, perhaps it’s an issue with initial calibration if the calibration during use resolves it. You aren’t pressing any keys when the board turns on right?

[arctic wasp]

when i press it quickly many times it seems to fix it

[boreal iron]

You should be able to press it only once quite hard to resolve it as well.

Really odd that it happens with Lekkers though.

[abstract cypress]

check on https://analog-monitor.wootility.io

[boreal iron]

He is

[arctic wasp]

I used that

[boreal iron]

Are you hovering?

[abstract cypress]

Weird

[boreal iron]

Like very slowly pressing right after the first calibration?

Not pressing it fully.

[arctic wasp]

I don't think so, I'm someone who presses the keys quite deeply when I write

[boreal iron]

In the video you pressed them fully when they shot up from 3.25 to 4?

[arctic wasp]

yes

[boreal iron]

Interesting, shouldn’t happen.

Only on switches with weaker magnets.

and because it happens with all of them, probably some bug in the recent firmware that causes it.

[arctic wasp]

now no key has this bug anymore, until this afternoon about 15 keys had it lol

[boreal iron]

If you unplug and replug the board, all will have it again most likely.

Then you can press them once a bit hard and they’ll calibrate properly.

[arctic wasp]

ok yes exactly, unplugged and replugged and all keys have the problem again

anyway yes you are right, pressing it all the way down once solves it

[boreal iron]

Yeah, it has existed for a long time to compensate for switches with weaker magnets and O-Rings.

[boreal iron]

It’s not a solution though, just trying to explain the behavior a bit haha. You can’t press all keys before you start typing.

[arctic wasp]

of course it's nothing annoying, i don't think there's anyone on this planet who would notice it without that graph. it was just to report it in case it was actually a firmware bug

[boreal iron]

You aren’t hindered by it right?

[boreal iron]

Yeah, it is. Good that you mentioned it.

[errant solar]

I’ve had this bug for a long time, I don’t know whether it’s some visual bug within v5, as I never fully use 4.0 actuation but I mentioned this months ago and I still have this issue, regardless of lekker, jade or magneto switches

[granite thicket]

If it happens on the analog monitor, like for Pedro, then it's not a visual bug

[errant solar]

I was just about to say, I just checked the analog monitor and my keeps seems to be actuating weirdly as well, I’ll try and send a screen recording…..

it definitely seems like a few of my keys towards the middle and right side of the board do act up....

[radiant gyro]

Good I wanted to tell you that since yesterday when I updated the new version of wootility the Wooting 60he keyboard started to give me failures literally what happens to me is that when I do the strafe in valorant, that is, I press the A and D keys to do the counter strafe, the A and D key often gets stuck and what it causes is that the character literally goes left or right all the time, which makes it impossible for me to play because when I want to press both keys, the A or D key is usually caught

Sorry for my English but I'm using the translator since my English is the worst thing I've ever seen 🙃

If someone would be so kind as to tell me what's really wrong with my keyboard, I'd appreciate it very much

[nova trail]

The Wootility seems to now have a pretty strict Content-Security-Policy, so I can't use it in Firefox anymore.

Anyway, I can keep on using V4 for now, but this issue with the gamepad key scaling seems to persist in V5

Funny enough, this isn't an issue on the actual gamepad mapping tab

[granite thicket]

You've been able to before? I thought FF didn't support WebHID?

[nova trail]

It doesn't, but I have a server running on localhost with an extension that talks to it

[granite thicket]

Interesting, well as long as FF doesn't support vital features it's not supported

[nova trail]

I think their plan is to support it in the near future

just with their own software that you have to install

[granite thicket]

Not possible without WebHID?

If you're installing software you might as well install Wootility?

[nova trail]

Get with the times, nerd. Everyone just does everything in browser tabs now

[granite thicket]

No?

[nova trail]

😛

Installed software does have drawbacks tho

I think it doesn't make an insane amount of sense to install a GUI for managing my keyboard

and the backend C++ program that just provides basic HID APIs is much more stable

i.e., doesn't need to be updated basically ever

[sinful fable]

while i like the conversation topic, please move to #🤖│community_dev . If this thread gets too cluttered, we will lose track of actual feedback, thanks

[nova trail]

Well, my feedback is here.

[iron crow]

just thought i'd mention this here but 2.9.2 firmware seems to be making my keyboard repeat letters, reverted back to 2.7.2 and it's working perfectly fine, for those who may have the same issue
thought maybe it might be my new gateron ruby pro switches but reverting firmware has completely fixed it it seems

[restive socket]

would be cool if the New Text / yellow dot next to the light indicator would vanish after like opening that section for the first time or sum

[shrewd palm]

can you get us recordings to catch repeating letters? https://analog-monitor.wootility.io/

[dawn ledge]

https://wooting.io/wootility/changelogs/4.7.4

https://wooting.io/wootility/changelogs/5.0.1

[granite thicket]

Migration seems to have worked great, all my profiles look right

[bleak verge]

Upgraded to 5.0.1. Firmware update from 2.9.1 to 2.10.1 on Two HE fails for me, disconnecting and reconnecting does nothing, just loops. 🤷‍♂️ 🤷‍♂️ 🤷‍♂️

[oak stratus]

V5 comes out the same day I get my first keyboard! I’m so excited!!!

[dawn ledge]

Two HE AVR or ARM? Is it always error looping? What are the logs?

[kindred zealot]

works like a charm. good job guys !

[bleak verge]

ARM. Error: "Timed out finding bootloader" , "Attempting to resume service" "Service not allowed resume, pausing"

Fails at step 3, reconnect and restart, same result.

Thanks for your help.

[dawn ledge]

Those logs have nothing to do with connecting your device to Wootility. "Timed out finding bootloader" only would be related to doing a restore or fw update

Can you send me your full log file?

[dawn ledge]

Forgot to post this here, whoopsie
https://wooting.io/wootility/changelogs/5.0.2

[copper sail]

I'm completing the google form survey right now. My opinion as an old user using Wootility Desktop still stands: We need profile auto switch for games/apps selected.

Btw, here is a bug: Language interface settings is all empty for me.

I'm on Wootility 5.0.2

The error Log says: [warn] We tried to match the locale 'es-419' using the following, but couldn't find a match { fullLocale: 'es-419', mainLang: 'es' }
[warn] Selected language es-419 isn't supported, defaulting to en

[bleak verge]

I'm aware of that, but the firmware update for my ARM Two HE only appeared after the Wootility update. I will DM you the log. Thanks again.

[brisk pendant]

I upgraded my wootility from 4.0 to 5.0 and my whole keyboard has shut off and won’t turn back on I’ve tried absolutely everything

[brisk pendant]

Thank you so much for a reply, i will try this once I get home, I’ll let you know how it goes :))

[brisk pendant]

It worked thank you so much!

[dawn ledge]

Thanks for the report! When digging into it I found some other issues and fixed those as well.

It also highlighted some issues with the language fallback, so we made some improvements to that as well. For your case, it'll now make sure that your es-419 (i.e. Spanish Latin America) will resolve to es-ES (i.e. Spanish Spain).
More generalised, it'll fallback to the most complete translation that shares the same main language (here being es) if your exact locale hasn't been done.
Ofc you'll be able to change it to English if you desire, at least it'll give you the language option now 😅

It'll be part of v5.0.3

[open steeple]

I haven't been able to get it to close to my disc manager since upgrading it, is that feature completely removed or will it be added in the future?

[dawn ledge]

Do you mean closing to the tray with the little icon? That usually only happens if you're using the Chroma Connect integration

[dawn ledge]

https://wooting.io/wootility/changelogs/5.0.3
Another little patch update 😁

[slate atlas]

yay

[open steeple]

Ohh, okay. Thank you!!

[abstract cypress]

Day 103 of waiting for switch selector and 0.1 rapid trigger 😴

[copper sail]

Wootabase One Click Profile is not working with V5 Wootility @dawn ledge

[boreal iron]

@lusty locust experiencing spazzing and affecting more and more keys (it was just backspace at first, now it’s multiple keys). Happens only on Tachyon and changing the RT sensitivity helps.

Profile code: 0f4600b4bd75a3c3937e764f022e83d97be8

(it’s not windows, PC restart didn’t help)

[left estuary]

5.0.3 is super duper laggy

[dawn ledge]

The behaviour shown on video is very bizarre, is there another thread for this somewhere?

[dawn ledge]

Could you elaborate a bit?

[boreal iron]

Not with more info I’m afraid. It was posted in #🔧│keyboard_modding here: #🔧│keyboard_modding message a bit below is the video. He’s using a 9800x3d with an X870 mobo, doubt that matters but that’s the only info I have.

After a full reset and creating the profile from scratch, it did resolve itself (so far). Only other thing he noticed after resetting is this:

(that’s without touching any keys at all)

[abstract cypress]

Day 109 of waiting for switch selector and 0.1 rapid trigger 😴

[errant hedge]

https://tenor.com/view/upset-woman-padded-padded-room-angry-hopeless-gif-1804075065120708208

[lusty locust]

HI! no further issues since i did reset on the keyboard

[lusty locust]

feel free to ask me anything you need. It just started out of the blue. Only with tachyon mode activated. Im using the 50€ cable from you guys. Been using it since august with the 60he+ with 0 issues. I double checked the jst connector was properly plugged and also on keyboard end. It just wont register on windows but i could see it activating on wootility (web). At first it was only esc key, then backspace, then while playing counter strike it started to lag or not register. I got the settings imported from my 60he

[dreamy kernel]

not entirely sure if this is the right place to post this but the link to the guide is dead

[vagrant iris]

Does it work without the /en/?

[dreamy kernel]

yeah it works now

[vagrant iris]

@dawn ledge fyi

[winter lance]

My wooting 60he+ has had a bug since i bought it that happens every few days where a certain key wont work while typing in a certain application then if i switch to another application the key will work and then if i go back to the original application it will then work and i dont know how to fix it

[mighty plaza]

this is not a bug but something on your pc causing it

[winter lance]

has happened on a few pc's and on fresh pcs

[mighty plaza]

nothing about the wooting keyboards do anything different whether program X is in focus or Y

better if you make a post in #1019755933959733258 so people with troubleshooting knowledge can help you figure it out

[boreal iron]

A bug, surely? https://discord.com/channels/167181566978555904/1350973638832165036

[dawn ledge]

https://wooting.io/wootility/changelogs/5.0.4
New patch release 😁

[slate atlas]

Yay

[mighty plaza]

when v5.1 featurepack update, DLC and battlepass?

[abstract cypress]

Me and all my neighbours are waiting for 5.1 wootility update

[errant iris]

this last update made my wooting go crazy. buttons are pressing themselves.

[abstract cypress]

Try restoring it (save profile before doing that)

[errant night]

When is switch selector coming?

[dawn ledge]

Cool stuff coming soon 😉

[dawn ledge]

Still WIP, no specific ETA yet

[stable crescent]

I’m curious as to why users are able to add the same RGB effect multiple times. Could this potentially lead to conflicts? For example, if the Scan effect is applied twice with the same direction, it might cause flickering on the keyboard.

[errant solar]

I think this is an addition to a few posts before this, that mention inaccuracy within analog monitor. I'm noticing that if I provide a slower, consistent force on a lot of switches, there is a disparity in what wootility's actuation feedback shows compared to the analog monitor. The actuation shows full pressed, but in analog monitor the keys don't reach full actuation or experience some sort of jumpiness. Probably not best explained but hopefully the video below better portrays what I am mentioning. (Wootility 5.0.4, FW 2.10.1, TTC Magneto RGB, 75% brightness and tachyon mode).

I need to test this without tachyon in fairness, but it seemed worthy mentioning as there definitely seems to be some different between what the visual actuation shows and the analog monitoring.

[granite thicket]

Odd, I don't experience that

[native osprey]

might be because you seem to use 4mm travel switches, not like the TTC Magneto RGB which are 3.4mm, which seems to get stretched

[granite thicket]

I've never seen them behave the way shown in that video before, from what I've seen recorded before they usually go steady until a point where they jump to the end. In the video above the analog monitor seem to lag behind and jump very early at times (the video from oli).

[boreal iron]

Analog Monitor seems to update extremely slow here, perhaps something PC or browser related or because both Wootility and Analog Monitor are open? Are you using hardware acceleration in your browser?

[placid cobalt]

Most likely, graphics acceleration is disabled by the browser. ( tends to show up that way)
If you wish to enable this (for Chrome), go to:
Settings > System > "Use hardware acceleration when available" (enable)

[errant solar]

I have just read untamed's comment (below) and he is seemingly correct. Turns out it is user error and the result of slower rendering due to the fact I had HWA turned off.

[errant solar]

No I turn off HWA, I have just tested and can confirm that was the issue though.

[errant solar]

Correct... my fault I completely forgot about the oversight of HWA. All is fine.

[dawn ledge]

https://wooting.io/wootility/changelogs/5.0.5
Another little patch update

If anyone asks for switch selector I'm delaying it by a week

[boreal iron]

Any update on the ||must not be named||? 🙊

[dawn ledge]

Sneaky

I'll let it pass this time

[abstract cypress]

0.1 rt ETA?

[placid cobalt]

i think wootility is trying to tell me somthing

[dawn ledge]

Same as switch selector

[abstract cypress]

shocking

[slate atlas]

Any plan for woot numpad

[dawn ledge]

Not in the near future

[untold epoch]

Why did you add an extra click in wootility to change profiles? 99% of what I use wootility for is changing profiles since I have them all set how I like, what was the issue with them being in the side bar?

[vagrant iris]

fn + enter swaps profiles

[untold epoch]

I guess I just dont get why there are now 2 side bars neither of which do what the old one did and there isnt an option to get that functionality back

like why isnt the left side bar just the old one and the settings and help at the bottom, like in the old one and like most UIs

[vagrant iris]

I appreciate you leaving your feedback, just wanted to give you a quick option to swap 🙂

[harsh fossil]

Idk if this is a bug or not but basically when using the 8k hz tachyon mode i can't raise the brightness above 70% from a keyboard function set from wootility itself and i have to do it manually through software every time. Curretly using latest stable 0.5.6 and latest firmware 2.10.1. Basically the function ignores that i have the lock button for the brightness inside wootility unlocked and caps out at 70%.

video example here #💬│general message (if needed i can upload the video on google drive for higher quality)

[dawn ledge]

That is not a bug, the firmware will only allow you to go above 70% brightness in Tachyon mode if you're already above 70% brightness. That being said, we do have a note to improve the UX of this