Resolved - Quest Airlink lags and stutters after V54 update.

[v1rtualv0id]

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.

[Sycix]

I'm sorry for the hate that you're getting, most of us know you're just the messenger.

I think it's important to understand for both parties that the customers and the support team should be on the same side in a disaster like this, and I think what sparked a bit of a riot was the downplay of the situation, since we're not sure that you understand that we cannot use our headsets at all.

With that said, we would really appreciate if you could sneak in a ticket for the engineers to implement the version rollback. Nobody would notice that it's not coming from management.
I'm just kidding. Hopefully we won't be in need of a version rollback feature again, but please at least tell the QA team to be more careful next time.

[Krissrex]

With v55 it seems to lag even at 80Mbps just staring at the menu in airlink. I don't have to do anything but wait about 20s, and it lags for 10-30s.

When it lags, the motion-to-photon and compositor latencies spike https://imgur.com/a/BU39GhA. 
It also seems to be a ~5-10 Mbps drop in network speed when it happens. 
I uploaded the csv files for 2 graphs here https://gist.github.com/krissrex/8092a199be369517c63ac4b76f273a3f .

I tried to test for bufferbloat on the router, but it doesn't seem like a big issue https://imgur.com/a/94E6t2o.
I also got about 400Mbps and 9ms latency on fast.com, so it shouldn't really struggle at 80Mbps. (Note that I was using my PC's wifi card (AX200) at that point as a hotspot.)

[Shadewing]

I beg to differ. The support group is working under the pretense that aalll of this is "user-error"

It's not.

Support refuses to be flexible, refuses to acknowledge the problem, refuses to compromise, refuses to be adaptive and refuses to change anything. They keep saying "no, we can't do this" (referring to the request for optional rollbacks) and never even consider the fact that they SHOULD be saying "Ok, lets change this thing and MAKE it possible."
Support and meta devs are, for some inexplicable reason, incapable of relinquishing their control on OUR headsets.

Improvement is IMPOSSIBLE without CHANGE. Support, stop being entirely stuck, and start being dynamic. start fixing, start being proactive, start thinking outside the box.

Contacting meta support has been nothing but frustrating and condescending. they tried to fix firmweare problems, by assuming everything and everything is my fault and every user's fault.

spoiler: Nothing they tried for the last month worked. because its a firmware problem, NOT a user-bug.

[Sycix]

Let me start by saying I'm just as mad as you. My headset is still a piece of brick.

But the support team is not responsible, there's no on/off switch for version rollback, and even if there was, they don't have any say in these things. They can't start fixing, because they are not engineers.
Just like when you're calling your ISP because your internet doesn't work and a lady picks up the phone, it's not that lady who's going to come to your house to fix the wiring.

This is how big companies get away with it, they don't give us anybody who's responsible, so there's nobody to get mad at. 

And for the user-error part, you're just a username to them, and believe me, users are often very dumb. So when they start off with saying "oh, did you plug your internet in?", that's because this sentence is solving like 20% of the problems, so it's good to get it out of the way first. I think it's clear to them at this point that this is a complete disaster.

And if you had a specific unpleasant interaction with a tech support in a private message, you should definitely let them know that.

[Shadewing]

I get what you're saying, its true. But if it's clear to them that it's a disaster, they sure aren't in any rush to fix it in any sorta way. That includes a rollback... like many, MANY other developers have done in the past, with zero issues. that's just one way of dealing with it. Just one example.

[Sycix]

That is true though. Someone somewhere could make the decision to temporarily have an opt-in rollback to v53.

Oh, but then nobody would be testing if the fixes are working or not.
I guess we unwillingly clocked in our shift as guinea pigs for Meta

[pikpukpak]

what a cluster f!

guys, just give up. it is what it is.

As i have noted before. this was done intentionally so we will have to upgrade our devices in the upcoming months.

we were not born yesterday. an update that breaks core functionality of a device....presumably the only functionality that is worth it to keep using the device after a newer gen will be released.

come on Meta. how dumb you think we are?

No way am i going to jump into the Q3 boat after having 2 versions (54, 55) that just bricked my device to the point every VR session ends in frustration. I hate the experience, the device and just rage quit. This is even worse than when i first got into VR in 2018 with CV1 and the experience was pretty much troubleshooting....all the time.

Absolute trash, everything! Support, Devices, SW, what a sham.

[Krissrex]

For anyone desperate, and with an AMD GPU, I am still having good results with ReLive VR. It requires a sidequest app as well for ReLive, so this needs some setup to work.

Not perfect, some small stutters, but I run at a high resolution https://imgur.com/a/noWdCrU (That's the web GUI https://github.com/GPUOpen-LibrariesAndSDKs/Radeon-ReLive-VR/wiki/Advanced-Configuration-Using-a-Web...).

Seems to be capped at 100Mbps even though my config says 170, when I check speeds in Task Manager.

[LeZech]

How to rollback to v53?

[mqt55]

After quite a bit of testing of the new update v55 ptc, i can sadly say that its still as unplayable as before, its not worse but still unacceptable for a multimillion dollar company. Seriously meta get yo **bleep** together