Inspiring

Solved

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

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

H

HardlyRaining

New Participant

Hello all,

I bought a TP-Link Archer AXE75 v1.0 firmware 1.1.9 Build 20231115 rel.37295(4555) especially for my Quest 3, and I can't connect to the 6GHz network.

The router is connected via ethernet to my PC and it is configured as an access point. It is between my PC and my main router (EdgeRouter 4).

The quest 3 is on system version 49777350068800510, Version 60.0.0.214.366.553497759, Runtime version: 60.0.0.214.366.553497793, OS version: SQ3A.220605.009.A1

My Quest 3 can connect to the 5GHz network on the router.

I tried and:

disabled the 2.4GHz and 5GHz networks:
narrowed the channel width to 20/40/80MHz only
enabled PSC with auto channel
manually selected channels 5(PSC), 21(PSC), 37(PSC), 53(PSC)

but the 6GHz network never showed up on the Quest.

I can connect to the 6GHz network with other peripherals.

Is there something I can do?

Thanks for reading.

P

poodude289

Up and Coming

Keep 2.4GHz enabled or it will be more difficult to connect to 6GHz with the Quest 3

V

Volklegator

New Participant

Hello everyone! I have encountered the same problem, and I've been unable to solve it for a long time. I have a Xiaomi AX3600 router with a 160 MHz channel width, connected to a WiFi 6-5GHz access point, 80 MHz, via a LAN-Cat5 cable. From the AX3600 router, 5GHz, a LAN-Cat8 cable runs to my computer. When set to 160MHz, the speed in Virtual Desktop changes every 3-5 seconds: 2100 Mbps - 1910 Mbps - 400 Mbps - 1200 Mbps, and so on. Changing channels and reducing signal power does nothing. Because of this, the game's image lags terribly. Question: does anyone else have similar issues with the AX3600 router, and how can I achieve a stable and constant speed of 2401 Mbps?

M

mouse212001

New Participant

It seems Quest 3 doesn't Make my router die anymore. I played for a good 2 hours just a few min ago with no interruptions.

I have the TP-Link Archer 8 5ghz

Transmit: 866mbps

Upload: 702mbps

Transmit Power : Middle

Channel : 80 mhz

I'm not sure if my router settings will help anyone else, Steam also released an update to the steamlink app. I'm not sure if that update fixed my problem or the router setting.

J

JPeaVR

New Participant

So this is the reason that I'm not getting any stutters with a link cable! Wow, I can imagine how great this would be if wireless PCVR would work this well!

C

CaptainLuds

Participant

All they had to do was to design a little space for a proper antenna array and the Apple Vision Pro would be DOA. Failure! Miserable failure!!!!!!

P

poodude289

Up and Coming

Except we haven't even 100% confirmed that as the issue yet.

S

StreamofConscious

Up and Coming

Just like the quest 2 lens lottery was never confirmed…..it just was. It’s likely that nothing will ever be confirmed about anything. They will quietly make a change in the next iteration and move on. At that point people like you will probably be telling everyone to just buy the new one.

D

darekd1977

Participant

I think the only chance to win may be a class action lawsuit.
tfosseli you need to be very careful with your thread and it's best to make a copy of it, because one day it may be deleted and everything written here will be lost.

tfosseliAuthor

Inspiring

Alright... that escalated quickly. Please keep the pitchforks down, folks.

No one is deleting anything. It's highly unlikely and would be a PR disaster. This has been thoroughly documented outside the forums, and Meta, through this thread, has acknowledged the issues and stated they still hope for a software fix. There is no evidence or behavior suggesting shady operations or cover-ups, only caution about the information they share.

I chose to stay positive. So far, I have seen nothing but gradual improvements. It's not fully fixed yet, and Meta has acknowledged that, but it's a hell of a lot better than v.57.

Let's not forget this issue is just one of many small problems. Unfortunately, they dropped the ball on the Quest 3. QA testing wasn't thorough enough, and shortcuts led to a heap of small problems snowballing into a big one.

My recent videos, "Was Quest 3 rushed?" and the follow-up "Meta support is overwhelmed," were like open letters expressing my disappointment. But the truth is, I genuinely want Meta's VR platform to succeed, and I think they will.

They are tackling the issues one by one. In the last update, they addressed concerns about microphone quality with a nifty AI solution. They also brought back Chromecast just two weeks after removing it, all thanks to community feedback. They are tuned in, scanning everything on forums, Reddit, and YouTube. Not everything has a quick fix, and some issues are just tricky.

One area they need to improve is being more vocal, letting us know that they hear us. However, they have superiors who are cautious about setting false expectations, especially when unsure about fixes.

Might be gullible, but sticking to that optimism.

D

darekd1977

Participant

You soothe and calm me down with what you write. Thank you. I will also try to start thinking like YOU and hope that WIFI 6e will work in the same way as via cable.

D

darekd1977

Participant

Dear!

I think we have it!!! There is a big improvement!!!

Today, I resigned myself to downloading the beta version of the V62 software, because I realized that I had absolutely nothing to lose.

After installing and restarting the goggles, there is a big improvement in the 6GHz WIFI connection!

After connecting to my router, the goggles maintain 2400mbit/s even when I turn around and move! Previously, such a state was impossible to achieve! Only when I go behind a wall does the connection speed drop, but there is still no disconnection. In the same room, no matter where I go, the speed is constant and amounts to 2400mbit/s!

I guess the meta fixed it!
While playing Beat Saber, everything runs very smoothly and there are no longer any drops or stutters (I'm talking about the beginning of testing after only 2 hours of testing). I play at 120fps and have the H.264+ codec at 460Mbit/s. I also tried it on AV1 10bit as well. in 120fps and 180Mbit/s there is also an improvement here, only at the beginning, after starting the song, there is a delay of several seconds, as if the stream was stabilizing, and then there is no difference between these codecs.

However, in H.264+ this problem does not occur at the beginning of the song.

In general, there is a really big improvement on the V62, now you can consider other improvements, whether to move the router to another place, replace the cable connecting the router with the computer with a better one, and the like.

Attention:
I recommend that people using the GT-AXE16000 router leave the 802.11ac Multi-User MIMO option disabled. When I have it turned on, the 6GHz network does not show up for a long time and disconnects.

Additionally for me setting a higher channel of 69 also results in a more stable connection than for example lower channel 5.

My current settings:

M

MrRobotG

Participant

your posts are like being on an emotional rollercoaster... 🙂

V

Vannor

Participant

If you enable PTC you can test v62. I confirm it fixed the wifi as it's rock solid 2401 now. This proves it was a software issue after all.

D

darekd1977

Participant

As I wrote earlier. There is a very big positive difference.

But I don't understand the continued complaining under my post. Instead of being happy and just checking out the V62 version for yourself, they keep complaining.

Perhaps we owe this improvement to ourselves, i.e. everyone writing here made Meta take care of the matter. We also deserve thanks to the creator of this thread tfosseli himself, who was not passive from the beginning and opposed the company's policy, and was followed by dozens of other people.

Meanwhile, instead of complaining, I encourage you to test the V62 software yourself, and I ask you tfosseli, if possible, to find out from the engineers from Meta what they did to make a significant improvement.

C

CaptainLuds

Participant

Pretty sure it was power adjustments via firmware. ALso super keen to get this confirmed. 🙂

Agree with your post. Everyone (with WiFi issues) should update as soon as possible.

C

CaptainLuds

Participant

Hi again all,

I can also confirm, that v62 beta fully resolves the issues for me. Rock solid 2401Mbps with Unifi U6+ AP on 160Mhz band (obviosuly). I come from a 2 hour session with Blade and Sorcery and the experience was better than ever before. VD, Godlike (despite only having a 3080ti) @90fps, H264+ @ 500Mbps showed a overall latency around 42ms average. That is phenomenal performance.

I also noticed my overall battery usage to be a smidge higher now. This lends credence to my theory, that the issue was a radio power output issue rather than an antenna array problem.

Kudos to META for fixing it-thumbs down for lack of comms.

EDIT: AND BIG KUDOS TO tfosseli FOR THIS ENTIRE EFFORT!!!

S

saccosvd

Up and Coming

TPLink AXE75

After updating to v62 it was the same as before, the 6E network has a real hard time showing up. Only worked once after rebooting the Quest 3 but never again.

U

Urchin80

New Participant

Aside from 6E, were you having the stuttering issue many of us were having while on 5Ghz? If so, has that gone away or gotten any better?

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO