#Wootility v5.0.0-beta.3 Feedback
1 messages · Page 1 of 1 (latest)




funny enough i just flashed it before the announcement came in
anything cool for my 2he?

Knight Rider profile for the led bar included yet?
Is Firefox browser support on your todolist ?

Do you mean something similar to the Scan Effect? We don't have anything like that yet (unless you use the main RGB effect and use the Sync effect)
Firefox doesnt support WebHid which is needed to even be able to do so.
switch selector waiting room
Firefox support is blocked by it lacking WebHID and other APIs for Wootility to work correctly. That being said, the Background service may open up support for Firefox with Wootility Web (although at that stage you may as well use the desktop version)
Same, it's very high on my personal want list, we are working towards it tho
Most of the new things with this release are only related to the 80HE. If you're coming from v4 tho, then having full per key Rapid trigger would be one of the bigger things (if you have a Two HE ARM)
WHAT wooting What do you want
haha im on beta 2

wouldnt it still be favorable to do that instead of having to download an electron app? idk how the background service works
I only just got mine and aren't at my PC so I can't check what the Scan is, but I just think it's a missed opportunity on the LED bar to not have that iconic Knight Rider Kitt's back and forth red light effect. Just because it's cool 😎 I tried making it but I only figured out how with the Sync but I wouldn't want it for the whole keyboard. I'll check again with Scan when I get home, thanks for the tip
Can yall add an led bar effect that only lights up when a certain key is pressed
So if i press Space it will light up a selected area of the bar
and if i press anything else it won't
The background service is something you have to download and run on your PC, so that + Firefox vs Desktop build would be pretty similar, but it can get a bit into personal preference territory.
I suspect there will be some other things broken with Wootility Web on Firefox, so that may bring the experience down when compared to the desktop version.
Either way, it will likely be something that'll be viable to use, so the user can decide what they want to do
@tepid roost @last geode thanks for the answer
how can i be a tester
done

i have
I see, it looks very similar to the scan effect, so I'll add the idea to our list and maybe we'll add it at some point
report back bugs!
try to cheat in videogames!
if it doesnt work, report an issue
if it works
give a thumbs up
🤭
wtf does that have to do with a keyboard
just kidding
That would be possible with the existing system and the custom building of effects if there were datapoints for if individual keys are actuated. Right now you can only effects on the basis if any keys are actuated
its a public beta
I see, thanks for taking time to answer. I appreciate your guys work!
Ok, i hope you guys will add it :) Would be cool for rhythm games
Any particular rhythm game(s) or just in general?

I was mostly thinking of osu! and osu! mania
We lost Key Depth lightbar indicator in Tachyon mode sadge
the way it was, tachyon was losing its benefit anyway. Now Tachyon works properly, but of course like rgb effects, you need to disable it to get dynamic lighting
Do we have the background service yet?
no
Hm, my 60HE+ wasn‘t supposed to suddenly stop responding as soon as I type any key after the update I guess? 😂
Definitely not, are you still having issues?
yup, had to get my 2 HE out to control my computer. after restore it did still not work correctly, then I restored with v4 wootility
I have the Wave RGB effect active, that also stopped completely, as well as the keyboard disconnecting from wootility when I typed that first key after update
After the first time was it the same trigger? as in, you replug, seems to work, then you press a key and it dies? or just outright not working
replugging seemed to fix, then I typed and it died again
Hmmm, I see. Is it okay to continue in DM to do deeper investigation with you so we can get this resolved?
Try changing the profile..
getting rid of effect layers worked for me
Hey, I have 2he, but can seem to find the Typing Speed Meter anywhere
This may be gimmicky but a words per minute gauge on the light bar could be neat, idk how possible it would be without downloading software, but maybe you could set a range of like 25-75 and the closer you are to the upper limit, the more the bar lights up from one side to the other
keystrokes per second were added with today's update.
Oh epic
Where is it? Cant find it under RGB Effects
it's for the lightbar
how would you imagine it for the regular keyboard? We can look into adding it as well
Oh, nvm I got confused sorry
Just a little update, we've released v2.10.1-beta.4 firmware update which fixes the issue that @drifting wagon was having. It came down to a bug when using the Random Colours setting on the Ripple or Trail effect causing a crash
I was trying to say changing mode bricked my 80he, but looks like it is fixed in beta4
and why Light Indicator - Progress bar effect is not compatible with Tachyon now? I was using it before. Sadge
Because before it was behaving as if Tachyon was completely disabled - drastically lowering your scan rate
This update communicates to you clearly how Tachyon mode and Light Indicator effects interact, whereas the previous versions kind of ignored the possibility of these two colluding entirely
how is bro dancing like tbat
60HE when updating firmware gives error when reconnecting but exiting out of updater everything seems to be fine its just when it tries to reconnect it doesnt seem to initally, I have noticed this 2 diffrent times now when updating it
I tried writing a more advanced description of the bug but the message instantly got deleted, not sure why.
seem like something wrong with the UI when updating firmware
I want to add to this, make it possible to also add layer to the effect? Like for example. the key G will trigger all of the first 5 of the LED bar, and the key H will only trigger the first bar.
And have em in a different color
It'll be cool for any rhythm game since 10 bar is enough for 1k all the way to 10k.
@last geode, does this build include the debounce changes from the latest debounce test build from months ago? And have you made any further progress on filtering out the bounce since we last communicated about it?
( #1187862357720977530 message )
Did you already push it ? Because i'm still on Beta.3, and it is not updating itself on my 80 HE
Ah nvm. On updates it appears: beta.3 but on my devices it is on v 2.10.1-beta.4
There's a difference between Wootility Version and Firmware Version, Beta 4 Firmware is out, Beta 4 Wootility is not
Yeah, that was my mistake, you are right.
Any idea how far away a beta for the switch selector is? That plus deadzone adjustability (one day maybe?) would be quite nice for folks who are using the more stable switches
what do you mean switch selector like you mean keyboard switches?
with diffrent magnetic strengths or smth?
Strange, not seeing anything particularly out of the ordinary in your error log. Did it just error while trying to find the keyboard in update mode in the update process? Have you been able to update okay now?
Yeah, lil bug got introduced 😅 We've got a fix ready to go for this one
I think that should be possible to do if we the general idea possible via adding individual key actuation as datapoints for the lightbar system 👌
The calibration system learns the characteristics of your switch and will make the deadzone as small as possible. So more stable switches will get a smaller deadzone (on the end of press).
Switch selector itself, hard to say right now, we're currently at the stage of collecting data on different switches so we can use that to give a more accurate output for them once the firmware knows about the switches being used via the switch selector
Ah that is very interesting - which explains why people measured the more stable switches and realized they automatically had less deadzone
Yea, for a more stable switch it is able to calibrate faster, but once we have the switch selector there and the firmware is able to make more assumptions about the switches, it'll be able to calibrate it even faster
Almost forgot to reply to you 😅. The debounce build is still separate, unfortunately not much progress has been made on it yet, but it is something I have as high priority.
I've got to make some adjustments to the test build system first, then I will release a new debounce build based on the latest beta firmware
Also, will the lower 0.1 rt setting that calder mentioned being available internally be pushed out anytime soon?
Currently my plan is to push that alongside the switch selector
Yeah so the update completed but keyboard didn’t reconnect so it showed a failed to connect screen but then it connects like right after idk it just looks weird ill record it next time there is a firmware update if the bug is still around then
Ok, thank you
just updated to this latest beta version. I have the 80HE and I had a profile with Tachyon mode enabled and I had the light indicator with the "key depth" effect and worked perfectly. Now it shows a message "this effect is disabled because its not compatible with Tachyon Mode". Is this a bug or an intended effect?
thats what I though, but since it worked in the last version I was curious. Thanks for the clarification 🙂
and what is that reason then? worked fine
you were losing the performance benefits of tachyon
well, some of them
we turn rgb effects off for a reason, sending color data to the leds interferes with scanning performance
i see. but, wouldn't it be better to put a warning instead of completely locking it then?
nah
that effect worked, but tachyon didnt work properly
Looks like the upgrade is actually a downgrade, now you can’t use light indicator functions while tachyon is on
Yeah some but not all
It was nice to have the choice
you don't need to doubt, we measured it.
uwu too big
there should be room for imporovement and optimizations for the LED bar, but at this point i think it would be a smarter idea to just go dual; MCU on the 80HE
only if the performance hit is that bad and for some reason cannot be improved on (hypothetically)
Hmm rather than dual mcu just a double core could be sufficient while being cheaper and much easier to program imo
as long as there is core management
that sounds like a pretty decent idea
giving that a thumbsup
There is usually, if they went with let’s say similar to current lineup stm32h747
(Though realistically something slightly less high end would still very much work and probably better)
Then there’s also options with equal core performance but probably needed
Though that’s all assuming changing the colors is an issue with processing power by itself which hmm considering how much more power this mcu has, might be power consumption or noise instead
And also having two mcus for one board would not be too fun though was done before tbf
I wish I knew the exact reason as I am curious whether there is a workaround with the current mcu, maybe one day
Tried to look back through lot of messages and can’t find the reason
i wonder if that means that future versions of the 60HE+ could also be true 8k with a dual mcu solution or like you said a dual core mcu?
60HE++
Sorry for the lil delay, updated test build is live now, new system properly reflects which exact firmware version it's based off of 😁
Hold up, noticed a bug with it where it will just install the v2.10.1-beta.4 build 😅
regression from beta.2 on linux
What are you using, a browser or the installable version?
"linux" refers to the linux package
You could have also meant to say on linux with a browser, hence i was asking
Looks like an issue with something related to electron i guess, my installable shows the same but the web shows it correctly.
Yeah this is due to electron having an older chromium version. Known issue.
I should also add that while I'm glad you guys added the possibility to customize the 10 LEDs separately, I'm personally still aching for a simple gradient effect so I didn't have to make the gradient manually :p
low priority I know, just putting it out there 
I sort of envision the gradient as an extra option on top of this layer, thoughts?
also, fixed the bug in your screenshot, should be in the next release whenever that ends up being :)
yeah I think I'd add it as an additional tab inside the "Solid" effect, much like the "multiple colors" button
something that in essence does this behind the scenes is what comes to mind
I'll bring it up internally
that was my first thought, to incorporate it into the 10 LED picker but I feel like it's inelegant and hacky
A separate tab/UI with just the 2 colors seems a little more purposeful
adding it as an option beside "Multiple Colors" with two color pickers would be the same thing but hidden yeah
and it generates the gradient into the lightbar preview and the board itself
UX is sort of a separate discussion, but the rough idea "2 colors -> 10 gradient" is enough?
the lightbar preview is actually live from the keyboard, if you use wootility in demo mode it doesn't work :p
I think so yeah, there's always the chance of going further with other algorithms/colorspaces and/or adjusting the "middle" point
question is when does it become too much
you can always get crazier with gradient editors lol (This is Artemis)
and yeah it's definitely too much hahaha
yeah something like that is too much by a long shot lmao
yeah i was just making a point :p
maybe just the two or even 3 colors and ability to adjust the intersection point
sort of like the bar at the top there and you can drag the midpoints around
/shrug but honestly just having the basic 2-color one with no additional adjustments would satisfy my personal need
while we're at it, anything else?
how's the progess with syncing one of light bar to any set key?
I wonder if it would be possible to have the KeyLock persistent and not reset itself after reboot or profile changing.
is there a way to save RGB settings/create our own presets?
without an entirely new profile
I share two bits of feedback from messing with the beta.
- I am attempting to use snappy tappy with two buttons (Q and W) while W is mapped to an analogue input. The result is odd looking, but in short it only allows W to act like W and not like analogue up
- Attempting to click enable gamepad in the online beta utility caused something catastrophic to happen to my wooting wherein it would not be detected by my computer, the browser, or anything else. Changing usb drive did not change this and there was not even a light to show anything was happening. Even another keyboard plugged in was not recognized. Thankfully a forced computer restart fixed it all but it was rather concerning!
Don't know for the latest update, but for me my whole 80HE stopped working... I had to uninstall the app and go back to the 'old' beta 3 version through my browser..
Could you send me your log file? When we've had errors like that pop-up, just a replug fixes it
also do you have any software that controls RGB software?
- Artemis RGB
- Asus Armoury Crate
- L-Connect3
- Open RGB
- Project Aurora
- Razer software
- Signal RGB
- Wallpaper Engine (1 Report)
- Motiv Mix (1 Report - Mic software)
Is there any logfile after uninstalling the Wootility app? @grave yoke I've got iCue installed, but never use it for controlling RGB and did turn off the service a long time ago
I've found "updater.log" in the appdata folder
There is an "Open error log" button in the bottom left when you're on the Settings tab. It'll take you to the folder with the log files
Hmm, too late then. Cause I already uninstalled it after finding out it was messing both my 80HE & my uWu. So I already switched 'back' to web based beta 3 and that works for now, don't want to crash it again. I did try the reconnect thing, even with an extra reboot. Didn't do anything. So uninstalled it, using the old version of web based which works for now.. thnx anyway. I'll wait on a new release to be sure 👍
There was a brief time where beta.4 was pushed to web but was displaying as beta.3, so there's a decent chance that you also were running beta.4 code when you switched to the web version. So I'm a bit confused as to why you only got an issue with the desktop version, there are very little differences between them
Does this new beta build finally have a full fix for the debounce issues that I've been experiencing ever since I first got my 2HE back in September of 2023?
You still need to be on the test build for now, when a firmware update includes the debounce changes, it will be made clear in the changelog





