Inspiring

Solved

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

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

R

rebapiskura

New Participant

nice

I

iGnln

New Participant

My Quest 3 also doesn't see my 6ghz WiFi

Version: 59.0.0.171.706.535429024
Router: ASUS RT-AXE7800
6G WiFi settings on router: 6G Settings

@MetaQuestSupport

R

Ruined

Inspiring

I got an gt-axe16000 coming tomorrow will let you know how it does with 6ghz

J

john2910

Participant

Yes ,let us know please..

C

CharlieCharlson

New Participant

My Quest 3 also doesn't find my 6ghz WiFi and 5ghz is fluctuating between 1900 and 2400.

Version: 59.0.0.171.706.535429024
Router: Tenda Nova AXE5700 - MX21 Pro

@MetaQuestSupport

A

AlkisTse

Participant

My Quest 3 doesn't find my 6ghz WiFi and 5ghz is fluctuating between 1700 and 2400.

Version: 59.0.0.171.706.535429024
Router: TP-Link Archer AXE75

@MetaQuestSupport

R

RangerKayla

Participant

deleted

N

nothingname1

Participant

Same problem with my Quest 3 and D-Link VR Air Bridge.
Can't do fixed bitrate of 200 Mbit/s via Airlink.
PCVR is getting shaggy and messy after some minutes. Dynamic 200 Mbit/s works though. But the quality is bad.
My D-Link VR Air Bridge is 2-3 meters away from me on a table.

EDIT:
Quest 3 has v59.

R

RangerKayla

Participant

deleted

N

nothingname1

Participant

I have 4090. Dynamic looks bad because it never does 200 Mbits. Furthermore Air Bridge should work.

"Air Bridge isn't recommended by the developer of Virtual Desktop": It's by Meta/D-Link. So it should work with Quest 3.

I have all new updates for Quest 3.

C

Ctrl2020

New Participant

I am having all kinds of problems with the Quest 3 (at. V59, specifically) and my Comcast XB8, a Wifi 6E router. It was fine under the XB7 - a Wifi 6 router (no 6GHz) but as soon as I upgraded to the XB8, which is Wi-Fi 6E, it's been nothing but problems. I can't load the store or the TV app at all on the Quest 3. Apps run fine but anything that needs Internet access doesn't work. Virtual Desktop works more or less fine if I am sub 90 Mbps, but there are spikes in the signal at anything above that. And I am sitting next to the Router with a solid 2400 Bit connection. If I connect to the XB7- at 5 GHz - there are no problems at all. If I connect to a mobile hotspot off my phone, at 5Ghz Wifi 6 - there are no problems at all. My quest 2 and Pro run fine no problems at all. It's something to do with Wi-Fi 6E implementation on this specific device. And I believe it's software regulated because the problems weren't that bad on the previous version. But they still existed. It's definitely a 6 GHz issue.

R

Ruined

Inspiring

Just as a counterpoint I tried the Asus GT-axe16000 and 6ghz works flawlessly . So it's not strictly 6 GHz, but there does seem to be some unoptimized Wi-Fi code in these initial Quest3 builds that appears not to work well with certain router chipsets

M

MrRobotG

Participant

Where is @MetaQuestSupport ?

the silence on this matter is deafening

R

RangerKayla

Participant

deleted

C

Ctrl2020

New Participant

I’ve done more testing with the Comcast router. It’s just the 6 GHz band. If I create a separate network on the thing at 5 GHz everything is fine. So it’s Wi-Fi 6E specifically

R

RangerKayla

Participant

deleted

D

Digipro

Up and Coming

hope they fix it soon its been driving me mad i dint realise it first and noticed blocky image sometimes and not very clear, checked my connection speed to me ax211 wi fi 6e i had set at 6ghz and it was only connecting with a speed of 289mb/s, i did loads took virtualization software off the pc everything , re installed windows 11 and drivers and still same issue glad i am not the only one and its recognised but i hope they can fix this soon otherwise i have to stick to connecting through virgin router and that's not good i only get 600mbs and increased latency of going through router . my quest 2 was 5ghz 1200mbps every time if it didn't connect full speed first time just disconnect reconnect and it sorted the problem out. have tried every fix for quest 3 command line different drivers no difference max i get is 20mhz channel with and 289mb/s with odd spike to 300mbps but lows go down as low as 75 mbps and the lows happen more often than the spikes upwards.

come on oculus my pc cant charge my quest 3 very good and dies too fast and have to use a wall charger so wi fi is a must as i mainly pay car and flight sims so charge cable is no problem but charge rate is need to get a better wall charger too and a mobovr v3 with couple extra battery's

Viisceral

New Participant

Man I'm pretty sad this hasn't been fully fixed yet. I have my main router (Orbi RBS850 - Wifi 6) that is then connected to my PCVR dedicated router (Eero Pro 6e - Wifi 6e) and my Mpbs has been jumping between 2400 and 1000 Mpbs on 6ghz. If it's just my main router (Orbi), it would be between 1200 and 400 Mpbs on 5ghz.

I am also very close to my router(s) as I'm playing it in the same room where the router(s) is. Using the most up to date drivers for my Quest 3, Windows 11, network equipment drivers, and NVIDIA drivers.

I also tested it if my Mbps still jumps when just using either just my main router or just my dedicated router, and the problem still persists sadly. Hopefully this gets fixed soon.

Update: Now it's just not letting me use the 6ghz bandwidth. Sometimes it works, sometimes it doesn't.

tfosseliAuthor

Inspiring

Finally i got an email response from Meta support. Hopefully we can start having a real conversation.

On Fri, 24 Nov 2023 at 09:49, Meta Store Support wrote:

Hello Thomas,

I would like to sincerely apologize for the late response as we are currently facing a high volume of request at this time. Rest assured we are still fully committed to addressing your concerns and making sure you well taken care of.

My name is ------ and I will be serving as your next level support. I would like to thank you for the feedback and providing the thread in your email. We would first like to confirm if you are still experiencing an unstable connection with your Wi-Fi when using your headset.

If you are could you please provide the serial number to your headset?

Once this has been provided our team will look into this further and provide you possible solutions for this.

Sincerely,
Meta Store Support

My response:

SN: --------------------

But you won't find a solution to this without updating the Firmware.

I have several users on the forums and in my youtube community who have the same issue. And there is simply something wrong with your communication protocols.

A working device should have a stable 2401 Mbps connection in close range if it is dedicated. Right now it's fluxing from 1080 to 2100 Mbps. And that's just from reading the connection details on the headset. (No PC involved) https://youtu.be/JFrl9rTJH8E?si=w8r0u-mvw5yJCX-6

TP-Link are trying to get in contact with your engineers because they want to help you fix the issue. They are of course interested in having the Quest 3 hardware working as well as possible with their network units. They have their own headsets now, one in the US office and one in shenzhen kina. Both are experiencing the same issues.

This is what we have found so far:

After trying to change channel and adjust wireless function, it still only randomly gets MCS9 negotiation, even in a short distance, at which it should have full speed and MCS 11 without any issue.
Both v57 and v59 are experiencing package losses on the Quest 3
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.

Please share my contact in TP-links email with your engineering team:

His name is ----- Senior Technical Support at TP-Link Shenzhen

Email is ----------------

F

Freds690069

Up and Coming

Don’t get too excited… none of those emails make it anywhere near real support engineering.

their next email to you (in a few weeks) will be “can we have you factory reset your headset and try again…”

The fact that they are asking you for a serial number and asking if you still have an issue with a problem that they haven’t resolved is the clue here it’ll go nowhere.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO