(Not Resolved) Known Issue - Quest PCVR streaming micro lags and stutter esp. when moving head
Hi team, I'm getting micro lags and stutter in Airlink on my Quest 3 (EU/UK), esp. when moving my head. In the Oculus debug overlay this causes brief spikes in transmit/decode, fps drops and visible stuttering. The issue is not present on my Quest Pro with otherwise identical settings - see below screenshots to illustrate. Few more details: - Issue is not present on Quest Pro with same settings on HMD, router and PC (using same res) - Issue is worse at higher bitrates, esp. >200mbps, but still present <200mbps - Issue is unrelated to PC/game latencies (CPU, GPU, Queue each <5ms) - Stutters/lags are intermittent (every 10-20 seconds) when not moving but happen immediately and reproducibly when moving the head to either side or especially looking downwards (i.e. on any bigger headset movements) - Wifi 6E router (TP Link AXE75 EU/UK) - EDIT: exact same issue with Asus RT-AXE7800 (EU/UK) wifi 6e router - Connection shows as 2,400mbps - Airlink codec H264 (but same on other codecs) - I've attempted factory resetting, installing latest drivers - Updated to v62 and latest Quest Link desktop version (I can see the 120hz option for my Q3) - EDIT: Ordered a separate Quest 3 for testing: presents the exact same issue -EDIT: Same issue on 5ghz 802.11ax 160mhz BUT switching to 802.11ac (!) completely fixed the issue. I cant test this on 6ghz but looks like 802.11ax or something related to how q3 implements it is the culprit As the issue is worse the higher the bitrate and not present on Q Pro with otherwise same settings, I suspect it's related to the below known Wifi issues - but opening a new thread as instructed. https://communityforums.atmeta.com/t5/Get-Help/Known-Isssue-Unstable-wifi-coverage-with-Quest-3-on-some-Router/td-p/1090698 Best, Jens Updates: - Tried separate router: exact same issue with Asus RT-AXE7800 wifi 6e router - Ordered a separate Quest 3: exact same issue on both routers -Same issue on 5ghz 802.11ax 160mhz BUT switching to 802.11ac (!) completely fixed the issue. I cant test this on 6ghz but looks like 802.11ax or something related to how q3 implements it is the culprit
Meta Quest 3 Being stuck on update, for over 5 hours when powering off!
My Meta quest three that I have had has been great best purchase, except for about a month ago. About a month ago when I was powering off my headset from playing it had an update, so like any other person I waited a few minutes. Then 20 minutes came and I was curious so I checked on it, and it was still updating so I waited longer. Then after about 3 hours I was too tired and went to bed. The next morning I woke up and it was STILL updating, so I got tired of it and just canceled the update now I know it may have not been the best option but hold on. Then two days later I tried it again and a hour goes by and still the update wasn't done. It has made it so I can't play any games on it and it sits in my room for now, when I posted this it is updating and I will leave it overnight to see if it does something new. I will stay in touch though I will look at this post every week on Sunday to see if anyone has a solution for this thank you and bye.Resolved - Unstable wifi coverage with Quest 3 on some Router Brands.
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-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 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-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. 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-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 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. Router make and model. Router firmware. Full Headset version. (59.0.0.##) Settings > System > Software Update --- Here is my video on testing version 60
Meta Quest v55 Release Notes
These features and enhancements will become available starting the week of June 21st, 2023 and will be rolling out to Meta Quest Pro and Meta Quest 2 headsets. Quest performance improvements We’re continuing to move VR forward by pushing the boundaries of what Quest Pro and Quest 2 are capable of. With v55, we’re enabling higher clock speeds for the CPU and GPU for all Quest Pro and Quest 2 headsets, giving you smoother gameplay and a more responsive UI. This update also adds more power for developers to take advantage of for both existing and upcoming apps. These performance improvements include: Up to 26% increase in CPU speed for Quest Pro and Quest 2 Up to 19% increase in GPU for Quest 2 Up to 11% increase in GPU for Quest Pro Passcode We’re adding the ability to use a passcode to unlock your device, which will work like the unlock pattern. As this feature gradually rolls out, you’ll be able to set up a numerical passcode between 4 and 12 characters to unlock your device, enter saved passwords, and more. You’ll be able to manage your passcode from Security in Settings. Messenger in VR We’re updating the Messenger experience in VR to help you connect and make new friends while in the metaverse. With v55, we’re bringing the Messenger app, including messaging and audio calling to VR, so you can hang out with those who matter most regardless of which device they use. People you follow are online indicator You’ll now see a green circle on the People tab in the universal menu to help you know when people you follow are online. Explore redesign We’re gradually rolling out an experimental design with new content for the default landing page in VR, Explore, so you can effortlessly engage with your communities, compelling entertainment, and immersive experiences. A few of the Explore changes we’re experimenting with include: New layout formats Reels in VR Reels in VR will only be shown to users who have a Facebook or Instagram account in the same Accounts Center as their Meta account Meta Avatars Store Meta Horizon Worlds featured worlds Media content from Peacock, YouTube VR, Pluto TV and Xtadium Easier avatar editing in real-time We made it easier to travel to the mirror in your Horizon Home to edit your avatar. With just one click on the mirror, you will be transported and ready to view real-time edits to your avatar in an optimal position. This will be rolling out gradually. Eye tracking improvements We’ve improved eye tracking on Quest Pro to make it more accurate across a broader field of view and during expressions like winking. For the most accurate eye tracking, you can always recalibrate by going to Movement Tracking in Settings, then Eye tracking, then Calibrate eye tracking. Use hands on notifications We’re gradually rolling out a new way to interact with notifications in VR using your hands. With hand tracking turned on, you’ll be able to tap on icons or buttons, or swipe to dismiss a notification. New virtual environments We’re releasing two new virtual environments: Futurescape: As featured in this year’s Meta Quest Gaming Showcase, Futurescape combines futurism with the beauty and tranquility of nature. You can try out this new environment by going to Personalization in Settings. The Great Sand Sea: Available for download to all Meta Quest users who pre-ordered Asgard’s Wrath 2, The Great Sand Sea is a large, free roaming, living world that allows you to immerse yourself in the mysterious sands of a vast desert landscape in VR. Once you pre-order Asgard’s Wrath 2, you can download this new Home environment from the Meta Quest app or directly from your Meta Quest headset and then launch the environment from the Home screen. Browser multi-touch support Quest Browser now has multi-touch gesture support, allowing you to use Touch controllers or your hands to zoom in, zoom out, or interact with other web elements.PTC v55 Release Megathread
The Public Test Channel (PTC) for Quest v55 is starting to roll out for Meta Quest Pro and Meta Quest 2 soon. Thanks everyone for all your feedback on our previous builds, we several bugs were identified in the last PTC and the solutions for some have shipped, while others are on the way! Let's use this thread for collecting feedback on v55. Share your impressions and let us know if you see any issues. Please make sure to also send in bug reports along with posting here if you notice anything going wrong. We know it's tough when you run into a problem on a PTC build and want to thank you all again for testing out PTC and sharing your feedback! This feedback is extremely helpful to our engineering teams. We appreciate your interest and persistence in testing out the core functionality of software as we develop!
