Anyone experiencing annoying frozen link sessions? Happens alot now, 5-10 mins once im in a link session..

I tried usb-c cable..was bad..

Any suggestions much appreciated

When I plug my quest two in, I get the logo screen and battery power at 100%. When I unplug it, it still shows the battery power. But when I hit the power button, nothing comes on the light does not turn green. I tried to do a reset a hard reset I tried to talk to customer support and they just told me to do the same steps. has anybody else had this issue? Was there fix it is out of warranty.

There out of warranty program I think is overpriced it’s $160 for a refurbished headset and I have to return mine. does anybody think that’s a good idea?

What do you think about this game?
Would you like to play similar titles?

Please

I got little information from the websearch on this topic, thought I should ask the folks in here if there's a resource or guide on this.

Hey folks,

I guess my QP updated to v2.7 August 28th and it is starting to have problems with eye and face tracking.

The eyes get real jittery and the eyelids don't close when blinks and such. Mouth tracking works but is also very jittery and if I hold a smile it'll slowly fade to a neutral expression.

I turned Natural Face Expressions off and the eye tracking works fine and smooth, even when I calibrate my eye tracking, the orb works just fine.

But with NFE on, it just goes back to being a mess as a whole.

Basically, am I screwed?

I have a new to me QP i just purchased that was on v.6x before we factory reset it. My plan was to disable updates via adb once I logged in but it looks like it wants to force an update before logging in. I know I could block some ports so it won't update but I'm wondering if it's worth the trouble or if that will even work.

I mainly use it for PCVR and VRC so I'm not concerned about standalone, mainly face tracking and controllers. My main Quest Pro is on the latest version and seems to be doing great but I REALLY miss being able to control updates. I remember v64 being REALLY stable for me. Then there's the sideloading firmware & Private Quest rabbitholes I'm about to dive into. Wanting to know if anyone's had success with PQ on a QP and if you think it's worth it.

Main thing, I don't want to brick this one, it's actually in WAY better shape than my old one :-).

**EDIT/UPDATE: Factory reset it it and let it update to v64. Right controller disappeared and won't pair now. Tried all the usual methods to no avail. For those wondering why I want to turn off updates, THIS is the reason. Every update is a gamble. SO disappointed.

Yesterday my left controller got disconnected, happens every once in a while, but I can't reconnect it because a couple of months ago my menu button broke on the left controller, I Don't really know what to do about it, I saw someone fixing it by just letting the controller die then charging it again, but what if that doesn't work? And there's no chance I'm going into the effort of using my warranty, because I bought it from the UK and I live in Norway (It used to be about 6 times more expensive over here than in the UK)

Am I one handed forever? Do I save up for a replacement? Can I open the controller and fix it there somehow?

Hey everyone I’ve been having this issue for around 2 months where my headset just randomly loses connection with my wifi for no reason. And i have tested this on my quest 2 to see if it has the same issue and it works perfectly fine. (I also have a router in my room if that matters and I’ve factory reseted it)

I recently got a new in-box Quest Pro, and I've come to realize it's on the original firmware that came out of the factory. Digging around, it seems to be v47, or "Build number: 28151810536300000" according to fastboot.

I'd like to set it up the headset if possible, then block updates/root it, but doing the OOBE will force an update to presumably the latest version. I'm unable to skip this OOBE with PrivateQuest because the firmware is apparently too old, so the parameters don't work.

Does anyone know what firmware(s) I can sideload update to relatively safely to at least get PrivateQuest working? I've heard conflicting reports of needing incremental updates versus going straight to a big update. And AFAIK, the typical firmware archive for QPro only goes as far back as v50.

ok my quest 3 finally gave out and after a month i started my headset search leading me to decide on a sealed package questpro due to specifically its face and pupil tracking hardware.

I'm now finding out that it has a HUGE flaw that seems to not be agreed on some say its inevitable some say its preventable and some may just be incredibly lucky.

my issue is this yes i want those features but NOT on a trial that stops whenever they die and i either buy a new one or leave quest pro behind in favor of quest 3.

here is my question

is sweat/heat an inevitable problem as stated in other posts or is this preventable

if so what are those ways that do not include having to completely lose immersion i at the very least want the side blockers on

I'm using Quest Pro - VD - SteamVR - VRChat with an RTX 2060/i5-11400F (I know but it has BEEN WORKING FINE UNTIL NOW), around August 12th I randomly started getting constant and random stutters/spikes in VR. Before that, everything was fine and I had changed NOTHING. I've spent two weeks so far troubleshooting at this point. I've updated my graphics drivers and the headsets software, completely reinstalled both SteamVR and VRChat (including deleting the leftover cache files), got off the SteamVR beta and went back to default, disabled motionSmoothing, tried changing resolution/refresh rates, lowered VRChat graphics, changed VD settings/bitrate, made sure the HAGS was off and cleared a bunch of storage on my PC. I've ruled out my Slimes because it still happens without Slimes server running. Updated SlimeVR and reinstalled its SteamVR driver anyway. tried basic/default avatars and it still happens. Desktop VRChat works fine. SteamVR and VD's performance graphs and Game, Framerate, and Latency spike when the stuttering happens. I tested another SteamVR game which runs perfectly fine.

I'm starting to wonder if this has something to do with a recent Quest Pro/Meta update, VRChat itself or something else that somehow I missed. I've asked multiple discord servers and spent days trying to fix it with no luck. I'm genuinely getting to the point where I might as well just replace my Quest Pro, but I obviously don't have the money to spent just to find out the headset wasn't even the problem.

If anyone has experienced this or knows something I haven't ALREADY tried, PLEASE help

Edit: Here are some updates just so you know what I've done since this. I have bought a new GPU (Nvidia GeForce RTX 5060 Ti 8GB) to see if maybe my 2060 just wasn't keeping up anymore. Unfortunately, it did not change the stutter. (I definitely needed a new GPU regardless) I tried going back to SteamVR beta since it was the most recently updated version and that just made it worse. Reverted again BACK to public default version. I just recently checked to see if my older Quest 3 possibly had the same issue and it didn't seem like it was jittering.

(I've also changed the codec to H264+ as well, also changed the MSAA in VRChat to 2x still no change)

So in my eyes, the issue is Quest Pro + SteamVR... I'm just not sure what to do anymore. Could anyone help out?

Hola y bonito dia a todos n.n

Soy usuario de unas gafas quest pro desde octubre del 2025 y la verdad eh tenido un problema bastante molesto con el trackeo facial o face tracking

Simplemente este se descalibra y se hace impreciso,no llega a extremos de no funcionar pero simplemente hace cosas como mantener entre abierta la boca del avi cuando yo ni si quiera estoy abriendo la boca lo mas mínimo,tambien no detecta el famoso inflado de mejillas o el sacar la lengua

Intente de todo como resetear las gafas fabrica,desinstalar el programa vrcfacetracking de steam e inclusive estar en una versión anterior de este programa por que siento que la versión nueva es una basura

Lo gracioso es que el problema se resuelve por si solo de repente,sin saber por que o la razón

Les ah pasado algo similar?

Saludos n.n

Hey fellow XR practitioners! 🚀 We're conducting a study on "Responsible XR" and really need voices and hear how you actually navigate these challenges in practice when building or deploying XR apps.

If you have a few minutes to spare, we’d love to hear about your real-world experiences in our ~20-minute survey. Really appreciate your participation or any shares! 🙏https://cambridge.eu.qualtrics.com/jfe/form/SV_8ku617x6qqXKN5I

Because we no longer have the setting to turn Travel mode on or off, You can enable Travel Mode via Meta AI
Make sure it’s enabled and active and say the command “Enable Travel Mode” and the screen will refresh

i have that problem with the button on the menu and cant really afford getting a new controller or replace the faceplate. can sm1 gve me a video guide or som sort?

I absolutely, unabashedly, love the Touch Controllers (when they’re working). They are the reason I’m still using a Meta headset. Thing is, I am so spoiled by how well they interact with game play, that I can’t play any games anymore that I can’t use them. Including non VR pc desktop games. It’s as if they have become extensions of my hands. Meta is lacking in many ways, but I have to give them kudos for designing a great game controller.

Set in an alternate present where technology forked in the 1930s, so the whole office is analog. Switchboards, pneumatic tubes, cassette decks, no screens anywhere.

Your colleagues are flat standees with three expressions each, and every one of them is facing you no matter where you stand in the room.

Good Morning, {Employee Name}. PCVR, out later this year.

Honestly, it’s been the last few updates, but I’ve noticed that the controllers work significantly better and has significantly less tracking issues, they don’t lose tracking anymore, don’t get warm (nor do I receive the message for it being warm) they update properly, and that hasn’t been a hassle for me since v60-70’s days. I can’t speak for everyone, but can anyone else attest?

Virtual Desktop recently added usb use, which is way better than the slow and buggy meta option for USB use. Researched - it can be done with the Kiwi "L1 Plus 13-Foot"
Any other cable that has capability to charge 19W or more can do it, but this one definitely can charge it and support usb 3.0 speeds at same time on 1 cable that goes into Quest Pro's USB 3.0 port

To charge and use you'd need a cable with 2 ports, one that can offer 19W or more via USB-C and a USB3.0 that goes into the PC.
But those are like, 1 meter, and your PC would need to have PD charging. I didn't find that even on 300$ motherboards or cases.
And I wanted 5 meters + ( 16ft+ )

The cable can be bought on their website.

I’m just curious to see if the “ use controllers as a gamepad” feature works on our headsets or if it’s exclusive to 3 & 3s

Heya there, I had a issue for a while and I wanted to know how to fix it :
Everytime I take my headset off and put it back on (like it turn off in the meanwhile) and when I get back on it my mic is muted. I always have to go back into the options of airlink to put it back on and getting back into my game which is frustrating, I tried to look on the support nothing, in the settings directly ? nothing pc and quest settings

So if anyone have a solution for this you'll take me out a big pain in the a\*\*
Thank you

I checked on the internet and apparently it’s some firmware thing again and told me to reset the controller but it didn’t work. And then it told me there could be dirt in it or smth but idk. I’d have to press the button 4-5 or more times just to bring up my steam menu

Hey everybody, a few weeks ago my quest pro started stuttering when using steam vr, I usually use steam link but I tried virtual desktop and that didn’t work either. There was a day that I decided to replace my wifi modem to see if it would fix it, it did but it only lasted a day and went right back to doing what it was doing before. Is there any ideas on how to fix this?