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

[tfosseli]

• 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 @MetaQuestSupport 

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

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:

1. What version is your headset running? (Full number, i.e. 57.0.0.####)
   • Quick Settings > System > Software Update
2. Which router do you currently have?
3. Tag @MetaQuestSupport 

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

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. 

@MetaQuestSupport 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-Br...

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 @MetaQuestSupport 

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.##)
   1. Settings > System > Software Update

---

Here is my video on testing version 60

[darekd1977]

I placed my settings in one of my previous entries. In general, there is nothing to set apart from my channel: channel 37 and only 160Hz. Proffesional, however, look earlier in this thread. Added only to test operation with beamforming enabled and disabled.

[darekd1977]

Dear TheAntiSocializer,

please let me know if Quest 3 supports it a function called: 802.11ax/ac beamforming, because my router states that both the router and the receiver must support it?

The second of these features is Universal Beamforming.

My question is whether both or only one of these functions should be turned on or off for the 6GHz network, which may affect the stability of the connection with the Quest 3 goggles?

I will be very grateful for the information.

[yermolim]

Tried V62. Didn't solve the issue for me.

As multiple people reported here, the connection speed in the overlay does not fluctuate anymore, but the real connection speed still drops constantly. Fast head movements still cause network delays and stutters. It seems that their "fix" was just to lock the visible connection speed to its maximum value instead of showing the real one, which is still unstable. 😞

[MrRobotG]

If you aren’t using VD, I suggest you use it, turn on the overlay and then capture a screenshot when the stutters happen. Stutters can happen for multiple reason. Any stutters I have had has been from my PC not the network, so it’s important to do some real testing if you haven’t already.

[yermolim]

Thanks for the suggestion.

I use VD with the overlay on. I have my dedicated TP-Link AX53 router 1-1.5m away from me without any obstructions. When stutters happen (when I move my head fast or crouch), I see a spike in the network delay. It becomes yellow and the number goes up from 6ms I usually have to 20+. If I don't move my head abruptly, no stuttering takes place. I had the same behavior with v60. The only difference I see using v62 is that on v60 I could see the connection speed drop at the same moment stuttering happens. Now (v62), it's no longer the case: the connection speed value remains unchanged in the overlay, even when I go to another room. I've seen here a few comments seconding that.

That's why it seems to me as if they just made it show the dummy maximum speed value instead of the real one to mask those drops in the connection speed.

That's a shame as buying the router for at least half the price of the Quest itself doesn't sound like an acceptable option for me.

[MrRobotG]

The AX53 has been described by VD support as ‘hit or miss’, so I’m not sure if there are issues with that router itself. 

I have the AXE75 and paid the equivalent of ~$130 US for it. I purchased it because it was one recommended by VD.  It seems pretty rock solid, I can stream H264+ at 500( the max setting ) without any issues. 

I have found some games stutter though like aircar. But according to the overlay it’s my PC struggling. 

with the v62 update my tx/rx drops as expected if I leave the room and put walls in the way. But if I’m in the same room it doesn’t.

So the connection speed is behaving as I would expect it to 

[Vannor]

Guys with Tp-Link axe75: do you have any particular setting in order to get the wifi 6E to be detected, or it's just a matter of luck? How to understand if my own headset is broken? Is it legit to expect some firmware solution or this problem affects only a minority?

[H1N1Johnyboy]

Please need help I'm desperate, 
Yesterday morning I played with my quest 3 and it was perfect
Came back the afternoon and it's unplayable with wifi, standalone or with cable still perfect, but as soon as I try Airlink, Steamlink or Virtual Desktop they all exibit the same behavior, cyclical latency spike every 4-5sec
I tried to reinstall windows 10 pro
Also made a factory reset on the Quest 3
Enabled Public channel test so I could update to Version 62 (from 60) but still same issue
Tested with my older wifi 5 router (now using Wifi 6 both from Proximus Belgium) 

My setup: 
Asus X570-E gaming
Amd 5800x watercooled
6900xt watercooled
Ripjaws 32go 4000mhz C16 DDR4
Samsung M2 1to + 2x SSd 1to
Antec 1300w PSU 

So what could it be? To me it feels like either the Quest 3 antenna became defective (maybe overheated after my last Beat Saber session) or something new is interfering with my WIfi in the neighboorhood but I asked neighboor if they have new wifi or any new connected device and they said no

[DeKCoH]

I have the same thing. Everything was almost fine yesterday.
wifi works fine for me, the next day it's bad, stuttering every 15 seconds regardless of the settings.
What is the problem?

[StreamofConscious]

Interesting. Who here believes they would do something like that?