06-01-202305:00 AM - last edited on 06-28-202408:54 AM by TheAntiSocializer
Been using Quest pro with airlink for 4 months now without any issues whatsoever.
After the headset was updated to V54 I'm having headset lag/connection issues on airlink.
Screen is stuttery at times when moving in my playspace or moving my head, the image gets laggy, choppy and black frames appear on the side of the screen oposite to where I'm moving my head.
Image quality has degraded significantly with lots of "artifacts".
This makes casual games like VR chat hard to play due to constant lag and stutter, games like Beat Saber are impossible to play.
I havent changed a single thing in my playspace nor my setup, router config is the same as when it was working, PC is the same, no update has been applied to any of this.
Any advice would be much appreciated as Im lost on what to do.
Just in case
Specs
CPU I9 12900k
32GB Ram
GPU: NVIDIA RTX 3080TI
Router: TP-link AX1500 Wifi 6 dedicated just to the headset.
Thank you for the update. I am trusting you - a totally random person - much more than any Meta support at this point. Whoever made this, whoever approved it in code review, and whoever QA-d it and decided that it's okay to roll it out are all out of their minds. I don't think I'll ever forget the v54 incident, and I really hope I don't have to interact with Meta products in the future.
I feel the same. Frankly, as soon as I can, I'm leaving meta.
for real guys... what is so absolutely horribly awful about the idea of rolling back to v53 and starting from scratch there so you don't introduce the bug again? any developer worth their salt would roll back if it's needed, and frankly... its needed at this point.
I haven't seen meta ruin their reputation this hard in a while. The extra damage simply comes from the fact that there is simply no scramble to fix the issue. its just... waiting... and waiting... and waiting...
The onlu thing that work is staying on the previous v53. V54 and 55 are just burnong my brain. I reinstalled windows and i tried my friend computer and network, not working . It's definitely tje meta fault
My school is actively getting rid of every Quest 2 they have and are replacing them with Pico 4. They’re part of a big School network and they’re encouraging every other school to do the same as this has been blocking students for too long now.
I honestly hope that more establishment will act this way because Meta is clearly taking this too lightly and i totally agree with the reasoning of Sycix.
Meta’s way of pushing updates is the stupidest thing I’ve seen. Even Apple don’t do that and god knows how many device they have out there. I’ve seen features getting removed for no reasons. I’ve seen the interface change every **bleep** reboot. Controllers gestures are **bleep**ed on Quest Pro. The Oculus Desktop App is the most bloated streaming software I’ve ever used.
How many people are working on firmwares ?
How many people are doing extensive testing of those builds ?
Some more feedback for this absolute beast of a thread.
Airlink streaming seems to be reasonably solid again on the Quest Pro now, however occasional network drop-outs are still an ongoing issue. I'll note that the Quest Pro is the only device on my local network that experiences these drop-out issues (seems that the Wifi stack on the headset completely crashes out and restarts about 30 seconds later?). The Quest 2 does not have this problem.
These drop-outs are made slightly more frustrating by the fact that they often upset the OculusLink software as any software that hooks into the eye & face tracking endpoints of the software also needs to be restarted any time the headset has to reconnect to the local network.
I really do enjoy working with the Quest Pro, but the frequency of problems on the platform are going to keep it relegated to a very small niche of users who have the patience and the know-how to deal with these common problems.
Hey there! We appreciate you bringing this to our attention. We understand how this may be affecting your VR experience. So, we'd like to jump in and assist you in getting this fixed as quickly as possible. Currently, there is no way for you to downgrade versions once you have updated to them. Version 55 is slowly rolling out to everyone and should fix the issues you're having. We thank you for your patience as we look into this!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
The issue is no longer breaking the wireless VR, but instead it has now moved on to how Meta is handling it and how to remedy it and the dumb update scheme used. We should be able to ROLLBACK and pause updates as we see fit. Judging from the responses to all the threads so far, V55 does not fix it, at least not for everyone.
PTC is not an option, because either you stay on there and face even more clown made updates OR factory reset and switch back to the current live HOPING THAT YOU ARE IN THE STUPID ROLLOUT WAVE OF UPDATES. Really, suggesting PTC is like telling someone to give up a wheelchair for crutches. AND there are people that update to this and they are STILL experiencing stuttering. So double F you if you end up in that happy group eh?
It is super super simple. We want more control over the version of the headset's firmware. Without it we clearly have nothing more than test units.
A rollback is the simplest, no brainer, no BS, no fuss answer. This should be an option for ANY Quest Pro/2/(and future 3) user. There is no conceivable reason why we should not be able to do that, and STOP updates when we don't see a reason to update to the next version and skip the horsing around prod testing that is meta's update process.
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
