I've also noticed if I cover the front cameras that the issue is not as persistant.
3 friends of mine that I talked avout the issue (including the one in front of me in the video) are experiencing the same issue. There's Quest Pro's being sold for cheap because people think it's a hardware issue. It's most likely not. This is a expensive headset and a update like this should never be pushed!
Does anyone know how to revert it? Or a work around
I have tried Factory Reset, clearing up my playspace for optimal tracking, cleared the cache etc, nothing works.
for reference: i use 4-6 lighthouses, depending on what im doing, alongside 11 lighthouse tracker, index controllrrs, and the quest pro connected to pc via virtual desktop. im also using a vive facial tracker as well via virtualhere to throw a spanner in the machine.
- every 20 or so minutes, my vd stream would lock up and the hmd would lose tracking.
- after losing tracking, the horizonos ui would fail to load, but noises still play.
- the hmds slam tracking would also get confused and throw me around the pkayspace
- after either of these two events would happen, tracking resumed to normal
the fix i believe i have found, is to simply force region tracking rate (in my instance 50hz (settings > system > headset tracking)) and to disable hand tracking.
this seems to bring enough load off the hmd for it to function properly!
this also did NOT happen on v68 and below, with this happening on v69 only (latest as of writing) which is the multi window update.
hope this solves your guys' issues and gives a good lead for metas team to resolve a fix 😛
3rd October - Thanks for hanging in there with me folks. I'll be collecting all the information we currently have here and marking it as a solution for the most visibility. Once I have an actual solution, this post will be updated.
13th October - This issue has now been resolved and a fix was implemented in PTC v71. Please enable the Public Test Channel to receive this update.
Current Status - Fixed (in PTC)
The information you all provided me has been passed on to the relevant team for further investigation.
Reporting
If you are encountering the same issue as the rest of the users on the thread, please leave a reply with the following information:
- Quest Model: - Quest Software version: - The exact error message you're seeing: - Are you using PCVR or just standalone?: - If using PCVR, are you using Air Link or a Link cable or a different service?:
Workaround
A fix for this issue has been implemented into PTC v71. If, for some reason, you are unable to update to PTC v71, please disable Hand Tracking as a temporary workaround to the problem.
We're happy to hear you have picked up a Quest Pro and have used Mixed VR to enjoy our Meta Quest. Sometimes, when there is a Third Party involved, we cannot guarantee that the experience with your Meta Quest will be as optimal. However, feel free to check on our latest software updatesand submit a bug report.
For any more queries, do not hesitate to reach out, we're always happy to help.
Talk soon!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
I couldnt exactly point where the issue is being introduced, but for me and friends simply covering the cameras that are pointing towards a base station fixes it.. Playing without the bases works just fine, just super odd to have to put a tape on top of the headset ;/
Im guessing its a issue with the sensitivity of the camera or something related to that, because its getting crazy with stations
09-28-202411:26 AM - last edited on 09-28-202411:28 AM by KaminasWife
I'm also using a mixed VR set up and having the same issue after the update, and know several people with the exact same problem. Will there be a patch for this issue soon?
Hey @windshields, we assure our technical team keeps an eye on commonly occurring bugs in new updates and we intend to get them fixed for our customer's to have a smooth experience in the world of mixed reality!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
I'd also like to chime in and mention that I'm having issues with my headset repeatedly losing tracking.
I have never once had this issue until I updated to v69. My VR space hasn't changed and my lighting hasn't changed either. I reset my boundary completely in an effort to see if that fixed anything, but it had no impact.
The setup I run is utilizing the Quest Pro with lighthouse basestations in the same room. I'm not sure if that's a compounding factor in all of this or not.
Either case, I'd be more than happy to provide any further details I can, but this has been a very frustrating experience, of late, to say the least, as things went from 100% stable to frequent interruptions.
Your lighthouse base stations may be the root cause of your issue, as I understand they can negatively interact with the IR cameras on the Quest Pro. If possible, I would recommend using the device either in a different play-space or altering your current play-space and seeing if that resolves your issue.
If this does not fix your current tracking issues, I would recommend getting in touch with support by clicking hereand sending them a Private Message.
09-28-202405:22 PM - last edited on 09-29-202406:19 AM by KaminasWife
There's hundreds of thousands of people using a Quest 2, Quest Pro, or Quest 3 with basestations with zero issues--and I'm no exception. I've had zero issues with something like this since 2022, but it's suddenly cropped up as soon as the v69 update came out.
I don't think the basestations are the actually issue--the software update clearly is.
09-29-202408:58 AM - last edited on 09-29-202409:06 AM by KaminasWife
Me and three friends have had the exact same experience after the latest update. I use Ultimate Trackers which don't use base stations and still have this exact same regular tracking lost issue that just started after the latest software update.
I am not using base stations, and have experienced this same problem since the v69 update on my Quest Pro. This is *not* exclusively a base station issue.
Please note that we will be upgrading the community on July 9, 2025. The community will be down for a few hours while we perform this upgrade. For more information, please see Community Upgrade & Downtime
