- 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.
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:
- 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 @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.
- Router make and model.
- Router firmware.
- Full Headset version. (59.0.0.##)
- Settings > System > Software Update
---
Got an ASUS GT-AXE16000 (EU, so limited 6 GHz channels) after the first reports that it would help with the issue to at least make the best out of the situation. The good news was that the 6 GHz Wifi would be immediately found by the Q3 and I also never got full disconnects or needed to restart the Q3 like others. But both a dedicated 5 GHz band as well as the 6 GHz band would still have lots of lags and fluctuations (router on head level only a few feet away without obstructions in between). Playable for slower games, but killing Beat Saber Expert+ maps pretty much. Quite disappointing. The v60 update didn't really change anything about this for me either.
Now with v62 (which took a long time to become available here) the 5 GHz band improved a bit, but is still not 100% stable, maybe because there are quite a few 5 GHz networks around here already. However, the still empty 6 GHz band has outstanding performance now, at least with my config. Just finished 2 hours Beat Saber (where especially the movements within the room and raising the arms in front of the headset posed extra challenges to connectivity) without a single hiccup, for the first time ever. I changed a few settings even before and left them as they were through the v62 update, thought I'd share my router config here for others who still got issues even with that expensive router and v62, hoping that it's helpful:
General:
Professional:
VD is set to H.264 with automatic bitrate option disabled on VD Streamer and the bitrate set to max. 200 Mbps in the VR settings. I might try H.264+ with an even higher bandwidth later, but honestly in Beat Saber and a few other games I couldn't see any quality issues with 200, stability is more important for me right now and 200 Mbps will always have a higher chance of surviving smaller Wifi hiccups.
Since I mostly play SteamVR games I would prefer to use the Steam Link app for ease of use, but for some reason using it (with also 200 Mbps and even also 150) I get a small lag exactly every 20 seconds, which I think is a bug in that app, so I am sticking with VD for now.
Usually play Expert to Expert+, so yes, even the smallest lag would kill the score for the current song, which is why I am so happy that I don't get any at all anymore now. Latency is usually around this, often even lower (saw dips down to 28 ms):
But sure, if the cable doesn't bother you too much, go ahead with it. For me it was the single most annoying thing, I'd rather play with a few lags than with that cable. It's 2024, I barely use any wired things at all anymore, keyboard, mouse, multiple headsets, it's all wireless for me.
