Meta finally fixed the Quest 3 Wi-Fi stability issue with Build v.62

Published 2024-02-07
After five months, we can finally say that the Quest 3 is a very good wireless PCVR headset for any Wi-Fi 6 router. The TP-Link AXE5400 (AXE75) works smoothly now, but there are still some kinks to work out.
www.amazon.co.uk/TP-Link-AXE5400-OneMeshTMand-Home…

This is the final video in a series on this issue that has been running since the launch of the Quest 3.
   • The Quest 3 Wi-Fi stability bug  

The forum thread that moved this issue forward:
communityforums.atmeta.com/t5/Get-Help/Known-Isssu…

Have problems finding and connecting to your 6G?:
Figuring out why the 6GHz network isn't showing up can be a bit tricky, especially since it seems to be affecting only a handful of TP-link AXE users. Here's a roundup of what people have shared to help troubleshoot:

- Ensure your router is running the latest firmware through the Theder APP.
- Run a network diagnosis to rule out any channel conflicts: Theder APP - Tools ➡ Network Diagnostics ➡ Diagnose.
- Confirm that the 6GHz network has a unique name and passkey. (preferably 8+ characters with only numbers, letters and underscore)
- In the Theder app, access advanced settings for the 6GHz WiFi and activate PSC. Ensure "Hide SSID" is not toggled.
- Be patient! Give it 3 to 5 minutes on the WiFi settings page on your quest and see if the 6GHz magickly appears.
- Add the network manually. Write down the Name, Security protocol, and passkey (e.g., TP-link-VR6G, WPA3-Personal, passw0rd23), then manually add the network on your quest without scanning.

Additional Experiments:
- If 2.4GHz and 5GHz are disabled, try turning them back on and se if the 6GHz network also appears.
- If Smart Connect is disabled, try enabling it to see if it resolves the issue.
- If OneMesh is activated, consider deactivating it as an experiment.

Connecting to 6GHz Network but disconnects randomly:
- If you manage to find the 6GHz network but experience disconnections:
- Head to the Wi-Fi connection settings on your headset. Under privacy, choose "Use device MAC."
In the TP-link web client you can try giving it a fixed IP using Network ➡ DHCP Server ➡ Address Reservation.

All Comments (21)
  • @ChapC_YT
    Im happy they fixed it, but I am still annoyed by the way they treated my support tickes, chat and e-mail. They avoided the issue completely, treated me like a dumb child and only resorted to 'try restarting your router' answers and asking me if i want a replacement model. Why is it so hard for companies to be honest, admit to internal struggles and simply involve us. Gosh, customer support can be so annoying.
  • @freds690069
    It only took 5 months and hundreds of forum posts, but we finally got a fix! My v62 results mirror yours.
  • @jamiet4201
    Thanks very much for making these videos! I messed around with a Quest 2 and Virtual Desktop around 2020, but wasn't very successful and eventually returned the headset. I've copied your setup with a used Quest 3 and TP-Link AXE5400 router and have been having a blast playing through Half Life: Alyx today.
  • @mikemagruder8444
    HALLELUJAH!! Thank you for these videos and your thread on the forum that drew Meta's attention to this issue.
  • @raheenb
    Oh good, they fixed it after I spent hundreds on a new routers, TV, and GPU because the wireless experience was so jacked lol. Thanks for all your help with getting this finally fixed!
  • @Neawoulf
    Thanks for the update. Looks good! Took a bit too long to fix this, but better late than never. I tried the new patch as well both with my router and that d-link stick and it's a lot better now. I can play fine with low bitrates now, but high bitrates are still stuttery with high latency. Guess i need a new router. I was hoping i could wait until wifi 7 routers are a bit more common and affordable.
  • Regarding the Quest 3 taking a long time to connect to a 6e router, I was experiencing this with my AXE75. It would often take minutes. But I learned from a reddit post that enabling 2.4 and 5 wifi modes (I only had wifi 6 enabled) on the router makes the Quest 3 connect to the router (via 6e) much faster. And this worked for me.
  • @JeffreyBlakeney
    Good to hear that it is working for you now. Another difference in our setups is that you have over 10 times the users on your router than I have on my 5 GHz router. I have myself and my room mate using my router and still have to reset it about once a month because it gets messed up. The more concurrent users, the more likely the router won't have time to deal with everyone at full speed. I have been ill on and off the past month while still being busy so haven't had a chance to set up my 6 GHz router yet but I'm hoping it will solve the little lag spikes I was getting from time to time on fast moving graphics.
  • oh, we have the same graphics card and same wifi router, maybe I should get the update and try my results as well. Thanks for the update video I haven't had any wifi dropouts while playing at all, but I did notice the speed fluctuations earlier on v60
  • @SaysSim0n
    thank you for your efforts! working great now! Since you are the man that gets things done around here I got a suggestion for you. Bluetooth latency is awful and ppl are forced to used wired headphones. Maybe you can get something rolling on this front as well. Just an idea
  • @iamone_
    Same here mine is also rock solid at 2400 and i use my default ISP wifi 6 router that is 6m away from me. The only thing i had to fix the channel number. I used wifi analyzer app for that and pick the one that is not used. Everything is so fluid now without stutters.
  • @kelownatechkid
    This is excellent news! Thanks for your help to the community with this.
  • @t3chnod3lic
    Great news and huge thanks to you for bringing this to Meta's attention. Probably wouldn't of been fixed otherwise. Shoddy service by Meta though. I'm still puzzled why this issue only effected some and not all users. It's all the same hardware/software? Oh well. Three cheers! 🍺🍺🍺
  • @traveller6713
    thanks for documenting the issue for everyone! I had fluctuating connection speeds with v60 and after updating to v62, I've enjoyed a stable 833MHz up/down (which appears to be the max speed with my 802.11ac / 5GHz / 80MHz connection. I recently built a new rig based on a Ryzen 7 7800X3D & RTX 4070 platform, so I wanted to push the limits of my PC and see if the WLAN could keep up. Setting VD to Ultra / 72fps* / 200Mbps / SSW disabled / VDXR / AVI 10-bit, I managed to enjoy several games with the ocasional stutter (network-related latency every time). This was ok for everything except for Beat Saber - even with a stutter only occuring once or twice in a 3min song is enough to mess up the score. *I'm one of those that doesn't need 144Hz+ refresh rate and have been quite happy with anything above 60Hz ... ymmv 😉 Thus I will look into upgrading my WLAN - either via a WiFI 6 Extender (€) or going with a "modest" 6/ 6E Router (€€). Regarding a router; There appears to be two paths to follow; either sticking to 5GHz (4x4 160MHz for 4804Mbps - example, "Archer AX72 Pro") or splitting it up between 5 & 6GHz (2x2 160MHz for 2402Mbps in each band - example, your Archer AXE75). I'm not certain if 4804Mbps will ever be needed (not to mention it will certainly require DFS channels) and there is an arguement for 6GHz as I would be the only person in my building using 6GHz, which is still in the "enthusiast" sector and not used by the typical household. My only concern is all the comments below from posters that are having issues with 6GHz... (naturally they can fall back to 5GHz with a Router like the AXE75 which offers 2402Mbps in BOTH bands). Recommendations are most welcome 🤗 Last but not least, a few screens (assuming I'm allowed to post links here...): 1. A beat-Saber run with Networking latency documented https://live.staticflickr.com/65535/53572793769_8b94bb3974_b.jpg 2. SteamVR-only game ("After The Fall" - purchased via Steam) with good results (the occsaional dip every ~120s or so, max) https://live.staticflickr.com/65535/53571624822_1fbcfd128c_b.jpg
  • I had a couple of issues with my Quest3. One was with Wifi which seems to be fixed now. The other was with the quality of pass through. For me pass through was never better than the camera of my 15 year old smart phone. In your video pass through looks like very nice HD camera. Some people in forum complained about recorded pass through looking better than it does in HMD. Does the pass through quality in the video reflect what you see in your Quest3? No grain? no flickering? (except the distortion at the edges)
  • @86themadhatter27
    That's interesting. I remember setting up my TP AX1500 at the beginning of this year, my router sits on my desk while i game and i would notice it often dropped from 1201mbps to maybe 900, sometimes even less. I was blaming it on my racing rig, that maybe having 4 different devices infront of my like steering wheel, fan, handbrake, shifter was causing an issue. So if this update smoothens this out then awesome. I'm stil on V60.000. Looking forward to image quality getting a little hazy when doing like 120mph on a rally stage.
  • @jornaggror
    Thanks for the hard work all these months! So is this router replacing the default router from your ISP? Or do you have it specifically connected to your pc? If so, how are the the ethernet cables connected and are you using Cat 6?
  • @FitzeVR
    They certainly have been stable 2401 for last five days , never dropped since been on PTC V62
  • @grumpywolfgaming
    Awesome, I'll make sure to update my quest tonight and see if this worked for me. Glad to see my review of the poor wifi was justified and all the people saying it was my networks fault can suck it :P