[1932] Keyboard bug animation resetting.
complete
Livvydoodlez
Okay so now the keyboard has managed to somehow get EVEN worse.
I'm on beta 1932, and the animations of the keyboard was added to this god awful thing. Why? Idk. I guess chat GPT wanted to throw flare in the UI.
None the less
*
THE BUG:
*Pressing [ENTER] or [RIGHT SHIFT] will RESET the animation of the keyboard. Even while you're actively typing on it. This means the entire UI gets reset and you have to wait for the animation to finish to start typing again.
However, because the animation ALSO reset, it will also NOT capitalize anything because the animation has reset the action of the shift key being pressed.
~~~~~~~~~~~~~~~~~~~~~~~~
Extra Feedback:
FOR THE LOVE OF GOD JUST REVERT THIS KEYBOARD UPDATE ALREADY. IT'S CLEARLY NOT WORKING. THERE ARE MORE COMPLAINTS ABOUT THIS KEYBOARD BEING BROKEN THAN THERE IS TRYING TO GET IT FIXED.
IF YOU AREN'T GOING TO FIX THE ACCESSIBILITY ISSUES IT MAJORLY HAS, AND IT'S JUST GOING TO CONTINUE BEING GARBAGE TO USE, AN AWFUL EXPERIENCE, AND MAKING LIFE HARDER FOR PEOPLE WHO TYPE, THEN JUST UNDO IT!
CLEARLY IT'S NOT WORKING!!!
GO BACK TO THE OLD KEYBOARD DESIGN FOR THE LOVE OF GOD.
MY ACCESSIBILITY CONCERNS STILL HAVEN'T BEEN ADDRESSED BUT IT'S BEING RUSHED OUT TO LIVE SO OTHERS HAVE TO DEAL WITH THE SAME PROBLEMS.
I'VE LITERALLY UNSUBSCRIBED FROM VRC+ AND WILL NOT RESUB AGAIN UNTIL THIS KEYBOARD IS EITHER REVERTED OR FULLY FIXED IMMEDIATELY.
THIS SHOULD BE PRIORITY #1. YOU CREATED A PROBLEM TO A SOLUTION THAT NEVER NEEDED TO BE SOLVING!
THE OLD KEYBOARD WAS PERFECT. IT WORKED FINE. THE ONLY ISSUE WAS SPACING IN THE INPUT FIELD.
NOW WE HAVE TWO UI FIELDS TO JUGGLE AROUND, ANIMATIONS THAT BREAK THE KEYBOARD BECAUSE WE WANTED TO BE FANCY INSTEAD OF FIXING THE GOD DAMN CORE ACCESSIBILITY ISSUES THAT CAUSE DISABLED PEOPLE, AND PEOPLE WHO USE THE KEYBOARD IN GENERAL MASSIVE STRUGGLES
GET RID OF THIS KEYBOARD!!!!!!
STILL REMAINING CONCERN ISSUES HERE:
Log In
_
_tau_
updated the status to
complete
The bug is fixed on live, and will soon be fixed on beta. Closing as Complete, since it's on the live Feature Request board, not open-beta bugs.
Also, idk, drink some tea and take a deep breath. We are still working on the keyboard and will improve it. We will, however, not revert it.
Livvydoodlez
_tau_
Yeah, kinda hard to just "deal with it" when, like I said, I'm disabled. I have to lay down in VRC to play 90% of the time. It's the ONLY way I can get around and socialize because I'm unable to do so IRL due to my disability, and when I can ONLY communicate via typing, this is not the way I wanna be interacting with VRChat every single day from now on.
The old keyboard was never an issue. It worked fine. The new systems could of been added with the old UI. This did not need to change. And IF you proceed to NOT revert the keyboard and to go down this path of reinviting the wheel to fix a problem that didn't need fixing, then the LEAST that should of been done was address major accessibility issues BEFORE pushing it live.
Instead, A LOT of people HATE the new UI with a passion and dislike it. Why? Because it was rushed out. These things take time to adapting to, and NO one is going to adapt if it's being forced out and none of the major core issues are fixed.
If the accessibility issues are NOT being fixed and are NOT being added before being pushed live, then the LEAST that should of been done is adding a legacy toggle for users, like me, to STILL be able to interact with our friends without suffering with the UI. It's already bad enough trying to stay in VR without issues. Now all those issues are multiplied because of this new keyboard system that fails to work as good as the old one.
I've started getting in VRChat less and have a hard time seeing friends anymore because I'm literally fighting with this UI every single day just to have a conversation with a person. No amount of "sipping tea and taking a deep breath' is going to fix that, and now because it's live, I cannot even opt out of the beta to wait it out for these issues to be fixed, IF they even get fixed.
_
_tau_
Livvydoodlez I wasn't saying "deal with it", I was saying typing a page of caps lock doesn't help your case. Most if not all of the cannys you link have been addressed, even during the beta phase: You can now dock the keyboard easily, you can lock it so it moves with the field again and is easily grabbable, you can turn on "Responsive Menu" in the QM Settings to always place it in eyeline, and the latest beta even improves upon it further by allowing easy use with both laser pointers.
If there are issues remaining, please open them in a new canny, and lay out objectively what you think should be changed.
Livvydoodlez
_tau_
i have done so here in the most constructive way possible:
WubTheCaptain
The open-beta is for testing, it's opt-in. If you prefer stable builds, try the default live branch (currently build
1921
). This frustration seems to be self-inflicted.Livvydoodlez
WubTheCaptain its no longer "opt-in" if the beta issues have been pushed to live.
WubTheCaptain