Inspiring

Solved

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

1188 replies
383252 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.)

B

bstefon

Participant

I am having the same exact issue. Trying to figure out if it's a faulty antenna, intended (but problematic) antenna, or firmware/driver issues on the Quest 3.

tfosseliAuthor

Inspiring

Since my Quest 2 has full speed I'm hoping its a quest 3 firmware issue.

C

CaptainSnickerdoodle

Up and Coming

Also check to make sure that your own networking equipment has all of its required firmware updates. Sometimes if a newer gadget is using newer TCP/IP specifications than what a router with older firmware supports, you won't get the best performance possible. I've seen the same with bluetooth as well. Everything works fine until a new device shows up and then all the old devices need updating to be fully compatible.

tfosseliAuthor

Inspiring

So finally got my Quest 3 yesterday and was thrilled to continue my playthrough of Propagation Paradise Hotel. Only to find that the tracking of the controllers in AirLink is totally broken. It's like they are moving at 6 fps and its impossible to aim.

Tried using USB Link and there they work fine!

(Also my Quest 2 controllers work grate in Airlink)

I Hope this is a bug an not a limitation of the new controllers.

tfosseliAuthor

Inspiring

Don't know what I did... but after testing virtual desktop, where the controllers worked fine. I went back to AirLink and now they are better... still not grate for fast movements but a lot more usable.

tfosseliAuthor

Inspiring

For context. I connect my headset to a dedicated 1500Mbps Wifi6 Accsess Point wired into my main network. My PC is also wired.

(Both my main Ruter (TP-link TP-AX1800 wifi6) and AP (TP-link RE-505X wifi6) has the latest firmware.)

In otherwords nothing else is using that particular wifi signal so we can rule out interference.

https://youtu.be/RFGjCXDRasM

tfosseliAuthor

Inspiring

Just in case, I factory reset the headset. No improvement.

Z

zoskia

Participant

My Quest 3 seems to have a problem with finding Wi-Fi 6ghz network. I tried different things like changing channels, setting factory settings on a router and nothing worked. My Galaxy S23 Ultra and PC is able to connect to Wi-Fi 6ghz without a problem. I’m using asus rt-axe7800 router with bandwidth set to 160mhz on a 6ghz band.

L

Luca300

New Participant

anche a me non trova il WiFi6 asus rt axe7800

D

DanielNemo

Participant

I do have the same issue: Quest2 via Wifi5 is working flawless and has a rock solid 1200Mbit connection, there is no fluctuation in connection speed and no interuptions.

On the same router the Quest3 via Wifi5 has an unstable connection, *constantly* jumping between different connection speeds and causing stutter on video and audio. Connecting the Quest3 to Wifi6e didn't improve the situation, the fluctuations in the connection speed are now just between higher values but the interruptions continue.

I just reconnected my Quest2 to doublecheck and can confirm, this issue is caused by the Quest3. I can not use the headset like this, currently the PCVR experience on Quest2 is superior to Quest3.

Going to doublecheck router settings if there is any new feature enabled that would only be available to Quest3 but I doubt that. Will also try a different Wifi5 router and report back.

Setup: tp-link Archer AXE75 Wifi6e router, Nvidia RTX 4090, Intel i11700k, Corsair 32GB, Win11, latest updates, latest drivers, latest firmware, no overclocking, no other devices in this WLAN.

D

DanielNemo

Participant

My Quest3 connected via Wifi5 has an unstable connection, constantly jumping between different connection speeds. In all PCVR games I do get occasionally 1 second long stutters (video and audio) which I attribute tho the fluctuating Wifi connection speed (constant 120fps with constant frame time besides those huge stutters). Connecting the Quest3 to Wifi6e didn't improve the situation, the fluctuations in the connection speed are now just between higher values but the interruptions continue.

I just reconnected my Quest2 to the same network to doublecheck and can confirm, this fluctuating Wifi connection speed and the occasional stutters in HLA can only be observed on the Quest3. Currently the PCVR experience on Quest2 is far superior to Quest3.

Going to doublecheck router settings if there is any new feature enabled that would only be available to Quest3 but I doubt that. Will also try a different Wifi5 router and report back.

Setup:

tp-link Archer AXE75 Wifi6e router, Nvidia RTX 4090, Intel i11700k, 32GB CL14 DDR4 RAM
Win11, latest updates, latest drivers, latest firmware, no overclocking, no other devices in this WLAN
Connecting via Virtual Desktop, same settings as on Quest 2
Quest 2 is working flawless with this setup, rock solid Wifi connection
The fluctuating connection speed on Quest3 can be confirmed via Virtual Desktop performance overlay

I will have to send back my Quest 3 anyways as it has a defective pixel right in the center, just trying to decide if I should get a new unit at all or simply acknowledge that this is a botched release and that the current Wifi-situation makes the device unusable for PCVR.

Questions:

Is everyone who is using Virtual Desktop experiencing fluctuating Wifi connection speeds on Quest3 (check Virtual Desktop performance analyzer)?
Is this fluctuating connection speed by design?
Why does this not happen on Quest2?
How to improve the current situation?

-----------------------------------------------------------------------------------

EDIT:

I did solve my Wifi issue by downgrading from a new Tp-Link Archer AXE75 6e router to my old Wifi5ax ISP provided router.

Long story (relatively) short:

Multiple people had been affected by WiFi issues with their new Quest3. Some have reported here, others on Reddit.

The WiFi issues reported where momentary blackouts, complete connection drops or sound/video stutter (despite 90% free headroom…). Multiple users did mention that the Quest2 is running find in the same network/same PCVR setup.

I did experience all of this too and started troubleshooting blindly: Fresh Win10/11, different NVIDIA driver version, different optimization settings on every level - the usual madness.

It wasn’t until I removed the newly bought Tp-Link Archer AXE75 Wifi6e router and instead used my cheap old ISP provided router when suddenly all the issues disappeared.

As the Tp-Link Archer AXE75 Wifi6e router is very commonly used in the VR community (it got its dedicated recommendation in the VD Discord) I guess many people will be affected by this issue. Especially now that Quest 3 supports Wifi6e many will have been upgrading - only to introduce new issues…

tfosseliAuthor

Inspiring

Let me know how it goes. Because if your turns out to be defect then so is mine.

https://communityforums.atmeta.com/t5/Get-Help/Unstable-wifi-covarage-with-Quest-3/td-p/1090698

tfosseliAuthor

Inspiring

Made a video demonstrating the problem on my YouTube Channel

https://youtu.be/qSBE57U8Sdk?si=ft9KVrPcm1j3X66L

Even tried upgrading my Accsess point to a 2400 Mbps Ruter. Better but still very unstable, and i only gets a max of 1200 Mbps so pretty waste.

Going to try a Wifi6e ruter next, but still a regular 1200 Mbps signal should work to begin with. Something is wrong.

B

bstefon

Participant

So I have found a few things out and still have some troubleshooting to do.

The issue seems to be part hardware problem (router), part software issue, and part reporting issue.

So in talking to the VD devs, Quest 3 reports Mbps in realtime whereas Quest 2 does not, so that is what is responsible for the fluctuation seen.

Now the stutters seem to be related to the router used. I swapped to an older router I have to try and it worked flawless (no gigabit Ethernet though so that was an issue, but that's an older router thing but it ran smoother than my one with gigabit). I have a new router coming today that I will be testing this out further and see if the performance is better.

Finally is the software issue. Using an auto bitrate selection will result in lower bitrate as the real time reporting makes this behave interestingly in my experience. It is best to just set the bitrate to a fixed value that works well for you (start at what the Quest 2 was doing and just bump up from there until you experience issues.)

I will update once I try out the new router, but in my testing thus far it seems like it might be mostly compatibility with routers being the main issue

B

bstefon

Participant

Okay, Update time:

The MAIN issue seems to stem from WiFi AC Bands (WiFi 5) vs WiFi AX and AXe bands (WiFi 6 and 6e)

There seems to be issue with all AC bands with the stuttering and issues overall. This issue has been reported to META by VD.

There still is a persistent issue with crouching specifically. Even on AX bands, when making fast head movements (crouching does this easily) there seem to be latency spikes that cause it to lag still. Not sure if this is pure hardware issue or possibly firmware at this point.

I will say the router swap to one with Wifi 6 solved MOST issues, but some still remain as noted. Hopefully Meta will have something on this

tfosseliAuthor

Inspiring

Thats amazing work! I am running a AX ruter so that might be accurate. I ran through 4 ruters but they are all TP-link.

Good to hear they are made aware and hope you're rewarded for your efforts. 🙂

I upgraded to a 6e router and there the speeds fluxes between 1800 and 2400. So more then enough speed to use it, but still very unstable. So in a last ditch effort i asked the retailer to replace my headset to rule out manufacture malfunctions. I'll get new model next week.

But now with your analysis i can tell that it probably won't mater till the firmware is fixed.

B

bstefon

Participant

Please update on the headset swap. I have been considering the same as there are reports from people of no issues happening (but hard to tell if they maybe just don't notice the issues acutely).

The more data points that we have the better!

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO