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

6th
🤓 ☝️
😏😏😏

🤯

Not first, not 6th, but definitely best 
aha, the other day OpenRGB killed the lights on my keyboard xD
Friday release gang gang
Have you ever had those moments where one of your balls disappear
it will continue to, we didn't change how it works. just made it not kill wootility communication
aha ok xD
well i couldnt get the lights going again unless I unplugged the keyboard
so everything else is good now?
are you on latest firmware?
Wootility - beta.7
Firmware. Beta.6
- Old RGB-sdk from artemis rgb
the device should now keep a stable connection
i couldnt break it on my system with artemis 
could change wootility settings and everything while artemis was sending lighting updates
Same happened and then I had to replug the keyboard
latest firmware is beta 6
Wootility couldnt detect it without replugging
wootility is beta 7
Wootility might just be goated now, hopefully there won’t be any bugs.
🙏
having a slight issue where it doesn't show the "wooting restore"
Could you elaborate?
so still no 'wooting background service' right?
When you start the update process dose the keyboard turn off or turn on quickly with out preforming the update?
It turns fully off and I have to unplug and replug it in
My bad I was trying to get a photo to remember what it was saying
after stable
Same answer as last time, it'll be after stable v5.0
I had the same, replugging fixed it
I've tried that and different usb ports
I can keep trying tho
yea, can I ask how to stabilize jades? saw your comment in other thread.
"Also the end of press gets calibrated as you press it, so you should keep pressing the key quickly to full bottom out to make sure it gets calibrated properly"
so should I press keys deep enough everytime on booting? or can I check this calibration?
Did it work after only replugging in once?
Yes
When you start the update process, the keyboard should receive a command to restart and stay in Wooting Restore.
Then, the Wootility software will either:
- (Web) request to access the "Wooting Restore" device and start the update.
- (App) Start the update process
If the keyboard is not being detected, check how it appears in the system under "Bluetooth and devices." Also, if the keyboard is connected through a USB hub or KVM, try connecting it directly to the back of the computer.
@naive crater what keyboard model?
This look right?
The uhh full one with num pad
looks like it is not in "Wooting restore: mode
Does it matter if I'm using brave browser?
possibly
Brave locks down a lot of things that we use in Wootility
So you should try Chrome or the desktop version
Ah alright
Is it intentional that I don't see the continue anyway button when the window is smaller?
honestly doesn't even make sense to do this in V5 because I think everything does fit quite well
tried it on google chrome and microsoft edge and it just doesnt show up on the select device
yo profile import + export might be not working
bruh
yes, when it's so small that the ui would definitely break, we drop the continue anyway
Oh I notice the linux app uses x11, any plans to make this app uses wayland protocol for rendering in ?
There's a bunch of bugs in the UI which can be fixed which should let us relax it even more
it's an electron app, not sure how we would fix that
Oh I will test a command flags --enable-features=UseOzonePlatform --ozone-platform=wayland
Well it works
On left, without these flags and on the right with these flags.
what am i looking at exactly?
At upper left of window, the icon changes to indicate the window protocol being used
The X will be X11 and the W letter will be Wayland
The reason why Wayland is to take advantage of scaling for those with big monitors without being blurry due being under XWayland.
The source for the info is this blog : https://www.skerit.com/en/make-electron-applications-use-the-wayland-renderer
I mean, V5 definitely fits with only roughly 620px of height, but there's no "continue anyway" at that height, seems a bit weird
not if you try adding an advanced key 😭
Well, I do notice there's a keyboard at the top which doesn't always need to be there 😛
for my personal usage tho I don't care if the UI looks a bit weird because it's too small
at the very least always give the "continue anyway" option
the user has been warned at that point
after this 5.0.0 beta .7 update my 2HE wont turn on anymore
I tried replugging and troubleshoot but both without success
I'm on latest firmware
v2.10.1-beta.5
analog SDK 0.8.0
we can reproduce, and are fixing this.
thank you
AVR or ARM?
Avr*
thanks
Been waiting for this for SO long finally can use signalrgb
wait i just clocked it
is the reason why import and export are fked the same reason that caused this
yes i had the same, you need to restore it via the old wootility or it wont come back online. your profiles will be gone tho
owh thanks for this reply , I'll try 🙂
can i safe my profiles with share code first?
owh damn, alright, I'll lyk 👌
skill issue, we're fixing 😄
Firmware update 2.10.1-beta.7 should be available now
Friday release moment
last time that happen, a company died
Read about the changes and improvements in Wootility version 5.0.0-beta.8.
still doesn't work for me sadly. it says: no connected device.. even though I've unplugged and replugged it back in 10+ times sadly. I have Back-Up Keyboards which is what I'm typing on right now.
I have the AVR Wooting 2 HE for reference
hey i think you need to restore it with wootility4 at least that worked for me
then update to newest beta
let me try that thank you!! 🙂
thats the v4
under settings -> trouble shooting -> two he
then take it from there
it worked thank you so much 🙂
i have the same issue
you don't need to restore with v4 first, you can just restore with v5 using Help -> Troubleshoot on the left side
Hi
My light indicator not working after update :(
I reset the keyboard and it started working again
Hi guys I accidentally unplug the cable while updating. After I plug it back Wootility could not find the keyboard and "E&R" lit up on my keyboard. How should I handle it in this case? Thanks!
If you run into any complicated issues or your Wooting keyboard is not responding, one of the first things you can give a shot is restoring your keyboard in the Wootility.
00:00 hey
00:15 Reset Wooting keyboard settings
00:42 Restore Wooting keyboard
➤ Follow Wooting online: https://links.wooting.io/?id=VY...
It solves the problem! Thank you very much!
my board exploded after installing this
Same 😔
Profile import/export is not currently working on the desktop client, but works on web app. The profile code here was generated a moment before on the web app.
This is on v5 beta 8
In case the error lines are needed, i get the same error on the beta.8 client.
waiting room btw
https://wooting.io/wootility/changelogs/5.0.0-beta.9
New release
Fixes profile sharing on desktop @silver furnace @twin glade
Read about the changes and improvements in Wootility version 5.0.0-beta.9.
Still having issues?
ill try later
Alright, lemme know exactly what happens and which model you have
lol
Thanks, it works now.
Are you getting them btw?
ehh, maybe not, lit no money after buying piano
One day 
Looks like import/export is working again, thank you!
in the latest version when you close the dropdown menu the icons are not centered
after update driver keyboard wooting60he+ found problem keyboard not working and disconnected. im Resetting the PC still doesn't fix it. how to fixed pls 😭
What exactly is not working? Like does the keyboard itself work, but cannot connect to Wootility? Does the keyboard not work at all? Have you checked to see if it shows up as a USB device? and if it shows up as "Wooting Restore" have you don't a restore via Help -> Troubleshoot?
same for me, its connects disconnects and just repeats making me unable to use the software both web based and through the desktop app...
Could you send a screenshot?
Do you have any RGB apps running like Signal RGB?
Have you replugged your keyboard?
i will try right now
yes finally lol
not sure why that happened on your guys end but alr 😭
thanks 💪
Let me know if you encounter it again, maybe was just a random one off
will do 👌
https://discord.com/channels/167181566978555904/1339232574593044490 AoE spread on big keys (bug?)
Not related to the v5 beta
Was AoE always this uneven?
My 2HE is on 2.9.1 and Wootility v4.7.3 and mine is similar
Ah, alright.
is this new beta safe for the 2HE AVR?
Yes
ok ty
Read about the changes and improvements in Wootility version 5.0.0-beta.10.
first
We've got a new little test build out for people who are still encountering issues when using Wootility + RGB apps

looks like it's more small-ish fixes and stuff, do you have any insight into when we might get some more feature-pack style updates
After v5.0 hits stable :)
you could've just said never
it'll be 80he 1 year aniversary by then
I think 80he's drinking age at that point
what's preventing it being bumped into a stable branch?
This new beta update is intended to be the last™️ beta release (i.e. release candidate). Only thing it doesn't have is migration stuff we're building to get people off of v5.wootility.io and beta.wootility.io (if they so wish) onto wootility.io and such
ooh, fancy! I imagine it wouldn't be impossibly hard to just sort of grab all the profiles they have, zip em up real tight in a .wootpack file (actually a .zip in disguise) and then import that into V5 via handydandy popup
getting users to click 5 buttons in order without messing up is very hard
sadly :(
ah so you're rather going the "Migrate me" button -approach which'll just do all of this automagically
still waiting for switch selector
I'll have to say -- the auto-updater is a really nice feature -- if it's not in the package manager it's very inconvenient to update stuff on linux but this one works a treat with the self-updater
in the past I've had issues with self-updating .appimages just create a new version instead of overwriting the old one, I'm curious if you did something to specifically not have this behaviour or is this my appimage manager just getting better over the years 
Make sure to backup every profile, the backlash will be big in case something went's wrong because of a small bug
I've already seen all of this happen 
We haven't really done anything specific for it, we're just using electron-builder + electron-updater and it just takes care of all that for us thankfully 😅
I found a bug: this thread wasn't edited to be named beta.10 feedback
Wootility v5.0.0-beta.10 Feedback
Inconsistent content width in Keyboard configuration menues(?):
Actuation Point > Actuation Point section:
The submenu doesnt seem to follow the standard "full content box width" (which I assume is the width of the Profile header at the top of the screenshot). As it seems to differ from the other sub menus. For example "rapid trigger", "quick settings", "advanced keys" etc sections. Do not really understand if this is intentional by design or just some flex box miss. But just in case I sent it here :D
(Copied from another thread as this is more relevant thread for this type of feedback)
Random Questions regarding "Unused space" in content containers in keyboard configuration:
Just a random question out of interest regarding design and usage of "dead space"/"empty space" I have noticed some places in Wootility where its just a "void" of nothing where no text or action button is shown.
Actuation Point > Visual Feedback:
Is it meant to be this much dead space? I noticed its matching the size and layout of the neighboring box containing the "set actuation point settings", but its mostly empty other than the indicator. Also personally I find the single "press depth indicator" looking a bit funny being aligned left and that small 😂
Advanced Keys > Active Advanced Keys : Similiar "empty space"
Is this by design or is more stuff going to get added here? Just asking out of interest, was mostly a bit surprised by the big void of gray box when clicking through the settings 😂
build 5.0.0-beta.10 (I do also assume to some regard that its not fully finsihed, as it is a beta after all ofc, so stuff can change and be moved around) (1080p screen)
(Copied from another thread as this is more relevant thread for this type of feedback)
Wouldn’t it be better if we can first confirm what needs updates before going along with the update?
@heady wagon
Are you confusing the desktop app updates and web updates?
On desktop we're able to tell you what the new version is and link you to the changelog, we don't have the same info on web, so it just gives a general pop-up and gives a general link to changelogs
Gamepad Configuration:
Gamepad > Gamepad:
The visible margin between the keyboard viewer and the section subheader with its corresponding actions feesl squished. The spacing seems to differ a noticable amount from the other configuration views in 1080p in "maximized" mode. When comparing it with the other views its looking and behaving like the keyboard preview is bigger than the other "full size previews" > takes up more space > reduces the space between the sub section and the preview section when the position of the subsections seems to be constant related to a ration of the window size? I saw that it has no text like the others, and that could affect the spacing, but the spacing still feels abit squished. Idk if this is just me ranting about random spacings at this point. Buy hey thought I would let you know :D
Just want to add, big shoutout to the wootility team on the design and functionality of v5. It looks clean, easy to use and genuinly a pleasent experience. Keep it up :D
Hey i notice ever since the update the rapid trigger values round upwards or downwards?
Yeah, that bug got introduced accidentally 😅. Follow the number next to the slider for now until we get the fix released 😁
Updated to newest build
Can’t even connect to my keyboard now
Says it’s timed out
Communication with device timed out
Reset it fixed issue somewhat
@lofty zodiac do you use RGB apps like SignalRGB or Artemis?
Anyone else’s can’t save there settings with the new update or use rapid trigger
Same shit is happening to me except it’s ARM what do I do
I need a fix updated my keyboard and now I can’t save settings or use rapid trigger reset keyboard twice but it said that my keyboard was timed out
I did it’s still says the same thing and when I close it and open it back up it’s not on
screenshot rapid trigger section
Bro I can’t I have to go to bed have work tomorrow morning but I turn it on then I hit saved and try to exit out says the same and thing
Even tried going to the profile and saving changes but still doesn’t work
@hollow estuary are you on the v2.10.1 firmware?
The pop-up saying about unsaved profiles could be triggering incorrectly, which wouldn't necessarily mean that it hasn't correctly saved
In your video you get the clear saved, which should mean it's all on there
need a feature where we can rename devices, just put it in this 3-dot menu here 

What's the significance of it for you when seemingly you don't have duplicate models? When we discussed this feature internally last, we were thinking it was mainly helpful for those with multiple of the same model, so it's hard to differentiate due to the same name
I would say it’s because it looks nice, adds a bit of personal costumizing to the keyboard. Like the rgb. And the fact it’s nice to have when you have multiple of the same model and don’t want to memorize the serial number
Technically it’s not strictly needed, but neither is RGB, nor rebindable key. I think it all comes down the user feels like they have even more control over keyboard in terms of behaviour and “representation” :)
Strengthens the emotional attachment
for me in particular, there's no good reason except for "I thought it would be fun", but for the people who have multiple it would actually be useful
I have multiple duplicate keyboards. Would indeed be nice
Thanks for the input all!
