Truce this is absolutely better but still WAY off from where it needs to be.

The keyboard should be exactly where my POV is facing, no matter if I'm laying down or standing up. I'm sure this look normal to people when they are standing up but when they are laying down I have to try to find my keyboard or guess where it is to move it to a place where I can actually see it. This means I'm going to have to keep trying to search for it EVERY SINGLE TIME I need to re-open the textbox which is not good for someone who is disabled, like me.

Another thing is that because they are separated that's two things I need to keep track of. Why not add a button that merges the two UI together? That way I can save that I want my input to be tracked to my keyboard and just drag the WHOLE thing if I need to whenever.

The other issue is that the keyboard/input field is ONLY draggable from the title of the UI box rather than the ENTIRE UI box which means I have to be very accurate when moving the box. Again, this is awful for people who are disabled if I:

I included a video of me struggling with the chatbox. Though it IS much more usable now, it's still WAY off than where it needs to be vs the old keyboard that worked just fine.

TL;DR:

Works better, still off. Add a button that merges the two UI's (input and keyboard) into one. Make entire thing draggable. Appear from POV facing rather than hips it seems? Save that location so a user doesn't have to keep grabbing TWO UIs to try to see what they are typing when they can't see the UI at all when laying down. An option for the old keyboard would much rather be preferred. Needs more accessibility in mind when developing this new UI.

Livvydoodlez : the keyboard/input field is ONLY draggable from the title of the UI box rather than the ENTIRE UI box

Can you provide some details of your setup? Both the keyboard and the input box should be grabbable regardless of where your cursor is hitting it on [1916].

[1916] also adds a keyboard button to the modal that reset the keyboard to the default position (which is docked with the input field.) After clicking that, it should be following the modal when you drag it, until you drag the keyboard far enough away from it to separate them again. They're effectively connected at that point, but maybe it's not immediately clear that's how it works. (Or maybe there's some other variable in your setup/situation that's not accounted for already?)

We have a few more fixes in the pipeline, but it seems like the main concerns you listed are already addressed to some degree?

Truce

["Can you provide some details of your setup?"]:

Version 1916

I use two index controllers with a Quest Pro headset, I've been struggling to be able to move the input box and the keyboard when trying to grab anywhere EXCEPT from the title of the input box. I've noticed people in other threads complain that they cannot grab from the keys? Which is primarily where the biggest space is to grab the UI box to move it.

["[1916] also adds a keyboard button to the modal that reset the keyboard to the default position"]:

I DID realize that clicking the keyboard button did snap it to the input box when trying to use the new UI to find out what that button did. However, clicking the button also does not help because it's still two UI models that have to be micro managed each time you use the keyboard.

For someone like me who is disabled and has to lay down, I CANNOT see the Input box OR the keyboard, even if I use the keyboard button to snap it together, so when I try to move the box that I cannot see above me to where I CAN see it, the UIs will become disconnected because often times I'll grab the keyboard rather than the input box.

This happens EVERYTIME the Keyboard UI closes, which means this needs to be moved when I cannot see it EVERY TIME I try to have a conversation. Every new sentence needs a UI re-placement to be able to see & type. This process alone makes communicating unbearable.

This is why I think that the keyboard and input field should ALWAYS be in the center of your POV (or last saved location) that way they do not have to keep being moved EACH TIME you access the keyboard, because it becomes INCREDIBLY annoying when you're trying to have a conversation with someone.

["main concerns you listed are already addressed to some degree?"]:

I HIGHLY recommend a new button NEXT to that keyboard button that merges the two UI's into ONE UI and saved that way so the user can easily move and see what they are typing. And then POV snapping that one UI on top. Two UI's make this way more difficult than it needs to be and is not accessibility friendly when they both have to be managed. Even with the keyboard snapping button.

If this is added, it lets you have both features of having a seperated input box and keyboard, and a button that keeps that both together in one UI as an option that can toggled on and off whenever they wish.

Most of the OTHER concerns have been addressed yes. As I said earlier this keyboard is more "usable", and I appreciate you trying to fix and modernize the UI, but I will still say the old keyboard is still far more superior. The only issue the old keyboard had was that the input field was too big and too close to the "SEND" button making backspacing really hard to fix mistakes. The old keyboard UI WITH the input field merged in was easy to access, nice and big, remembered my POV or last placement settings, and was easy to manage. The new one is STILL difficult but more "usable". Still really big accessibility issues, and I'm sorry but the two UI field is a huge factor that makes this really difficult for disabled users.

WHY did this go live?????