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

[W0IBC]

Broke down and got a new router. Went from Linksys 866/866 to Netgeart 1200/1200. SO FAR, I have had no loses  of connection. Knock on wood and we’ll see how it goes!

[W0IBC]

Seemingly have it solved….here’s hoping. In my case, a new router has been the answer…so far!

[W0IBC]

Looks like new router was the answer in my case!

[FrenchieBong]

Meta is absolutely horrible with their WIFI tech. I'm on tplink archer ax23 which is a pretty new model, i'm not even getting 50 mbps most of the time and any wireless link (steamlink or airlink) does not work at all and keep tearing my screen and a nightmare slideshow. Absolutely unplayable. I tested all my other wireless devices (phones, laptops etc) all are getting 400 mbps on my 1gbsp network. Just FYI, v67 on the quest 3

[RabidRaccoon]

Had my quest for about a week and a half. v67

D-Link router DSL-3890 on 5GHZ, have set it up so the Quest 3 has the 5GHZ all to itself.

First time I tried Airlink, 1200mbps and games were playable.
Not been able to get over 900mbps since then and PCVR over wifi has become unplayable. When I can get a game to launch it becomes a stuttering mess pretty quickly and usually completely crashes my PC.

I've tried Steam Link, Meta Remote desktop, OpenComposite and even bought Virtual Desktop.

I know it can work with my non-wifi6 router which can do up to 1753Mbps. I've seen it and played on it for 2hours at 1200Mbps. ONCE.

Got a lot of much cheaper wifi connected tech like my couple of years old VIVO Y12 phone, and it all connects at high speeds no problems. Only the Quest that is the issue

Paid $800aud for this thing and it cannot even do one of its basic features properly..... and seems Meta have known about this since launch. And I am expected to buy a completely new seperate wifi 6 router that may or may not work?

Cheapest wifi router where I live is a $150 TP-Link Archer AX53, and I've seen nothing but people poo-pooing on those. And even more expensive 'recommended' routers seem to be a lottery also. Seen videos of people saying "Meta Fixed the issue" on those fancy pricey routers, to then make an update in their videos comments that the problem is still there.

This shouldn't be a lottery. Paid $800 and cannot even play the games I want to play and own. Stuck with crappy Meta demos and Meta exclusive games that don't interest me. (So many games that are just clones of other games)

How much money are we expected to pay for accessories and upgrades are we expected to pay to make this thing half decent and functional?
Eats it's own battery super fast, cooks your face after using it for 5 minutes, has a crappy cloth strap they knew sucked from the quest 2. (and it's white.... even with clean hands that thing was filthy in a couple of days.) Yet some no name Chinese company can make a plastic strap that is better than the official upgrade straps for much less.... Even more pricey companies like BoboVR. Meta couldn't take a leaf out of their book when it comes to designing the Q3? Especially in terms of making the Q3 actually comfortable to wear out of the box.

This shouldn't be a lottery. Honestly thinking about returning this thing to Amazon and waiting until something better is available.

The way people rave about how good the quest 3 is, I have to wonder if we're using the same device.

Feels like some early access device, not something a billion dollar company with several devices and years of experience in VR under their belt have made.

Week and a half and I've barely been able to use it as intended. When it does work, it just becomes unbearable to wear after 15 minutes. But hey, that can be fixed if I give BOBO VR $150 just so I can have a half decent $5 cooling fan.....

I'm extremely disappointed. Got a new powered link cable coming this week. If that doesn't improve my experience, it's back to amazon with this thing.

Cannot even roll out updates properly. Maybe I'll get the v68 in 6 months if I am lucky.

Quest 3 seems to do a lot right in terms of hardware, but it does even more wrong where it actually counts.

Awesome spending money on what should be unnecessary upgrades instead of using that cash to buy games I can actually play and enjoy. Literally hundreds more to make this device what it should be out of the box for how much they're charging for it. and this is just the 128gb model.... so glad I didn't spend over $1000 to get the 512gb one now.

Pull your finger out Meta.

[D3ft0ne]

Hey yall.

Just posted this on reddit on r/OculusQuest.

Wanted to see what people are using in terms of their streaming network setup :  Direct connection to the main router via Wifi , or having extra dedicated VR streaming router set as an access point?  (And if you do have a dedicated router, set as AP, are you still seeing wifi performance issues).

---------------

My post - 

Would like a clarification on this, I am currently using AXE5400 TP link wifi 6e router as my main router for Quest 3

• Its directly connected to my PC

• Quest 3 is the only device on wifi6e SSID

• Rest of the devices are using 5ghz wifi6 SSID

• This router is in the play space (2m away from me) and i am still getting stutters and network lags when playing via AirLink or VD

---

I have an older Dlink router, which I can setup as a main router and wire it to Axe5400 (which will be setup as an Access point and connected to my PC via Wire and Wifi6e to Quest 3) ...

• Will this give me any advantage? As in - are other devices which are connected to my AXE5400 via Wifi6 - 5ghz taking up resources?

[nixt]

It's all a mystery to me.  I have the same router.  VD recommends setting up the wifi 6e router as an access point and only the Quest 3 connected to it although i have not done that yet.  I had been getting many stutters and lags, but i was only playing it with SkyrimVR.  Sometimes it would play ok (and i got used to ensuring i was facing the router while playing)  and other times i would constant stutters or even scenarios where it can't even pick up the 6Ghz to connect. 

Bizarrely, i switch to a different modlist in SkyrimVR - not as intense graphically, and i no longer have any issues at all. Have played for several weeks without a single crash, hiccup or stutter - even when i'm looking away from router.   So I'm as confused as ever as to the true cause of this issue. I was convinced it was a router thing, and maybe it is but it's weird that have such perfect connection all of a sudden. Not at all helpful to your question, but thought I'd share my experience. 

[Mister_Y]

Keeping on following this thread from the start, I am still so happy I went all in and got an GT-AXE16000 half a year ago (after previously trying various other routers with no luck). Even that didn't help right away, only since the v62 update it's finally good on 6 GHz (and only there). Used H.264 and now moved to AV1 in VD.

But recently I was shocked to find the lags came back, not a constant and extreme stuttering, but the occasional lag bad enough to make me miss in Beat Saber - which is extremely frustrating. I was about to blame the latest Meta update I had installed on the Q3 just before that, when I remembered that after playing the last time I had the FPS increased from 90 to 120. It came as a surprise to me that it was set to 90, I thought I had it set to 120 all the time but obviously I was wrong, so I didn't think much of changing it to 120, no big deal, right?

But once I remembered that and went back to 90 fps, it was immediately buttery smooth again and has been ever since - 8 hour gaming session without a single hiccup? No problem!

I don't know why 120 fps is an issue vs. 90, a 7800X3D with an RTX 4090 is certainly not hitting any limits at Beat Saber, but to be sure I once more tried 120 fps, lags came back, switched to 90 and it's fine again. But: 120 fps when wired is fine too!

I just had to think of this when I read your post, since it's also graphics settings that made the difference for me when you wouldn't expect it, and also only on Wifi, which confuses me a lot, especially since the bandwidth/bitrate stays the same in both scenarios.

Maybe Meta should have left 120 fps as an experimental option and it still isn't ready (or it never is because the Q3 just isn't up to the task). I wonder what fps settings others here are using.

[nixt]

Interesting. I can play SkyrimVR in 120 or 90 fps with no issues using Virtual Desktop H264+ at 500Mbps in Ultra mode. Before when facing away from the router, every single time it would drop from  2401 Mbps to 1200 Mbps or lower and spike erratically. When turning back to face the router it would lock back on 2401 Mbps quickly.  Now that i have reduced graphical intensity, I never see that happen. Not once.   Mind you there has been updates to the Quest 3 and i just had another update today, but I can't even figure out what Meta actually thinks about this issue as they never speak about it here that I have seen.

[CYAN_ure]

I don't get your post. 

1/ You're saying that you're using Virtual Desktop so your tests are biased straight away as VD is a third party software.

2/ You're saying that you were on 120Hz so I guess: In VD settings, right?

3/ You're saying that Meta should have left 120Hz experimental because the Quest 3 can't handle it. But... You're using VD, remember ?

120Hz in the Meta software alone works just fine (or as bad as the other refresh rates when the bitrate drops). Stop using VD, especially if you come here to post a feedback because it unfortunately becomes worthless due to the third party software usage. It's like saying "This car doesn't work well" after having modified parts in it...

You say it's smooth at 90Hz but maybe you still have bitrate drops. And since your WiFi 6E with 6Ghz band router max bitrate is very high, you just don't feel the drop but this is exactly what this topic is about: The bitrate drops issue, and you didn't tell us anything about your bitrate, if it's stable or fluctuating ( while turning the head fast, doing head translations horizontally, crouching...). 😕