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

[yermolim]

Sure, I do not claim that they only edited that connection speed reporting. I just assume these are different changes. For other people present in this topic, the fw changes really helped. So there are real improvements in the scope of this update. But not for all the router models.

It looks as if the built-in connection speed reporting now just ignores short-time fluctuations, always showing you a nice stable value. However, you can clearly see those fluctuations using other software. At least, for now, I do not see anyone in this topic who tried v62 and still has unstable connection speed reported by the Meta software or VD overlay. However, there are people, including myself, for whom it's the only perceivable change.

[yermolim]

I also own Archer C6, which is cheaper but it's in the list recommended by VD, and its 866 mbs should be enough for playing with H264 200 mbs. I tried it as well, both with v60 (and lower versions as well) and v62. It has exactly the same behavior.

Before v62 it used to stutter when moving my head fast or crouching. The same moment the stutter happens the network latency in the overlay goes up and the connection speed goes down for a second or so. I did try to lower the graphics setting and resolution to exclude the possibility of my hardware not being able to keep up. It changed nothing. Only lowering the bitrate to less than 200 mbs minimizes the issue while not being able to get rid of it completely. It doesn't fix the network hiccups though, as you can still see the fluctuations. It stutters less only because the drops rarely go lower than 100-200mbs.

After installing V62 nothing has changed in the behavior except for the connection speed value being standstill at 866 mbs. The stutters are still there. Same as with my AX53.

The last thing I'm going to try before giving up on Q3 is to borrow the friend's ASUS AX3000 V2, which is mentioned frequently in different sources (including this topic) as the (relatively) budget option working fine with Q3 on 160 MHz.

I'll post the outcome of the test here if anyone is interested.

[poodude289]

Conspiracy theory.

They already proved that they are trying to help, yet some can still not bring themselves to have any trust whatsoever in the team fixing the problem.

[007x007]

For me it change connection speed when I go to second room. It drop to 1xxx-12xx Mbps, but in this case connection is lost, reconnect, lost, reconnect... It only keep connection when I'm close to router. Back to 5Ghz.

[darekd1977]

That's right, you should at all costs rule out the computer as a weak link. There are many factors. You need to set maximum performance in the power plan, configure the network card as well as possible, have a good quality LAN cable, and the like.

[darekd1977]

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

It's the same with me now. In the same room int 6GHz, the speed does not drop. I also noticed that on my second 5GHz-2 network propagated by the Asus router on the V62, there are no more micro-cuts and it can be safely used for VD.

[darekd1977]

Time for a little summary of the V62 beta.

On my Asus GT-AXE16000 router, the connection speed has stabilized for the 6GHz network. It is 2400Mbit/s when I am in one room, after going to the other it drops a bit, but even behind the wall if I am facing the router it is the maximum.

Stability has also improved. However, there are still network disconnections, especially at the very beginning and sometimes when moving around. However, I did not experience any disconnection while playing.

Currently, there are still micro-cuts, VD then indicates an increase in the Networking value, which of course manifests itself in a temporary drop in FPS or such micro-cuts. These symptoms occur irregularly and sometimes do not occur at all. They often occur when a sudden change of position occurs.

My thoughts are that the 6Ghz network is much more sensitive and what may not have caused symptoms at 5GHz becomes visible at 6GHz. However, of course, these symptoms should be eliminated, which is what I hope for.

[FigBird.1992]

So i thought i fixed the stuttering issues I was having by upgrading to v62 and tweaking my touter settings to 160hz, AX only and enabling beamforming, but im still having issues. The stuttering seems to occur when my head moves, not when the controllers move. This can be resolves by significantly dropping the quality settings of VD to something MUCH lower, both bitrate and resolution, but something doesn't add up here. I'm also noticing that the Encoding latency quickly spikes before the Networking latency spaces in the VD overlay.

[acreed11]

Intermittent stutter/lags still present in v62 despite connection at 2,400mbps. See below quest 3 vs quest pro performance graphs for reference (all other settings equal).

 

 

[Freds690069]

I got the official v62 yesterday.

before v62:

quest 3 would connect and run at 433/566 speed (in VD) in wifi5ac and VD streaming was around 150 hevc.

with v62:

quest 3 connects at 866 in wifi5ac (stays at 866, maybe drops to 780 with distance) and VD streams at 200 and maintains 200 hevc.