Inspiring

Solved

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

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

M

Mysterofthee

New Participant

Version: 57.0.0.295.669.526537896

TP-Link AX1800 (Archer AX21) Wifi 6 Router.

R

Raison75

Up and Coming

So what's everyone doing in 2 weeks when the return window expires? Are you guys holding out in hopes it can be fixed via an update? 🤔

R

Ruined

Inspiring

Its not clear what needs to be fixed on Meta's end. Some like myself are not experiencing this issue, at all.

A

Anonymous

I think it's fair to say that 9 out of 10 people here are experiencing this issue and extremely disappointed with it, and they are returning headsets already. The fact that one month after the release there is absolutely no support speaks for itself. It is should not be the task for customers to test the headset and justify why it's not working.

Finding some unique router one of a kind router after trying 5-10 different alternatives is not a solution, it's a distraction! Quest 2 works on the same network just fine, so should Quest 3. I returned my headset because it didn't work for PCVR.

P.S. I believe there are people who have the same issue and choose not to post anything on the forums - there is no help whatsoever and it ends up being a complete waste of time.

R

Ruined

Inspiring

FYI I know one other person outside of this forum who got a Quest 3 besides myself, and they are also having zero issues with WiFi and heavy PCVR use.

Their router is: Netgear Nighthawk RAX70 with no special setup on the 5ghz band. This is a WiFi6, not 6E, router, but a high end WiFi6 one.

edit: remembered i knew one other individual as well. He also is having no issues with heavy PCVR use and wifi quest3 via Netgear Orbi Rbr750 @ 5ghz

LunchAndJosh

Inspiring

In this case, you are suggesting that Quest 3 has quality control issues, and this is an even BIGGER issue. You are implying that some Q3 headsets have faulty wifi hardware because it works properly for some and not for others.

Thanks for making it visible!

R

Ruined

Inspiring

Nope not suggesting that at all, tho of course anything is possible.

Could be as simple as a firmware update needed to improve wifi compatibility on the headset or router side

Or could be the wifi chip in quest3, or quest3 being more resource demanding itself, requires a more stable wifi signal for lag free VR play. From reading thread it seems TPLINK routers in particular are problematic, and also lower spec'd routers from various brands. The high end wifi6 gaming routers from Asus/Netgear seem to be doing okay as far as I can tell.

But, just cause your router worked well with quest2 doesn't mean it's gonna work well with quest3. VR gaming is one of the biggest challenges for wifi, requiring both high bandwidth and low latency. And since it's new hardware, if you want to be on the cutting edge you might need to reconfigure some of your hardware to accommodate said new hardware.

D

dedmoin

Inspiring

When looking at the WiFi issues some people experience it might looks like some isolated strange situation, a few people might have bad luck with their WiFi setup (in combination of possible other WLAN interferences, who knows)

Although when reading other threads, like

bad passthrough quality (recorded image is much better than what users see in HMD)
issues with controllers (not being recognized at all, losing tracking, ... issues with IR)
GPU at lower frequencies (500/545 instead of 599 as confirmed by users and devs)
strange behavior of Quest 3 when coping with bad connections (like controllers cease to work in pause menu. I have no clue how bad WiFi can impact tracking)
connection latency spikes in certain situations (works generally fine except when moving up/down)
Airlink not finding PC
Oculus app stop recognizing Quest 3 micro (ie shows error saying Quest 3 doesn't have one)
...

...then it definitely sounds like a generic quality problem with Quest 3 and not bad luck for some people.

I have all of those issues and still tried to find a solution for them by improving all possible factors since people with perfect conditions won't experience those issues. Like buying a new WiFi 5 router, which resolved some of the controller issues. But improving conditions just 'hide' those issues, they are still there.

However, since recently I am experiencing extreme ghosting effects in passthrough, and I am going to return the Quest 3. I already spent enough of my time trying to solve issues, although I would expect more for my money.

I have 2-3 tickets at Meta/Oculus support (not sure how many since support/ticketing system is a mess imho) but I didn't hear from them since days. (the most useful advice by support was to replace the Quest) And another ticket with Asus for the WiFi 6e issue.

Anyways... just wanted to add some context to the issues people have with WiFi. Having consumers to buy another WiFi router for additional 300,- or so shouldn't be the official 'solution'. Currently buying a new router is not more then a best guess since no one seem to know why there are issues in the first place.

F

Freds690069

Up and Coming

It’s a little concerning that meta has been quiet with no new info on this wifi issue.

J

john2910

Participant

Same problem here on my wifi 6e router archer axe75 !

F

FUNtastic

Inspiring

I currently have three WiFi 5 Ghz routers here that I have tested with to see if the problem occurs. When testing, the routers are 1 meter away from the Quest 3, and the Quest 3 is the only device connected to the router via WiFi. With one of the routers, no interference is felt at all. I have set a fixed channel in each routers configuration.

1. my already older Netgear X6 Nighthawk R8000

The Quest 3's network connection speed fluctuates continuously. Sometimes 866 Mbps, then again around 700 Mbps and so on. Each time the speed changes, a brief hiccup is felt in the headset. Virtual Desktop's performance overlay briefly shows that the frame rate drops from the set 90FPS to 89 frames, although there is still plenty of performance overhead as far as the GPU and CPU are concerned. SSW is deactivated.

What's even worse is that fast head movements, especially in the vertical direction, cause such lag spikes that the image in the headset can't keep up. When this occurs, the performance overlay states that both the network and decoding are causing the latency.

2. a relatively inexpensive TP-Link Archer AX10.

The router behaves similarly to the Netgear router. Especially the lag spikes during fast head movements are massively annoying. I have the feeling that the change in connection speed does not occur as often as with the Netgear router, but I could be mistaken here.

3. the FRITZ!Box 6591 Cable of my internet provider

Again, the overlay shows that the connection speed fluctuates, though definitely far less frequently than the other two routers. The speed is always in a higher range between 1700 Mbps and 1400 Mbps. However, no more visible hiccups occur here when the speed changes, and the frame rate also remains stable at 90 FPS according to the overlay.

There are no latency issues at all with head movements with this router. The picture in the headset remains absolutely stable, and both the network connection and the decoding do not show any increased latency according to the overlay when I move my had like a crazy person.

With the other routers, a reduction in the bit rate led to the problem being less prominent when moving the head, but it never completely disappeared even with a very low bit rate. With the FritzBox, I can set the bitrate with HEVC 10Bit to the highest possible value of 200 Mbits without any degradation. Believe me, I moved and shook the head and the headset very hard, everything remains absolutely stable. With this FritzBox and the Quest 3 PCVR via Virtual Desktop works without any problems. Even though the connection speed to the WLAN fluctuates here as well, this has no effect on the 90 FPS and high bitrate setting tested so far.

The FritzBox has an Intel Puma 7 CPU, so maybe this info is interesting for one or the other.

I will check how my PICO4 behaves with the 3 routers and report if interested.

All tests done with RTX 3090 and Ryzen 7900X3D.

tfosseliAuthor

Inspiring

Todays endeavor with TP-link https://www.youtube.com/watch?v=Dqi-ieY6aq4

R

Raison75

Up and Coming

Thanks for all your work on this, by the way. I just caved and bought both a TP-Link AXE5400 (based on several reports they work well with Q3) and also D-Link Bridge as a backup last resort. Looking forward to testing them tonight but won't get my hopes up.

R

Ruined

Inspiring

One feature request I have (and also reason I entered the thread originally) that would also improve wifi performance for some routers is 5.9GHz U-NII-4 WiFi6 band support. This would allow an additional 160mhz width channel on 5ghz for select WiFi6 routers, on a frequency range that will have no interference at all in the vast majority of installations (even less interference than 6ghz will over time) - and allows for range beyond what 6E's 6ghz offers at the same 2401mbps link speed. This would be a nice way to offer improved capabilities, as would WiFi7 for 4802mbps link, assuming the Quest 3 hardware is capable of one or both of these additions.

R

RagingBeard474312

Participant

When I put the Quest 3 on I frequently see a notification that it's disconnected from wifi. Usually it has reconnected itself, but sometimes I have to do it, and sometimes I even have to turn wifi on and off to see the SSID from the AXE75.

R

RagingBeard474312

Participant

Adding to my post above, my ISP router is actually always in the SSID list, whereas like I said sometimes I have to turn wifi off and on in the Quest 3 for the AXE75 to show up. So perhaps there's some AXE75 issue? 😞

R

Ruined

Inspiring

The AXE75 has been mentioned several times in this thread by people having problems, so yeah there is likely some compatibility issue with it and quest 3

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO