Starting at Rift 1 it’s silly that Quest in 2025 still lack basic user controls for core functions
People have been asking Meta for years to add a simple toggle to disable the proximity sensor directly on the headset. Instead, the only way is through ADB or SideQuest, which makes zero sense for a mainstream device. A native setting should exist by now. Meta also removed the option to disable the “double tap to glance” overlay. It’s now permanently on with no way to turn it off. In fast movement or dance sessions, both problems annoy constantly. Quick head movement or leaning forward trips the proximity sensor, and accidental taps or scratches activate room view. It breaks immersion every time. It honestly feels like the product designers don’t actually use the headset actively. Having to open a developer account just to disable Guardian proves it. If there are legal concerns, add warnings. Don’t take away core user control! Small note while on on the train of annoying issues about Pro: -thanks for fixing the odd rendering issue on Pro headset where a diagonal line was breaking the image on the headset after updating to v80 and up its gone BUT when will your microphones ever be flawless? It's not as bad as the Rift S, but occasional mic dying turning robotic or giving a high pitch scream still appears once every few months or weeks does not happen on my Quest 3, Rift cv1, but we all know the famous Rift s mic going robot mode! (all headsets now on newest OS at the time of writing this)
Add extra thermal cameras to Quest 3
Hello everyone! I would like to know if it is possible to add extra cameras to the Quest 3 headset. The idea is to add two small thermal cameras to the front of the headset, to obtain a passthrough with night vision. It would be an extra layer of information that helps RGB cameras see in complete darkness. Initially I think of gluing the thermal cameras to the front of the viewfinder, and connecting them by cable to a cell phone, where it obtains electrical power and image processing. Then that image should go from the cell phone to the Quest 3 wirelessly. I was analyzing the documentation, and I think this could be done through the Passthrough.API, Android Camera2.API, your opinion on this would be very useful. I am a person with a visual condition called retinitis pigmentosa, which causes night blindness and decreased peripheral visual field. Therefore, it would be miraculous for me (and for many others), to be able to have night vision, but also assistance for low vision, such as contouring people, objects, steps, obstacles and all kinds of dangers. Thank you very much for your time. And thank you very much to META for giving us this wonderful technology that improves our lives in many ways. And also for opening the passthrough code!! Julian Almendra
Meta Quest white color saturation with OpenXR
Hello I am trying to build a VR application for Meta Quest 2/3 headset with Unity 2022.3.7f1 using OpenXR. However, when I build a pure white object, or whatever. The color appearing inside the build won't be pure white, it is something around RGB=(243,255,255). I tried many things such as URP Settings, OVROverlay, switching to HDR, environment light, texture compression to None, Graphics API to Vulkan, Color Gamut to Display-P3, OVRManager's Color Gamut to Unknown, Unmanged,etc... I can't think anything else. There is no light baking in my scene, nothing else than a pure white object. Can someone provide me some ways to prevent that please ? Here are my Unity settings :
Rename Headset on Meta Horizon
I have 3 headsets, 2 Meta Quest 3S's and 1 Meta Quest 3. I would like to change the device nicknames on the Meta Horizon app so I can differentiate between the 2 Meta 3S's without having to remember which serial # belongs to which one. Is there a way to do this on the consumer side? Only posts I found about it were 1 year or older and they only mentioned it being capable on the Developer side of things.
