Inspiring

Solved

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

1188 replies
383310 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

J

jakejm79

Up and Coming

Asus ET8, no issues solid 2400Mbs constant, even 20ft away, same with Zyxel NWA220A6XE. Both with V59 and V60. Total latency in the 30s with VD.

I assume everyone is disabling beam forming MU-MIMO and OFDMA (and anything similar) since you are using the router for a single dedicated device.

While this seems to be affecting people with various brands, the majority of responses do seem to be with people that have cheaper (TP-Link, Tenda, etc) device.

S

StreamofConscious

Up and Coming

No offense, but I didnt buy my router thinking I would need it to make a 650 dollar Quest 3 work properly; especially since my 250 dollar Quest 2 works just fine.

J

jakejm79

Up and Coming

The use case scenario for a normal router (multiple clients in different areas) is very different than a dedicated router for VR, it's hardly surprising that you'd need to configure them significantly differently. Obviously routers are going to come preconfigured for the more likely use case scenario. Since not every single person is suffering from this bug then it seems like a configuration difference could explain that.

iKadash

Participant

MetaStoreHelp

Situation: Dedicated router for the Quest 3. Literally sitting right next to it.

Issues:

- can sometimes find the 6 GHz WiFi when 160 Mhz is disabled but can never connect to it (connection is lost while connecting)

- 5 GHz only available and working with 160 Mhz disabled

As soon as i enable 160 MHz on 5 or 6 GHz i can't even find the SSID reliable.

Only stable solution currently is to use 5 GHz with only 20/40/80 MHz enabled.

Correction:

- 5 GHz seems to work somewhat reliable with 160 MHz. I was able to connect succesfully to 6 GHZ 160 MHz once but it's still a gamble if the SSID is even appearing.

Router Model: Asus RT-AXE7800

Router firmware: 3.0.0.4.388_22068

Full Headset version: 60.0.0.173.366.544898056

t3chnod3lic

Up and Coming

Totally agree. I purchased the Q3 thinking that was it. But no, Ive gone through 3 routers since and my current one is the Asus GT AX-6000. All £330 of it. Certainly £330 more than I planned. Was working half decently with v59 but v60 took it to a whole new sh*tstorm. I wish I'd got myself a decent headset. Ive only ever had one headset. The OG Vive for 6 years. The money I spent on the Q3 and the router.. I could of got myself a Big Screen Beyond or something instead. And they wonder why they arent selling well. Wake up META read the forums for a change.

t3chnod3lic

Up and Coming

If Meta are as committed as you say. Then why are they not engaging more on this issue here? Ive only ever seen one (so called) person from Meta here, but haven't heard nothing back in ages. This issue isn't going to get fixed if they don't get involved. They are doing nothing at the moment to make me think otherwise.

tfosseliAuthor

Inspiring

Yepp. When I say they are committed this is referencing the lifecycle of the Quest 2. When talking about the Quest 3 they are careful to say anything in an official capacity as they still don't have a solid grip on the issue. As the last email I got stated.

"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."

(Full mail in the OP)

I don't agree with this strategy as transparency is the best way to build trust with a community or consumer. But its politics, Meta is a big company, and coming out with a red flag stating we got a major problem right before the holydays probably wont be very popular with investors and shareholders.

A

Alphy81

New Participant

There is also a possibility that this is waiting for the wifi manufacturer's solution. I haven't looked it up so I'm only guessing that it's Qualcomm and Meta is waiting for an SDK update for example to either fix this or give Meta a possibility to create such a fix. Either way this needs to be externally escalated or it can even go on for half a year or longer. At this point I am not in good conscience recommending Q3 for PCVR to anyone and I don't think anyone should either.

t3chnod3lic

Up and Coming

It maybe a big red flag at Christmas. And my thinking is there's gonna be a lot of upset people on Christmas day when they fire their Quest 3's up and discover this issue. Could be bigger than even Meta can handle. So keeping it quiet isn't exactly a great strategy.

T

Tasyyassie

Participant

I got version 60 a while back, and there was no noticeable difference WiFi virtually unplayable . However, three hours ago, I received a QUEST 3 HEADSET and controller update I have pro controllers. Surprisingly, the issue has disappeared. I played 30 minutes of Beat Saber through PC in expert mode and experienced only one very minor stutter when transitioning from 90fps to 120fps in Virtual Desktop. Additionally, 30 minutes of Half-Life: Alyx went perfectly smoothly. I hope this improvement is not just a temporary anomaly, as I haven't made any changes to my setup. Version 60.00193.366547773830 ,Runtime Vers. 60000193.366.54.7773779. I have a new "Tenda WiFi 6" router , the quest has a dedicated 5mmhz Ch using a 160MHz bandwidth.

R

Raison75

Up and Coming

What about your Virtual Desktop connection speeds though? Do they fluctuate or are they steady at your router's max expected speed?

T

Tasyyassie

Participant

Sits on 2401 most of the time with occasional dips to 1700's with no affect on the game play.

O

Orangentroll

New Participant

Update:
The AVM FritzBox Routers have the option to enable a Guest WiFi with access to the internet, but no access to you other network devices. It uses an isolated network.
If I connect my quest 3 to this Guest network my connection is stable, no disconnects so far.

The question is why. Maybe we can further elaborate.
My local network doesn't use the default IP Address range 192.168.178.x/24 but 10.10.10.x/24.
My Guest Network uses the Network 192.168.179.x/24 (pay attention to the 179)
Maybe the quest has some weird shenanigans with local network address ranges. Just a wild guess.

R

Ruined

Inspiring

This is actually great information and super useful, probably the most useful debugging info anyone in the thread has found

It's prob less likely to do with IP ranges and perhaps more that Q3 is using some stock Qualcomm driver that is attempting to do network discovery that is bogging things down

0

0culusRift

Participant

One should note, that wifi6e 6Ghz is normaly not any faster than 5Ghz Wifi6 IF you get your Router to apply 160Mhz mode in reality.

On Asus Routers in Europe, you have to set 5Ghz Control Channel manually to 36 or 100(preferred, more transmission Power allowed) to let this hapen.

In this case, you can expect the 6Ghz to be more distance dependent because physics.

0

0culusRift

Participant

I want also repeat my question regarding WPA3. Could this be also cause problems? Who is using it (default on some devices)?

iKadash

Participant

Currently running a reliable setup with WPA3.

WPA3-Personal
WiFi 6 5 GHz 160 MHz Channel 36
ASUS RT-AXE7800
Dedicated WiFi for the Quest 3
Range about 1-2m

Mostly running stable 2400 Mbits (sometimes dropping to 2100 Mbits). Going to try channel 100 when i have the time to. 6 GHz is still not working.

Update:

Was reliable for a few hours. Started fluctuating hard resulting in pretty annoying stuttering/lags.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO