Forum Discussion
Mixed Reality Link: Controllers are not working, I can only watch the screen
Is this expected behavior in V72 and Mixed Reality Link App from Windows Store that my Quest 3s Controllers cannot click and interact in my Windows 11 or Windows 365 Cloud PC?
Hello! Thanks for the feedback. This is the expected behavior currently. Meta Quest controller as input for mouse/keyboard interactions with the connected PC is not supported. Is there a specific use case you all are aiming for, or general usage?
5 Replies
Having the same issue here, I thought it was broken at first but it seems that this is the actual intended behavior.
Granted this is a beta but it's still extremely bizarre that they haven't implemented this feature yet, because in all the alternatives, including the older Oculus Quest Link app that this is meant to replace, you can control your PC through the Quest by using the controllers and a touch keyboard or connected BT keyboard. It's extremely limiting because this means the only way to use your PC with the Quest is to stand right next to it and use the built-in keyboard/mouse. That limits it from a "walk around and use your desktop anywhere in the house" type of app down to a "oh you can just use your PC the normal way slllliiiiightly easier without removing the headset now." Nice I guess? But not all that useful.
Hello! Thanks for the feedback. This is the expected behavior currently. Meta Quest controller as input for mouse/keyboard interactions with the connected PC is not supported. Is there a specific use case you all are aiming for, or general usage?
Interesting. So I have the same issue. however, I have due remote in to the same system in order to get my mouse and keyboard to somewhat work while using 'Integrated on to Q3' Not talking about the windows app in the Q3. Anyways so I've tried this on two systems. One is VM/remote over LAN and the other is a workstation with above preforming specs. So with the RemoteVM i use proxmox and merged the vga display with the physical dummy HTMI port plug onto the GPU and i can both access remotely with the Q3 and access the merged display with the vnc output through proxmox and i can use my mouse and keyboard from the other system vncing into the vm. So this concept works so far but not very ideal for me. Now for the workstation, i can just put on my head set in front of my multi monitor config and access the desktop as intended, yet... I would have to use the mouse and keyboard already connected to my workstation in order to get anything to move or interact with my Q3 remote into my workstation desktop experience. I'm not sure but is this the original idea behind this integrated app inside the Q3? Or am I supposed to be able to use a Bluetooth mouse and keyboard on the headset 'Q3'? I've tried that with Bluetooth keyboard and mouse and on both systems i still cant control the desktop on ether system. I have to do what i had mentioned above by having equipment like mouse and keyboard connected directly or vnc'ed into the host system in order to interact with it. Is this wrong or is this what has been intended for use? Yes. i actually went that far on my own to figure out how to get some control over the Q3 Integrated Remote Desktop interface. The Windows App works ok but can't seem to properly Forword an Xbox controller through blue tooth on the q3. Only way anything seems to work for gaming wise is steam in desktop mode vr mode. But for windows, just has those bugs or if this intended will there be an update to correct this for added controls like bluetooth mouse and keyboard in addition to the Q3 Hand controllers?
Same issue. It makes no sense to move through apartments with both bluetooth keyboard and mouse just to do simple operations in remote desktop window, when I have controllers and hands with me.Seems like functionality is missing for now. Microsoft, please 🙏
Same problem for me. Is this not working because it hasn't been implemented, or is it because my user account on Windows 11 is a Standard User and not an Administrator? I ask this because I have this problem with AirLink when using it to get a virtual PC desktop -- using AirLink to access a PC that's signed in as a Standard User doesn't pass the controllers through to the desktop (as mouse activity), but if you upgrade the account to Administrator, AirLink passes the Quest's controllers to the PC as mouse operations. I'm wondering if it's the same problem here, or they just haven't at all implemented any form of PC control via the headset, leaving us needing to use the PC's mouse and keyboard for now.
