Inspiring

Solved

Resolved - Unstable wifi coverage with Quest 3 on some Router Brands.

1188 replies
383260 views

Update January 2024 - full post history below

Hi. Let me try to give a quick TLDR summery.

Since the launch of the Quest 3, numerous users have encountered difficulties with their Wi-Fi connections related to wireless PCVR. A notable bug affects certain mid-range AX and AXE routers, such as TP-Link's AXE75, leading to significant packet losses and varying negotiation rates. Consequently, connection speeds fluctuate between 480 and 1921 Mbps, occasionally reaching 2161 Mbps but rarely achieving the full 2401 Mbps speed.

In contrast, the Quest 2 maintains a stable 1200 Mbps on 5GHz dedicated networks. However, on release, the Quest 3 struggled to reach 720 Mbps, with speed fluctuations occurring every other second.

Meta was promptly notified of this issue on launch day and has been working on resolving it through build updates. Versions v.57 to v.60 have seen a dramatic reduction in negotiation rates, making wireless VR "usable" under certain conditions, particularly when in close proximity to the router and within the line of sight. Nevertheless, users still report random speed reductions to unusable levels (below 740 Mbps), even at close range.

TP-Link has been diligently working on resolving the issue since the initial launch. Unfortunately, their latest update indicates that they couldn't make a breakthrough on their end, and they believe the problem persists on the client side. They've conducted thorough tests with various chipsets, including MTK, BCM, and QCA routers, and it seems these routers are experiencing similar issues. Their focus shifted to Meta software updates, and their most recent test with the Quest3 V60 suggests that while the negotiation rate still varies, the occasional streaming lag seems to have disappeared.

A glance at this threads posts reveals that TP-Link is not the only affected brand; users with Asus and other AX and AXE routers also face similar challenges. The root cause seems to be linked to either Meta or Qualcomm. Users have noted similar issues with the Google Pixel 7, leading to speculation about problems with the XR2 Gen2/Snapdragon 8 Gen2 drivers. So in other words it's in Meta and Qualcomm's hands at the moment.

Please reply to this thread and post your information as per Metas instructions:

"December 14th Update from MetaStoreHelp

Hey everyone! I wanted to let you all know that I heard back from our engineering team. It looks like there might've been some changes with the recent v60 update. I recommend checking your headset to make sure that it is updated to the latest version, and then checking your Wi-Fi connection with your headset. If you're still having trouble after updating your headset, please let me know the below information and I'll pass it along to our engineering team so this can be looked into further.

1. Router make and model.

2. Router firmware.

3. Full Headset version. (59.0.0.##) Go to Settings > System > Software Update"

You can also make a video grab of your issue and send it to Meta over the "report a problem" option in the headset.

For video references on the issue here is a playlist in chronological order

NOTE: If you have a working setup with a different router and not experiencing any issues please post the details on this separate thread: https://communityforums.atmeta.com/t5/Get-Help/What-Wifi-6e-routers-currently-works-bug-free-with-the-Quest-3/td-p/1101778

Original post October 10th 2023

On my Quest 3 the WIFI signal is hopping from 720 - 864 - 960

But my Quest 2 ti stable at 1200 Mbps

I am sitting 1 m from the Ruter

Is my Quest 3 broken or is this a bug?

Edit FYI: This is a firmware bug with communication between some brand of routers. Please post your info here as a reply. (Se MetaQuestSupports reply)

The team has been made aware and is currently looking into the unstable connection reports.

Meta needs to know:

What version is your headset running? (Full number, i.e. 57.0.0.####)
- Quick Settings > System > Software Update
Which router do you currently have?
Tag MetaStoreHelp

Also.. Remember to send a bug report via Oculus apps or headset...

Here is how: https://www.youtube.com/watch?v=7i9Q_h_yeQQ

Edit 2, to be clear:

The issue is not dependent on AirLink or VirtualDesktop. It's a clear communication issue between the Quest 3 and certain routers in Quest build vertion 57. That effects both 5Ghz and 6Ghz. Quest 2 is unaffected.

Here is the issue we are facing demonstrated to TP-link:

https://youtu.be/JFrl9rTJH8E?si=2vBOI6E2PjGvPL_7

If you're r not experiencing any issues please post the details on this seperate thread: https://communityforums.atmeta.com/t5/Get-Help/What-Wifi-6e-routers-currently-works-bug-free-with-the-Quest-3/td-p/1101778

Edit 3 - Update:

Version 59 showed no improvement. TP-Link has received a unit and are experiencing the same negotiation rate problems. They are investigating the problem.

MetaStoreHelp has stated that they are working on the issue and it will be fixed in a future firmware update. https://communityforums.atmeta.com/t5/Get-Help/Unstable-wifi-covarage-with-Quest-3-on-some-Router-Brands-Known/m-p/1099915#M241197

Edit 4 - Update...
TP-Watched @VirtualOmnipresence 's video and confirmed:

Our Wireless RD found that it might be the case Quest3 are kind Quest3's wireless connection rate strategy is more aggressive in terms of speed reduction. Once it encounters wireless packet loss or interference, it will reduce the negotiation rate on a large scale, thus affecting the actual wireless performance.

In other words, it is actually unnecessarily overly sensitive... especially when interference is basically impossible at 6GHz.

We've tested the Quest3 v57(haven't got v59 yet) so far with almost all our routers from wifi6e to wifi7 with QCA/BCM chipest...

Also thanks a lot for your updates about that article, we will also notice to get the previous quest2 sample to check how it works with our router in old firmware, then upgrade it to newer one for checking.

We will also focus on this issue later quickly if there's new firmware released.

Edit 5 - November 20th 2023

Still no more contact with meta and the silence is deafening.

Though with the new update to v.59 it is actually a lot better on AXE75 for both 5g and 6g. It's fluxing, but not below 1200 in 6g and not below 720 in 5g. Making it... "usable"... if you are relatively close to your router.

Here is my video in my test with v. 59.

We still want to take advantage of the 2401 Mbps so that we are not reliant on no interference and being 2 to 3 meters from the access point.

Any working 6Ghz device connected to a 6 Ghz router, dedicated at close range should output a connection at 2401Mbps. If it doesn't it's simply not working correctly.

So I'm not giving you a pass just yet Meta. 😉

Edit 6 December 8th

A lot of new posts here and in my community on still experiencing this issue making their wireless experience unbearable. The uptick has been noticeable since the release of SteamLink bringing more people over to PC wireless.

I also go a new confirmation from MetaSupport over email:

Meta Store Support following up on your issue.

To clarify, the issue you are experiencing is most likely to be patched up with a new software update. I know how inconvenient this may be for you. We really appreciate your extended patience and utmost understanding regarding this matter. As much as I would like to give you an exact timeline, since this is still a known issue, I'm afraid we are still unable to provide an exact date for it.

This is also for our customers, as we don't want to set you an expectation that is vague. We value transparency here at Meta, and we can assure you that we will quickly contact you as soon as possible once the issue is resolved or workarounds are provided.

We're eager to have this one sorted out for you, so we'll keep an eye on this issue. Looking forward to solve this issue at your earliest convenience so you can proceed enjoying your VR experience.

----

later:

I can confirm that your issue regarding Wi-Fi connection has been coordinated with our engineering team; however, they didn't provide an exact time; maybe they are still figuring out the root cause of the issue. By the way, thank you for the clear explanation of your issue; that helps us a lot.

Edit December 14th Update from MetaStoreHelp

Hey everyone! I wanted to let you all know that I heard back from our engineering team. It looks like there might've been some changes with the recent v60 update. I recommend checking your headset to make sure that it is updated to the latest version, and then checking your Wi-Fi connection with your headset. If you're still having trouble after updating your headset, please let me know the below information and I'll pass it along to our engineering team so this can be looked into further.

Router make and model.
Router firmware.
Full Headset version. (59.0.0.##)
1. Settings > System > Software Update

---

Here is my video on testing version 60

tfosseliAnswer

Inspiring

EDIT May 21th 2024: The bug returned with build v.65. Lets hope its a hiccup.

...

Hey everyone! Build v62 has officially arrived, and I'm pleased to announce that my initial issues have been resolved. The speeds remain rock solid at 2401Mbps, even when I'm in a different room from the router. There was only one brief 5-second disconnect, which was swiftly resolved and did not reoccur during my session.

The issues concerning fluctuating speeds, packet losses, and random negotiation rates have all but disappeared.

However, I'm aware that some of you are still encountering difficulties connecting to the 6G network in general and are experiencing random disconnects. I'm unsure if these issues are related, especially as the problem doesn't seem to be consistent with router brands.

I recommend creating a separate forum thread on the matter so that those affected can voice their concerns and avoid being mixed up with the excitement in this thread.

Thank you to everyone who has engaged in civil discussions and shared their experiences and constructive feedback. And thank you to MetaStoreHelp and TheAntiSocializer for making sure our issues were heard by the Meta engineers.

Edit: if your experiencing micro studders in AirLink follow this thread: https://communityforums.atmeta.com/t5/Get-Help/Quest-3-Airlink-micro-lags-and-stutter-esp-when-moving-head/m-p/1150175/

When a "problems finding 6G Wi-Fi" thread is created, share it here, and I'll add a link to it.

(I can't stay as the OP of a post concerning problems connecting to a 6G network as I am not experiencing that particular problem and can't replicate it.)

Show previous replies

D

darekd1977

Participant

I have a new 3-band RT-AXE7800 WIFI 6E router that I bought especially for Quest 3 to be able to use the 6GHz network. Unfortunately, this network is not found by quest 3. After all, quest 3 supports the 6GHz band or does it not??!!

Meta 3 can only see and connect to the 5GHz and 2.4Ghz networks, but I didn't spend a lot of money on a new router to continue using these bands.

Please provide detailed information on the stage of Meta's actions aimed at removing this global failure, because there are plenty of descriptions of non-working (invisible) WIFI 6E networks on quest 3 on the Internet on forums.

Due to delays and lags, I can't imagine using the 5Ghz network.

D

DanielNemo

Participant

It is absolutely ridicolus that Meta has not even replied to this three weeks later. The issue is wide spread (at least in Europe) and Meta does not care that their product simply isnt working.

H

Hicks613

Inspiring

Wifi performance on the Quest 3 is broken whenever you move physically in your play space. You can rotate, but don't duck or step left, right, forward or back.

This issue affects AIRLINK and Virtual Desktop and I have recreated the issue on wifi 5, wifi6 and 6e. 6e copes better. But there is some major wifi issues breaking the Quest 3. I also have the problem whether I'm using H.264, H.265, HVEC or AV1 codes. As good as AV1 runs half life alyx on my test machines, I cannot duck or the game will slow to a 4 or 5 fps crawl, then recover. If I stand up, same thing. It's not the game or the pc, its the wifi on the Quest 3.

I'm testing on 3 machines using 4070ti, 4080 and a 4090. Isolated networks with only the quest 3 and the pc (wired). I'm mainly using ubiquiti and asus routers or access points. All test machines are AMD 7700x, 7800x3d or an i7 13900k. The games I'm testing is oculus desktop empty play space. Super hot PC at the end of the level - when you don't end the level. This is a great low poly and really simple game that runs like absolute garbage on Quest 3 when you move. But is butter smooth if you stand still.

Virtual desktop performance overlay shows the issue to be caused by network delays.

I'm starting to wonder if Meta didn't "engineer" a pcvr breaking feature into the headset.

All games run great via usb C cable. But who wants that???

M

MetaBasementWarrior

Participant

I'm experiencing the exact same issue with my Quest 3, and have tried two different routers, though both are Wifi 5.

The most terrifying thing about this issue is how it's so specific to moving up or down or side to side to cause the massive network drop, but rotating in circles and waving your arms around gives no network drop at all. I've seen a lot of tech stuff in my time but I have no real way to explain this phenomenon. The idea that wireless PCVR is broken for all Quest 3 units is absurd to consider but appears to be the case, which is such a discouraging outcome when the Quest 2 and Quest Pro were working properly.

R

Ruined

Inspiring

Using ASUS GT-AX11000 Pro (wifi6) and a dedicated 80mhz width wifi6 radio I haven't had any issue maintaining 1200mbps link

HOWEVER, I think its a bit crummy that Meta doesnt support the new 5.9ghz U-NNI-4 wifi6 band when there should be no hardware barrier in doing so I am aware of, considering the headset supports wifi 6e and its hardware supports up to wifi7. U-NNI-4 is not wifi 6e/7, but it supports 160mhz like 6e (tough to attain with other wifi6 bands due to radar) while having better range and probably will have less traffic over time than 6ghz band. Quite a few 2023 routers support this band, and I would really like to use it so I can get 160mhz and 2400mbps link for ultimate stability! Hoping meta updates the headset in the future for this.

tfosseliAuthor

Inspiring

FYI. TP-link users. Their engineers are also on the ball.

If you have TP-link issues also share your findings here: https://community.tp-link.com/en/home/forum/topic/634366

F

Flobud

Up and Coming

Are you the one who reported the issue there? Because if you are and you don't mind, you can add the TP-Link Archer c5400 to the list. 🙂
(but let's be logical, it cannot be a TP-Link issue since 1. Some users have the issue with other brands, 2. The Quest 2 works just fine)

2 weeks left before I send my headset back, Meta. Tic, tac, tic, tac, tic, tac. 😉

F

Freds690069

Up and Coming

What if…

what if the wifi issue is a physical defect?

undersized antennas…

antennas poorly placed inside the shell…

Internal interference from other circuitry…

how long are we supposed to wait for a fix for our new purchase as the 30 day return window approaches its end?

tfosseliAuthor

Inspiring

Don't worry. That's not the case. There are examples of it working fine with the Linksys Hydra f.eks... and if it was poorly designed it would never reach 2400... but it does ocationaly. So its definitely a firmware issue.

https://www.youtube.com/watch?v=OtUgvYZFeiM&t=143s

A

Anonymous

I'm so glad you guys properly documented the issue! I had/have exactly the same problem and tried many different solutions and none of them really worked. The issue was always related to random network stutters that occur especially when moving head or doing a sudden response to anything that's happening on the screen. What's worse is that sometimes it'll get a little bit better and then it'll start getting much worse again - whether it was also related to charging or anything else, I don't know.

I tested with many routers all properly connected and no prior issues with Quest 2, these are: RT-AX55, RT54, TP-Link AXE5400.

Here is how I described it to Meta and in later communication I also provided a reference to this post:

I am having significant issues with my Quest 3- the headset is slow and has significant lags. As I connect through Airlink or Virtual Desktop it is present in both applications. This is evident from: freezing as I turn, lagged response to movement, stutters and lag, unresponsiveness and network latency.

I tested with Half Life Alyx, Microsoft Flight Simulator with different OpenXR/SteamVR runtimes and it does not solve the issue. I also tested with different routers and all possible channels, settings, etc.

There is no resolution at this stage and it is also documented/discussed on Virtual Desktop Discord channel and online.

I didn't find customer support helpful and only one person offered a replacement only after 3-4 days. But, the other 2-3 people who committed with me were just stalling the discussion and aren't actually listening to what the issues are or reading this post to understand it better.

Since other people also reported that a replacement did not solve the issue I chose to return the headset. I definitely feel that was the right decision especially considering that it is still unresolved and no proper assistance or action whatsoever.

P.S. I also feel that marking this post as Solved is extremely misleading. I don't think it was a good reason, it really makes an impression as if it's been solved for the public.

D

darekd1977

Participant

Of course, the problem is not solved and the meta should fix this problem as soon as possible!

On my Asus RT-AXE7800 router, at night, after turning off the 2.4 and 5Ghz radios, I managed to obtain a 6Ghz connection with a speed of 1200 Mbit. Until I moved further away from the router, Beat Saber ran smoother than on 5Ghz. But after about 10 minutes, the connection was broken and the 6Ghz network disappeared from the list of available ones again.

It's a total shame to release such an unfinished product and boast that the best and recommended connection for meta 3 is WIFI6E..

But what's worse is that in Meta everyone is whining and no one has officially even farted that they know the problem and that they are working on a fix or something, and technical support sends users to the tree and tells them to do a factory reset or sends step-by-step instructions on how to connect to the WIFI network

R

Ruined

Inspiring

I recently researched a router to buy for quest3 and have read elsewhere the AXE7800 has issues with drops and low latency applications

For quest3, best choices are GT-AX11000 Pro or GT-AXE16000. They are tri/quad band and you can assign quest3 it's own radio. The former should work fine in most cases and actually outperforms the latter for less money in every area but 6ghz, however if you have extremely crowded 5ghz band the latter may be better. Personally I went with the GT-AX11000 Pro.

N

neoxx0

Participant

P.S. opened a support ticket with ASUS, too. Maybe it's a router issue, maybe Quest 3, maybe both. So it might be good it's analyzed from multiple angles.

R

Ruined

Inspiring

Are you using the ASUS RT-AXE7800? This is a known problematic router for latency, speed, stability, etc: Asus RT-AXE7800 WiFi 6E Router Review: Slow Speeds, High Price | Tom's Hardware (tomshardware.com)

The Asus GT-AX11000 Pro, despite not being WiFi6e, works better from a VR perspective than the above router does - and its only about $60 more these days ($318 at amazon currently). Can see my typical performance below playing a PCVR title with it + Virtual Desktop and the Quest 3, seems to work really well:

N

neoxx0

Participant

Thanks - I have the ZenWiFi Pro ET12 - should be more than capable for the task.

S

s1uccy

New Participant

I have a 4090 with an AXE75 6e router using a Quest 3. Using Virtual Desktop and AV1 10bit encoding, I can't get passed 140 mbps bitrate. Using Airlink, I can't get passed 300~ with h264. Meanwhile, I see others maxing out at 850 mbps for h264 and 200 for av1.

In VD, it says 6GHz and 2000mbps~ connection. Why does that not translate jnto higher bitrate? Not sure if this is a hardware issue, software bug, or I'm just doing it wrong.

omegle xender

M

MontellS

Participant

Someone is speculating there could be an issue between meta and the non USA version of this router. Are you in the USA by chance?

V

VirtualOmnipresence

Up and Coming

I also do see pretty unusable WiFi latency. I think this issue was introduced with the V57 OS Version and is also happening on Quest 2 (not just the Quest 3):
I have a Quest 2 device that is still using V56. It has perfectly normal WiFi latency. I also have another Quest 2 device that is already on V57. With tha tdevice, as soon as I move a bit around in my room, WiFi latency gets crazy high. As if the tracking task is interrupting the wifi task or something like that...

The more you move around, the worse the latency gets. I can reproduce this very consistently.

Really hoping for a fix. V57's WiFi is completely unusable for me...

R

Ruined

Inspiring

There are two different things going on. Yes, Quest 3 has a bug currently that when you are crouched/tracking related latency may spike, confirmed by VD desktop dev. It's still playable tho, just a bit unstable.

But separately, some routers are doing just fine for the most part with Quest 3 while others have major problems in general. I have none of the issues the TPLink and Asus AXE7800 users are reporting in this thread with transfer rate fluctuations and unplayable latency. On my GT-AX11000 Pro, for most games network latency is 5ms or less most of the time, the only one I've seen frequent spikes is Boneworks when in physics loops but that game seems to have latency demands in general because of the physics. In terms of transfer rates when I set router to 2400 Mbps/160mhz VD stays there and the same thing with 1200 Mbps/80mhz.

This is likely a software issue, though it is possible quest 3 has a less powerful/more sensitive wifi chip than quest 2, and hardware/situations that were not a problem on quest 2 maybe be for 3. However, the router hardware you use appears to play a large role in your experience given the info in this thread

F

Flobud

Up and Coming

"Yes, Quest 3 has a bug currently that when you are crouched latency spikes, confirmed by VD desktop dev. It's still playable tho, just a bit unstable."

This is not at all what the issue is. The issue is that the WiFi on the Quest 3 is broken. It's that simple. There is nothing specific to crouching, it also happens when quickly moving the head. (And crouching implies a fast headset move/translation)

There is not two different things going on and if you don't feel it as much as some others this is because of the Wifi6 and it's high speeds performance.

I don't understand why people are trying to make things difficult. Wifi on the Quest 3 is broken. Period. Now, only Meta can do something about it. 😊

Y

yuhan370810

New Participant

Is there anyone get V59 update to see if this issue has been fixed?

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO