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.

[Shadewing]

You can't, Meta doesn't want you to. Unless you go download an older version through reddit and sideload it (which you need a developer account to do as far as I understand. forgive me if I'm wrong), but good luck staying on that version for more than a day with your headset's forced auto updates. You should find a bunch of info on reddit on how to side-load an older version, and I wish you luck. maybe you'll have some luck.


On a different note, Pikpukpak is right. We should just give up. Meta doesn't care about this problem and at least in my case I'm buying a different headset (pico 4) and I'd recommend others do the same.
I don't care if the Quest 3 is/will be a better headset than the pico 4. The quest 2, 3 and pro are all expensive bricks/paperweights if I can't use them and don't trust the company to not ruin them later on like they did airlink with this v54 and v55 update.
Multiple people are leaving meta, and I personally know a few people who are no longer getting meta products anymore either 😕

Meta, I'm not even mad anymore. Just a bit salty. Here's some words of hope/advice: You can still recover and rebuild trust if you guys and girls over there start... I dunno... Doing something? Start treating us like humans? Fix the problems you've caused? Maybe I'm for once being too hard of an optimist, being too hopeful, I dunno.

The ball's in your court meta, I'm... Pretty much done here.

[LeZech]

My friend, i think we all did it. But as well we all stop to answer after 10 or 20 messages with the support team. Probably all these issues are then considered as solved, but believe me it s not.

You must know that we spend more than 1000€ or dollars buying games and meta material.

You can't leave it behind. 

A friend bought his first vr headset end of april and he could play decently only 1 month with it. It was just too late to get a refund.

Please do your best

[Arbak22]

So I've just made an account to complain here because I think it's the only way for this bug to be recognized by META, but I have the same issue.

Haven't been on VR for a little while, and came back to this disaster, airlink is suddenly unplayable, I have insane latency, whenever I move my head around I can see some black borders around me, on vrchat it feels like I have no more than 1 fps.

V55 didn't fix this issue, it needs to be recognized by META, this is NOT an issue caused by your userbase, your update is bugged, and it's a very serious problem.

[VincentGraves]

I'm still having an issue with AirLink\Virtual Desktop if the bitrate is set to 100mbit or above. There's definitely no issues with my network, but airlink is just unusable at higher bitrates.

[Exius86]

It's getting more and more ridiculous. For over a month key functionality of the headset keeps staying ruined. I understand that the software architecture may rule out the ability to roll back updates, but what any other company would do in such situation - release a hotfix ASAP which removes whatever change to drivers or other part of software was made that caused this issue. Any company would do it, but what does Meta is a joke... Stupid and not funny joke. I can't understand is it a secret policy of the company - to ruin PCVR? What's next - will you ruin Link cable the same way?

The problem of such scale should be treated in a completely other way! The only update that fixes the issue (and half of the users report that the problem is not fixed) is rolled out so slowly, that I guess I'll get it when Quest 3 is released this fall. And the only alternative is to enter PTC and get even more bugs. I don't understand what's wrong with Meta, why can't you just release a hotfix which rolls back to the latest stable Wi-Fi driver and then experiment with your QA team and take whatever time you need to make that improvements that you wanted to make but failed. I don't mind if the next update comes in a year but is super-polished and well-tested.

[Ryko0483]

I agree,  we should have the ability to roll back to a working Firmware

[Krissrex]

I tried H.264 and Sliced Encoding, and got pretty a playable connection. Not perfect, but not garbage. Was able to bump the bitrate quite high (like 400Mbps) and not trigger the "craziness" of this bug (black edges, swimming display and lag, 1fps). Slice count is the default 5 for H.264 (you need regedit to see the setting). I still had the small hickups because of high bitrate and bad router, so I lowered it down a bit to 250, still not perfect.

https://imgur.com/a/zyNzSBE

[TheAntiSocializer]

Hey all! I just wanted to jump in here because I did want to note that the issue with v54 should be resolved now/with the v55 update. 

If you're on v55 and still continue to experience issues, I recommend continuing through this thread here. This way we can distinguish v54 and v55 since we don't have a specific way to determine the difference other than reading each comment individually. 

Thank you for understanding!

[Rayne23]

Good Afternoon,

I can tell you that I am currently on v55 and the issue still exist with the Quest Pro. I did manage to isolate the issue that I am having is in result of moving the Bluetooth Mouse, (Logitech 650M L) which causes the stuttering and screen tear within Virtual Desktop as well as increased stuttering within the Meta Home Screen as a whole. I am not the only one who is suffering with this either. Other users within DIscord have complained that they've been having the same issue whenever they moved their mouse around. This issue only started happening when My Quest Pro was forced to update to v54 where it was at its most worst. Even though the stuttering has slightly decreased after the update to v55, It still persists when moving the mouse.   

[Sluttty]

Rayne,

You've probably already checked this, but Bluetooth is 2 Ghz -- are you absolutely sure your headset isn't inadvertently connecting to your 2 Ghz wifi access point?  If you haven't already, try disabling the 2 ghz wifi radio entirely?