Inspiring

Solved

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

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

t3chnod3lic

Up and Coming

Thanks for the info on updates and settings. I'll see how I get on and get back soon. Hopefully get the GT-AX6000 by tuesday.

B

BoltonHunter

Participant

But is this small update a little better or worse than before, regarding connection and stability ?

probert

Participant

For me nothing has changed. It´s unstable on my two Quest 3´s.
I have the 128 and 512GB version and the Asus GT-AX11000 Pro. The signal from this router is so strong that other routers register it as radar and are sometimes unable to establish their channels. But even this is not enough for the Quest 3 wifi receiver to receive and transmit stably.

And the annoying meta popup shows every three minutes or so. I send back the 128GB version this week and if there isn´t a real fix and opinion from meta for this in till January the 512GB goes back too.

But when I look at the other serious bugs, some of which have been in the software for months, I have little hope that they will be fixed.

The bug that the quest home menu and sometimes even running apps have annoying jitter when moving sideways crept in a few months ago and has not been fixed. Nothing happens anymore, as it looks in the posts here on meta.
When I bought the Quest 3, I thought that the quest and the software were polished, but unfortunately that was only the external impression created by advertising and influencers and which unfortunately cannot be found in the technology and software.

Just4Fun

Participant

So I have sent my headset back.
Why has this topic not been mentioned by the mainstream YouTube channels? Are they ignoring it or somehow not having any issues

F

Flobud

Up and Coming

I think we all have the issue but with a very good WiFi connection, maybe some don't feel it as much as others.

t3chnod3lic

Up and Coming

Have been contacted by Fitz Peng at TP-Link. Asking for me to upload my clip of my Quest 3 and TP-Link 5400 via VD. I cannot post the link here. Says my Google drive link is invalid html 🤬 so sorry, cannot post here. Unless someone has any idea's.

R

Ruined

Inspiring

Use streamable.com

t3chnod3lic

Up and Coming

Didn't the link work then?

t3chnod3lic

Up and Coming

Thanks very much tfosseli

Here's the link..

https://www.youtube.com/watch?v=z4dgLW9lGnQ

P.S The clip might not seem bad, but normally the whole screen judders like double vision. I have had some freak days where it behaved itself. But these were few and far between. 99% of the time it was horrendous. The routers now been returned. I now am setting up the AX6000 as we speak.

tfosseliAuthor

Inspiring

For a minute there i thought hey its running at 2400! That's grate! Then i got to the end of the video... 😪

BTW you can use the video icon over to embed the video in the post if you want. 😉

t3chnod3lic

Up and Coming

Yes, looks ok at the start, then starts to spike. Have no idea, because some days were not bad. But, in the end I couldn't stand the fact you never knew what it was going to be like from day to day.

Thanks for the video tip 🙂

t3chnod3lic

Up and Coming

Have just had a fair old session with the Quest 3 and the Asus ROG Rapture GT-AX6000. Wow, what a difference. This thing is a beast. Wanted to thank everyone who recommended it, especially Ruined. Was a little unhappy I had to spend double my budget, but I can't deny it did fix the issue. Just hope Meta get round to recognising there's a problem to be fixed. Now I have to learn the settings and fine tune it if I can. Using ch36 (160mhz). I'll try ch100 tomorrow.

B

BoltonHunter

Participant

Maybe you can share your experience in this thread, so we can gather information which routers work good for wireless pcvr at the moment. I also got the same router, works perfectly fine with my setup as well !

https://communityforums.atmeta.com/t5/Get-Help/What-Wifi-6e-routers-currently-works-bug-free-with-the-Quest-3/td-p/1101778/page/4

A

AlkisTse

Participant

I have just bought it also but however hard I try the 6Hhz SSID is not visible in Quest 3. It can see only 2.4 and 5Hz bands. I have tried many things (enable-disable 2.4 and 5Ghz bands also, enter manually the SSID on Quest etc). Both Quest 3 and AXE75 are on the latest firmware. Also I dont know if it has to do with it but the router is a European version. I succeded only once to see the 6Ghz SSID but that was for a few second and could not connect. Please I want some help for this problem!

R

Raison75

Up and Coming

AlkisTse wrote:
I have just bought it also but however hard I try the 6Hhz SSID is not visible in Quest 3. It can see only 2.4 and 5Hz bands. I have tried many things (enable-disable 2.4 and 5Ghz bands also, enter manually the SSID on Quest etc). Both Quest 3 and AXE75 are on the latest firmware. Also I dont know if it has to do with it but the router is a European version. I succeded only once to see the 6Ghz SSID but that was for a few second and could not connect. Please I want some help for this problem!

I have the save router and have been having decent performance for weeks, below are my settings. It's in dedicated Access Point mode, nothing else connected except the Quest 3, and of course tethered to PC via Ethernet. The Axe75 is in same room as Q3, 6 feet away.

t3chnod3lic

Up and Coming

Sorry to report ... this issue has started again with the Asus AX6000. A £300+ router???? I even reset the router and tried again but still the same. This headset is a joke. I am very upset now. This is my third router and I can't dare try again. Amazon will probably flag me for this. I am at a loss. I really wish I hadn't bought this headset now. I wanted to reset the headset back to defaults but I suspect that wont do anything. Meta need to take this seriously and fix it. What a pile.