Inspiring

PTC v66 Release Thread

39 replies
17747 views

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

The Public Test Channel (PTC) for Quest v66 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 v66 jump on over to our Get Help board and search for any existing thread, if you don't find one, make a new thread. Please add the tag "PTC v66" to the thread and in the title. This way everyone can look for just PTC v66 issues too.

It's best if you can post each bug you spot in its own thread, to keep track of individual issues separately.

Share your impressions 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!

Show previous replies

O

Ovrtaker

Participant

Bug report: The Quest Pro controllers sometimes don't work at all when waking up from sleep on my Quest 3. It happens probably 50-70% of the time and is very annoying.

E

EdwinBraun

Participant

Can you please explain what the idea is behind sending out a release without explaining what has changed? This makes no sense at all. I'm a Developer and Product Manager, if we were to output anonymous builds we would get so much flack and fire.

Seems like a small company like meta , does not have enough staff to document software changes.

Take this as feedback to improve on the rollout cycles and getting better and faster feedback form your user base. I'm sure you are on an AGILE software development method, and collecting user feedback in the shortest amount of time will ensure a proper cadence and overall satisfaction in the user base.

K

KermenTheFrog

New Participant

The wrist buttons work amazingly I'm surprised that this wasn't previously a thing.

It would be great if this would enable just the wrist buttons to be active instead of both wrist and pinch to bring up the menu.

This could allow developers access to using hand gestures that weren't previously available and would help with users accidentally pinching to bring up the menu when they don't indeed to in apps and games.

NicoEng

Up and Coming

An option to turn off pinch gestures would be great.

MetaStoreHelp

Community Manager

Hey KermenTheFrog, We’re just dropping in to thank you for taking the time to share your insight on how to better improve the VR experience. We would love to make sure your views and suggestions get heard properly. With that being said, if you haven't already visited our Ideas Forums section to submit your thoughts, We hope this information is of use to you. Have a legendary rest of your day!

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

nalex66

Honored Contributor

I just got v66 today, and I've had a repeated bug. Sometimes the Quest Link button in the Quick Menu says "Not connected" instead of listing my PC. If I click on the Quest Link button, the interface freezes up and the menu disappears (including the universal menu bar). I can hear the menu sound when I click the right controller menu button, but it doesn't return to view. I have to restart the headset from the power button menu to get the Quest UI back. I've sent a bug report from the headset.

DK2, CV1, Go, Quest, Quest 2, Quest 3. Try my game: Cyclops Island Demo

O

Ovrtaker

Participant

nalex66that bug is not related to the Quest Link button as far as I can tell. It happens all the time on my headset under normal use. Sometimes the settings app crashes and then the UI vanishes until reboot, sometimes I just put the headset on and the UI vanishes until reboot, sometimes I exit a game and, well, you get the point by now.

nalex66

Honored Contributor

Ovrtaker Well, for me, the freeze-up definitely seems related to the process of detecting the nearby PC after the headset wakes from standby. Usually the PC name pops up once the headset reconnects to WiFi, but sometimes it doesn’t. In those cases, I can still use the UI, until I touch the Link button, or try to go to the Link page in the Settings menu. Then, I’m stuck. Happened several more times yesterday. One time I left the power menu and the UI reappeared, but it was still frozen, with a blank menu page just showing the Settings icon.

DK2, CV1, Go, Quest, Quest 2, Quest 3. Try my game: Cyclops Island Demo