PTC v68 Release Thread

Why is there no hotfix for the Controller going sleep/cutting out/overall tracking issue?

Some ppl say thats not related to v68? Only because he dosen't have the Issue? Well you are wrong.

I recomment pretty much everyone who watch my Stream to upgrade on v68 because the performance boost was insanely good and the first 2 Days it was fine but then you  updated the version (like 150 mb) and it starts struggle like crazy. 

Pretty much everyone had the same tracking issue like me (told me in chat)

+Sometimes i can ONLY cold start the Quest 3 (15 seconds push of the Power button)
++AIR LINK STILL NOT WORKING++ OVER A YEAR NOW 
Always lagspikes when i move IRL after version v55 or so it starts and i never found a fix for it.
++++DEBRIS IN USB IS STILL THERE++++ <---- Makes my Quest3 not Counter charge. (restarting the Quest3 solve the issue and comes back when you above like 80%

so stop developing AVATAR / AR Stuff nobody is interested in and start fixxing THE CORE ABILITYS of the Quest 3.

Thank you 

i am pissed 

Pwn1

I have the issue with 1 controller too. Just FYI, I discovered that you can get it re-connected by removing and reinserting the battery.

"I am pissed"

What, you mean you expect something to work when you pay $650 for it!?!? Not to mention the ongoing costs of software and subscriptions???

Although working for my particular use case (MSFS), the performance of the updated OpenXR runtime seems to be reduced. (Alongside the known bug with other OpenXR API Layers)

My non-PTC/non-beta just updated on my QPro (v68.0.0.507.364) and meta-link pc app (v68.0.0.474.361). All’s working very well with my QPro/rtx4090 using Link (without OXRTK). Actually seems to work slightly better but it might just be a placebo thing, lol!  

I still haven't got this non-PTC on my Q3 yet and still no new V68 Release Note Thread.

As far as I know there is no non-ptc v68 yet. 

wolfabishop Yes there is.  As I said, I got this earlier today.  Like all meta updates, these get rolled out so you may not have this yet.

After reading what everyone else has said so far in the thread, I think v68 might be giving me the same controller issues. I'll post my issue just for datas sake in case it isn't.

Essentially, they'll work for about 5 minutes on initial startup but then start cutting out every couple of seconds, can be either the left or the right controller.

What happens is:

   1. The controller will disconnect (status light on controller turns off, quest 3 doesn't show controller, practically off) then...

   2. It'll reconnect (status light turns back on, virtual controller snaps back into view on headset, tracks and behaves like normal).

   3. This will happen multiple times in less than a minute. But after a minute or 2 of that, they sort themselves out and everything will be good for another 5 minutes only then to start the loop all over.

I've tried replacing batteries (ive got lithiums in them if that matter, only mentioning because I seen another thread mentioning putting "good alkalines" in, of which I have none), ive done the re-pair shuffle, factory resetting the controllers with the "X/B button held down, menu button 5 times" trick doesn't work, reapplied the update with the software update tool, etc.

Im at a loss at this point, im pretty sure its not a hardware failure at this point because 24 hours before my issue occurred, I had zero issues over the course of a 7 hour play session and had placed my controllers in their normal spot, so i can only assume the v68 firmware update on either the controller side or headset side has caused this.

After the V68 upgrade on my Meta Quest 3 last night (8/2/2024), it failed to connect to the right controller.  Trying out the new battery, power on/off not fixing it.  Today I tried to use my Meta Quest 2 as backup.  The same thing happened and it also failed to connect to the right controller.

wolfb1978 I’m still having the same issue. The voice input level entry has no setting problem. I’m a bit worried about it, so I’m considering factory resetting my Quest 3 to see if it’s a bug. What do you think?

That could help, as long as you have a backup. But that should resolve things.