Skip to main content
neurodivrgent
Inspiring
July 15, 2024

PTC v68 Release Thread

Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v67 and the solutions for some have shipped, while others are on the way!

The Public Test Channel (PTC) for Quest v68 is starting to roll out soon for Meta Quest 2, Meta Quest Pro, and Meta Quest 3. 

If you're seeing an issue or bug after updating to PTC v68:


1) For issues: Go to our 
Get Help board and search for any existing thread on the issue, if you don't find one, make a new thread. Please add the tag "PTC v68" to the thread and in the title. This way everyone can look for just PTC v68 issues too.

2) For bugs: If you come across a bug, please post each one you spot in its own thread, to keep track of individual issues separately.

Share your impressions in the comments below and let us know if you see any issues.

Please make sure to also send in bug reports along with posting on the forums 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!

125 replies

New Participant
August 4, 2024

I’m a bit hesitant to factory reset because I don’t want to lose all my apps and videos. I’m looking for a way to adjust the microphone input volume without having to go through the hassle of a factory reset. Any suggestions?

New Participant
August 4, 2024

I’m super excited about the microphone input levels setting because it’s going to make a huge difference in my VRchat experience. I’ve been having a really hard time hearing myself in VRchat, and it’s been really frustrating. I’m hoping this setting will help me get a better volume.

Participant
August 4, 2024

Not even the so called community manager has posted since starting this thread 3 weeks ago! neurodivrgent 

I think what bugs me the most is the handling of te PTC/Beta program. I mean, the point of being part of the Neta is that users like us will test pre-release versions and provide feedback. But there is absolutely zero participation from anyone on the Meta team. nobody addresses our concerns/feedback directly. Nobody provides updates. They make the opening post, and then it is radio silence from the Meta team.

To me, that is just plain disrespectful to those of us willing to deal with bugs in the software to help make it better. 

I am strongly considering removing myself from the program. Not because of the bugs. but because of the lack of appreciation Meta is showing beta testers. If you do not appreciate the contributions we make, why should we waste our time and deal with things breaking?

Inspiring
August 5, 2024

My Quest 3 headset is still a paperweight after your last update.

How do I get this version 68?!

I tried over the weekend again to boot my headset and it is stuck in a loop when powering on. Did this since an update was pushed about a month ago. I've tried to sideload in the past and it did no good. Is the sideload option now pointed to pull v68 so I may have a working unit?

Inspiring
August 5, 2024

Just as an update, tried to sideload update...still broken. Spinning META logo (08/05/2024). I'm not going to send my new unit back for a used one.

It would be a miracle if they ever actually sent me a return label.

Electronic Express won't exchange because the one year warranty is not up; have to deal with META. 

Guess next step is just take back to return and just give me my money back. So tired of fooling with this nonsense.  

Up and Coming
August 5, 2024

Adaptive Display is not in my experimental tab and voice commands not working.  In fact the last update borked the microphone and I can't use the mic anywhere.  

New Participant
August 5, 2024

Since the first PTC update to v68 and now that the official update has come out, the controller disconnection symptom has been very inconvenient.
I did a factory reset a few days ago due to this symptom and tried reconnecting the controller, but the symptom occurred the same way.
What is clear is that this symptom has never occurred until v67, so this symptom is definitely caused by v68, but there is no sign of it being resolved in Meta.
If someone buys Quest 3 at this point, he will likely put the device on the second-hand market with a complaint soon, which will most likely lead to a decrease in purchases.

 

Participant
August 5, 2024

TheRealKrom 

I had this happen when I first ran the update. If you have not already, try doing this (it worked for me):

Make sure the headset is fully powered off.

Boot into the boot menu (power+vol -)

Select the boot device option

This should allow it to boot. Once you are booted into your headset, restart, making sure that the install updates option is selected. 

Let the device apply any updates and fully reboot. This might take awhile (took about 40 minutes for me).

Now power the device off and then try to boot in the normal way.

This process worked for me, so hopefully it will for you (and anyone else having this issue) too.

CEO, Host Magi Inc https://hostmagi.com
Up and Coming
August 5, 2024

Add one more.  I didn't have the problem with one of the controllers dropping until a moment ago.  And I have tried everything that is suggested this.  Add another paperweight to the list of others on here.

 

Inspiring
August 5, 2024

How do we file a class action lawsuit against Meta?! This is ridiculous!