so im pretty scared right now.
after having this headset for about a year now, one day i was playing vr just fine no face tracking issues then the next day it does this…
can only half smile and eyes wont track just jitter around. tried a factory reset and caibrating but nothing works. please help i dont want this to be the end of my quest pro.
So something strange has been happening for a bit I have a dedicated router TP-Link AXE5400
set up with a 6g signal and when I turn in my headset it shows no connection and can take a few minutes or more then suddenly connects. I’ve tested it with my quest 3 and it connects instantly. I’ve tried restarting the pro but the same continues to happen. Any ideas would help thank you
Hey everyone, for about the past month, I noticed that my performance in virtual desktop dropped significantly out of nowhere. I began to gain intermittent latency spikes that even virtual desktop claims is > 400ms. I noticed that sometimes if I sat on my bed, or even got down low to my floor, my latency would go absolutely haywire, if I stood relatively close to my desk setup or even just sat in my chair or even simply faced a certain direction at a certain angle, it all spikes my latency for a second, sometimes a few seconds, or even 30 seconds. This has obviously frustrated the hell out of me, and I can't pin point what Meta has possibly done or if there's any workaround around it.
This isn't even a virtual desktop exclusive either, the general network performance on my quest pro is actual shit compared to my other devices, I hardly get any higher than 60mbps on multiple internet speed tests despite the fact I have fiber internet, the various other devices I tested easily get over 300
I noticed that this is infact a quest pro specific issue, I have tried my quest 3 and quest 2 in the same exact room, under the same exact conditions, and everything is perfectly perfect with absolutely zero issues whatsoever. Researching this issue was also extremely frustrating, as it seems that absolutely nobody else has this issue as of recent. Yes I saw the issues people were having back in like v77 but the general consensus was that the issue was since fixed? Yes, I already tried factory resetting, that did absolutely nothing. I tried Meta's "official" update sideloading tool thingamajig, I don't even think it updated me at all or changed anything as im pretty sure im on the latest version (51412760034600340). Either way, that ultimately didn't do anything either. Yes I tried checking the latency and even running the internet speed test when I was in direct line of sight of my router, not even 4 feet away even.. Still nothing, shitty subpar 50mbps speeds still.
After looking more into things, I noticed that these weird network issues are only specific to whenever I had my headset connected to my primary Xfinity (xb7) router, I tried a Tmobile home internet router and that seemingly worked perfectly fine, hell I got significantly faster speeds when running an internet speed test as well, despite the fact that the Tmobile router is quite literally phone hotspot.
Before you all ask I always kept my maximum bitrate relatively moderate, around 80mbps for the most part, I noticed that with all of these latency spikes, virtual desktop would automatically set the maximum bitrate to crazy low numbers like 22mbps, and the other night, even 15mbps. My pc is plugged into my router via ethernet, and again, everything was perfectly fine before, presumably this v2.3 update was installed, things still work fine on my quest 3, and quest 2, but NOT my quest pro.
So.. if I were to guess? Im assuming this is some weird oddly specific bug that only occurs with my quest pro, and whatever the hell is going on with my Xfinity router in particular. I already tried changing my channel bands to no avail, and unfortunantly Xfinity is realitively restricitive on the options you can even play around with within the app, and the local gateway portal.
TLDR: My quest pro network performance has degraded significantly after a somewhat recent update, seemingly only with my primary Xfinity (xb7) router.
Has anyone else out here ran into these issues? Do I really have to go out and spend more money on a dedicated router to curb Meta's terrible software update practices? PTC is full so I can't even test if thats an option.. Anyone have any ideas in general?
I RMA'd mine for a dead pixel and it has been FIVE WEEKS since I sent it. I received an email over a month ago confirming that they'd received it, inspected it, and that I would be emailed soon with tracking info on my replacement. Nothing since.
I have opened tickets with them asking, they just say they are still working on it.
I am now wondering how many months it will take.
hello i'm experiencing issues with my face tracking, it says there is 0 OCS every time i launch the vrchat face tracking app and im not sure how to fix this. i have already looked up the causes and tried them all, i've reset and reinstalled everything as well, also i have all the settings that need to be on turned on. can anyone help?
my setup: quest pro, vrcfacetracking app, vitrual desktop, steamvr, i also have fbt but i don't think that effects it.
Just curious where all of your heads are at on this upcoming product.
My initial thoughts are that it would be a sidegrade with more pros than cons, except for the fact I lose native face tracking, which unfortunately is a non-negotiable loss anymore.
I could just get or make a babble, but I appreciate the native no-frills aspect of it in Quest Pro and don't feel the value of the Steam Frame over the Qpro justifies an entire HMD purchase.
I remember seeing meta announce this, did it happen, does anything use it?
My quest pro controller started behaving weirdly.
Doesn't stay connected. When powered on, the led flashes in a weird pattern: One long for the left led, and one blink on the right led. There are no documentation showing this led pattern.
I believe the controller is able to pair with my headset. However, it stays connected for a short bit before a notification pops up saying it's been disconnected.
I tested the input by checking the joystick deadzones, and the joystick responds for a short while before it stops working, then starts working again.
Has anyone experienced this before?
I've been using this headset for only 4 months and just the other day my right eye wouldn't blink. I ran calibrations and test and when I closed my left eye it would jitter in the same spot, I factory reset and cleaned the hell out of it and it came back just for a couple days and now it back to jittery in the same spot. Any ideas to fix it or is it a new one angle
Hi everyone,
I honestly don’t know what else to do at this point, so I’m posting here hoping someone from Meta or the community can help.
After only 4 months of use, the face tracking on my Quest Pro stopped working completely. Since the headset was still under warranty, I contacted Meta support to request a replacement.
The first problem: Meta told me they don’t provide warranty support in my country (Brazil).
Because of that, I had to pay around $300 in export taxes and shipping costs just to send my Quest Pro headset to a friend in the United States so the RMA process could continue from there.
In the support emails, Meta explicitly told me to send ONLY the defective headset... no controllers, no cables, no accessories.
So I followed their instructions exactly.
Weeks later, after spending all that money and waiting for the headset to arrive at Meta’s warehouse, I suddenly get told that they actually cannot replace only the headset, because they only have replacement for full kits. Now they’re saying I need to send controllers and cables too.
The problem is:
I tried everything I could to find a solution:
Every single response I get is just a generic copy-paste email rejecting every possible solution without any empathy, flexibility, or real attempt to help.
I’m honestly exhausted and extremely stressed by this whole situation. I already spent a huge amount of money trying to follow their process correctly, and I still feel completely unsupported.
Has anyone dealt with something similar? Is there any way to talk to someone at Meta who can actually help?