Accessibility Feature Request: Conversation Focus Mode for Ray-Ban Meta Display Glasses
Hi everyone! I’m a Ray-Ban Meta display glasses user who is hard of hearing and wears hearing aids daily. I’d love to see a conversation focus mode added that prioritizes voices directly in front of the wearer and reduces background noise. In busy environments, this would make a big difference for hearing-aid users and others who rely on clearer speech in real time. If this type of accessibility feature is ever developed, I would absolutely love the ability to have it added to my glasses and would be happy to provide feedback or participate in any beta or user-testing opportunities. I’ve also submitted this through support channels, but wanted to share here in case the team is gathering feedback.
How to disable controller's auto-sleep?
Hello, I'm working on a project (PCVR) that continually reads coordinates from Quest Pro controllers (integrated cameras), all works fine in my side. My issue is that the controller automatically turns off (auto-sleep) after few minute if no movements detected, so, reading the controller's coordinates breaks. How to disable controller's auto-sleep? Thank you.
MQDH Input Forwarding: Gaze Click not working
Reposting an archived discussion as it seems to be still unresolved: MQDH Input Forwarding: Gaze Click not working | Meta Community Forums - 1283192 I'm trying to get the Gaze Click input from my mouse click to work to be able to interact with the 3D UI inside the quest. I have disabled hand tracking and disconnected the controllers as suggested but still unable to get the mouse click to go through. The use case for me is to be able to remotely control the quest 3 from my PC without having to use the headset nor the touch controllers for testing developed apps.Controllers suddenly flipped on the Z-axis for no apparent reason, and I have no idea why
I’m making an action game, and a few days ago Unity suddenly started throwing errors and wouldn’t open for no apparent reason. After I deleted Meta’s SDK, Unity launched normally again, and reinstalling the SDK didn’t cause any further issues. However, yesterday I noticed that both controllers in my game had suddenly flipped 180 degrees on the Z-axis (see Image 1). This only happens during actual device testing — it does not happen inside Unity (see Image 2). I tried flipping the controllers’ Z-axis by 180 degrees in Unity to cancel out the issue, but it had no effect. I haven’t touched any packages in the past month, and everything was still normal about a week ago. Currently, my Meta SDK version is 81.0.0, OpenXR Plugin version is 1.15.1, and Unity OpenXR Meta version is 2.2.0.Unable to use Meta XR Simulator more than 3 minutes
Hi, I’m trying to test the Meta XR Simulator in order to develop a VR experience in Unity. The Unity package requires the headset to remain connected to my PC so that I can test VR without wearing the headset, and so the controllers can be linked to the simulator (I’m not sure why they can’t be paired via Bluetooth like Switch Joy-Cons when developing a Switch game in Unity). The workflow is essentially the same as testing in Play Mode with the headset on — but why not I guess. On the headset, the XrSimDataForwardingServer.apk is running, and I’ve covered the proximity sensor with black tape to prevent it from entering sleep mode. With this setup, I’m able to use the controllers for about 2–3 minutes, but then the headset still goes to sleep. Because we are a school, we use a third-party MDM to manage all our headsets, so this device is in Shared Mode. As a result, I get the “Continue the session?” popup. Even when I press the button to continue, it simply loops back to the same popup indefinitely. In our MDM, the headset is configured to sleep after one hour, but since the device detects no movement (even though I’m actively using the controllers in Play Mode with the Meta XR Simulator), it still enters sleep mode. How can I resolve this in order to develop my VR experience more efficiently? Thank you in advance for your help.
