My Quest Pro Nightmare: Meta Support Canceled My RMA After Two Months of Silence
Right before Christmas, I treated myself to a new Quest Pro. When the headset arrived, I was over the moon. I’ve been with Meta since the Oculus days—starting back with the Rift S—so I’d been waiting a long time for this upgrade. But my happiness was short-lived. On the very first night, I discovered that the Menu button on the left controller wasn't working. I looked up some troubleshooting guides which suggested unpairing and re-pairing the controller. That was the final nail in the coffin; the controller died completely and refused to pair back up. The next day, I contacted Meta Support. They replied quickly and authorized an RMA (Return Merchandise Authorization) for a replacement. On December 29, 2025, the return was officially approved, and the process began. Then... silence. Nothing for half a month. I started messaging them almost daily just to find out what was going on. Eventually, the Meta Support bots started sending me the exact same canned responses: how sorry they are, how they don't have any specifics, but how helping me is their "life's mission," and so on. At one point, a human named Brad replied. (Hi Brad, love you.) The wording of his email was different, which gave me a glimmer of hope that my problem might actually be solved. Well, hope is still barely alive, but the situation has become even more inexplicable. Today, February 27, 2026, I received an email from Meta stating that my return has been canceled for the reason: "Other." I contacted support immediately, and once again, I was showered with empty promises. They told me they would get back to me as soon as they "clarified the information regarding the cancellation." This is pure madness. If anyone has had a similar experience, please share how you resolved it. I am as desperate as a person can possibly be at this point...😫
Enabling Facial Expressions on Networked Avatars
Hi all! I'm looking to enable face tracking for a multiplayer game I'm currently developing where each avatar is network instantiated. The current documentation explains how to set it up for local avatars. Is there any documentation available for networked instantiated avatars?
Meta Quest Pro Eye Tracking Enabling Issue
I am working on an application that retrieves the eye position of a user by using collision of a surface with the OVRGazeRay. I was able to make it work and could retrieve the data points over the meta link to my computer. At some point I updated my Quest Pro and from then on it stopped working. The Movement SDK tells me that the eye tracking is enabled and working In addition to that the Meta XR project setup tool also tells me that there are no issues in my project. I have enabled eye tracking everywhere it needs to be and I did first send a build of the project to my quest to be able to enable eye tracking for the application in the meta quest pro and have verified that from then on it is enabled in the settings when using the meta link. In addition to the eye tracking using FixedUpdate (I doubled the frequency of the update) I also have an additional C# script taking controls from the controllers and interacting with a TextMeshProUGUI which is not used for collision detection (the two are hence separate). Everything seems to work just fine but somehow since the update I cannot retrieve the data anymore. Hence I asked the API directly if the eye tracking is enabled using (OVRPlugin.eyeTrackingEnabled) and this tells me that it is not enabled. This results from the following code if (OVRManager.isHmdPresent) { OVRPlugin.SystemHeadset headset = OVRPlugin.GetSystemHeadsetType(); UnityEngine.Debug.Log("Headset type: " + headset); bool eyeTrackingSupported = OVRPlugin.eyeTrackingSupported; bool eyeTrackingEnabled = OVRPlugin.eyeTrackingEnabled; UnityEngine.Debug.Log("Eye Tracking Supported: " + eyeTrackingSupported); UnityEngine.Debug.Log("Eye Tracking Enabled: " + eyeTrackingEnabled); if (eyeTrackingSupported && eyeTrackingEnabled) { UnityEngine.Debug.Log("Eye tracking is supported and enabled."); } else if(eyeTrackingSupported) { UnityEngine.Debug.LogWarning("Eye tracking is not enabled."); } else if (eyeTrackingEnabled) { UnityEngine.Debug.LogWarning("Eye tracking is not supported"); } else { UnityEngine.Debug.LogWarning("Eye tracking is not supported and not enabled."); } } Things I have already checked multiple times: - Developer Mode is enabled on the Meta App on my phone for the Meta Quest Pro - I did factory reset the meta quest pro multiple times - I am using 2022.3.35f1 LTS Unity which is compatible last time I checked with the movement sdk and the meta sdk. - I am using up-to-date versions on all my packages - Before the update I was able to retrieve the eye tracking data and I have verified that it matches the exact eye pattern. I also know that no collision is occuring as the eye gaze ray would change from white to red were it to collide with something. I have been trying to figure this out for weeks now and I really do not know what the problem is being caused by. I hope someone can help me. Thanks in advance.
