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!
What are the changes with this? Like others have stated it would be nice to know what each release is bringing so we know what to look for. It's hard to debug if we don't know.
The point is if we know what we're supposed to be testing then we would go to that sections and test it, even if it's something that we normally would not use ourselves. Like I don't use the laying down feature, so when that was in PTC I would not have though of trying it or even looking for it to see if it has any bugs, and to test it for release, yes I would have used it for that purpose only. It's like telling someone you lost something and need help finding it but you don't tell that person what it is you lost or the vicinity you saw it last.
By the time people figure out some of the things in PTC, it's been released already officially. They obviously don't care that you know what changed, other then just download it and does it still run fine. That's all they probably care about regardless if you touch any new features lol.
I don't see a wrist menu button on mine and not even sure where to look for it. Which is why, again, we feel that detailed notes on what is being released and all is important.
@MoonstoneWolf7 I agree 100% it would be great to have detailed release notes with every release, I keep asking for this as well!
The wrist menu is in the Experimental section in Settings at the bottom but I had to power off completely and restart before it showed up for me even after the upgrade restart.
The Meta PTC is a complete joke, no one has ever gotten an answer regarding release notes from day 1!! The first I ever hear about what's new is from Tech Your tubers about 2 weeks after PTC release! I've seen many a video about multimodal mode, but not ever seen it myself. To be honest if you want to know what's new, just pick one the Apple Pro headsets features and water it down and that's what it will more than likely be!!! lol
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.
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.
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.
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!
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.
@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.
@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.
I don't know if this is new to v66. I did not experience it earlier, but then there's a few things that changed...or maybe this a Beat Saber thing. I added my wife to my Quest 3 account. My son was already on it as a sub-account. Now, if I run Beat Saber, it loads. If I quit and switch accounts (when I had 2 accounts on the headset), I could also launch beat saber on the 2nd account. Now, however, I'm finding with 3 accounts on v66, I have to power off and restart my Quest 3 in order to load Beat Saber on another account. It's like it's stuck in memory or running or something, but it just hangs on the initial load with 3 dots forever, cannot be exited and requires a headset restart.
My headset is going sleep during play now....remove the headset and putting it back give the image back, but there's no pause in online gaming as you know right?
The one controller and one hand feature has now vanished and it takes around 20 seconds to switch between hands and controllers when I put them down or pick them up again.
I have a quest 3, i have had no issues whatsoever with it UNTIL I UPDATED AND INSTALLED V66. Now my quest 3 is stuck on boot logo, unityx error pop up and immediately restarts by itself endlessly.
Am i seriously going to be forced to do a factory reset and just wipe out the 500+ gigabytes of data i have stored locally on my device?????How the heck did this update even go live????
I am on 66.0.0.488 and ising virtual desktop with a 6e connection on my quest 3 I get split second breaks in sound but using a 5ghz connection even though virtual desktop says it has a slower bit rate there are no split second breaks in sound. It looks to me this is not virtual desktop so i hope it fixed soon.
Hey everyone! If you're experiencing issue with PTC v66, I'd recommend making your own sperate thread/post about the issue as some posts can get drowned out here. By making your own post, @MetaQuestSupport will be better able to assist you with your specific issue. Before posting your own thread, please make sure that your issue hasn't be brought up before in it's own standalone thread. If that's the case, please respond to that thread with your specific situation. Thank you all for looking out for issues on the PTC and letting us know!
@WootM4ge@neurodivrgent do you guys actually bother to read the comments people post ? and if you do, do they fall on deaf ears / not my problem. I have had a quest 3 now since dec. On every single ptc release - all i see (quite rightly) is people asking for a list of changes coming up - so people can :-
1. contribute to providing feedback on whats changing
2. decide if they want to take the early release to perhaps see if it fixes an issue thats affecting them
3. to stop asking if x or y has been fixed in this up coming release - although reading the threads you can see the same issues cropping up time and again ie wifi drops (which i suffer from too but i used wired connection so not bothered). And I do wonder if these issues are actually being fed back to the devs ? Cos if they are there is zero communication coming back the other way to the community about when it will be fixed....
Here we are coming up to release 66 - and yet again no release notes / expected changes - how many more releases / planned PTC releases are you going to do without providing a list of the changes in it ?? Its like you guys just don't actually care about the community. So much so I will seriously be considering moving to pimax for my next purchase.
I agree totally with what you are saying and myself have asked the same question time and time again, until I realised why they don't give release notes in the PTC, They use it as a blind trial, with random improvements & fixes set to different regions!! ie: they will release a several different versions of a fix to different regions and see which one works best before adding it to the final release! I can almost prove this is what is happening because reading these threads you'll notice some people with the same headset will have different issues with the same update??? If it's the same hardware and same software surely the SAME problems will occur?! As for why they are doing this is another question, which I believe is due to fragmentation within (Facebook) Meta and departments haven't a clue what another is doing!! Yet again proof of this is right in front off you now, as when I log in to this to add this comment it asks you to log in with a Oculus account!!??!! (Which is still valid btw but I moved all my details to meta nearly 2 years ago) and still a lot of web stuff is under the name Oculus and not Meta which change over 2 years ago..
I applaud Meta/Oculus/Facebook or whatever for there investment in VR and MR but for crying out loud get your house in order first...!! It's a friggin s**t pile!! I don't wanna have to login 3 times when I move from Meta store to Help to Facebook in a single session!!
A/B testing can only be done when you "know" what you are doing. Randomly changing lines of codes does not work. Whoever thought this is a good idea, should go and water plants instead.
The purpose of Bug-Fixing, and I'm not talking here about UI optimizations (e.g. a button placement to increase clicks), is to fix bugs and not end up with more bugs of unknown origin. all builds are v66 and users come back with v66 does not work. So there is no way that this system could ever work with random fixes.
Delivering stable builds, fixing bugs, improving and meeting cadence targets is all established and optimized and known to all professional software devs and product managers. Putting out anonymous builds is pure nonsense and shoudl be penalized.
I just got another v66 Update, QuestLInk is **bleep**tier than before I had v66 - do you see where I'm coming from?
On top of this, users show different UI settings and features in youtube all over the place. It just makes no sense and someone in charge should really swap out the Product Managers and the whole AGILE abomination of a software development concept at Meta.
These features and enhancements will become available starting the week of June 3, 2024 and will be pushed to Meta Quest 3, Meta Quest Pro and Meta Quest 2 headsets.
Meta button on wrist
When using hands, you can now add a Meta button to your wrist to easily open the universal menu by tapping it or recenter your view by holding it down. You can also use the Menu button on your other wrist to bring up the current experience’s in-app menu. You can try out this feature by enabling it fromExperimentalinSettings.
Background audio and media controls
You’ll now be able to launch a music app and listen to music while playing games or using other apps. When background audio is playing, you’ll see a new media control bar under the universal menu to control music playback. Press on your right Touch controller to bring up the universal menu and media control bar.
Family Center updates
Teens and children supervised by the same parent or guardian will automatically be able to see each other in Family Center.
Improved passthrough and mixed reality interactions (Quest 3 only)
It’s now more natural to interact in mixed reality on Quest 3 with significantly reduced passthrough distortions and improved hand alignment.
Hide apps in Library
You can now hide any app (installed or uninstalled) you’ve downloaded from the Meta Quest Store to help clean up your Library. You can see apps you’ve hidden by selectingHiddenfrom the dropdown menu in the top right.
Space Setup automatically captures furniture
Space Setup will now automatically identify and mark furniture in your space to improve realism for MR games and apps. For now, this will work for windows, doors, tables, couches, storage, screens, and beds, with additional furniture types supported over time.
Meta Quest gallery on web
You can now sync media from your headset to your Meta Horizon profile, allowing you to view your Meta Quest gallery on the web. Log intometa.com/gallery/questto view content you have captured on your Quest headset.
Sleep mode added to power off menu
When you press and hold the power button on your headset, you’ll now see an option to put your headset to sleep. Putting your headset to sleep and leaving it plugged in allows your headset and apps to update in the background, keeps your battery charged, and significantly reduces the amount of time it takes for your headset to turn on.
After my last post about missing improvements has gone unanswered ! (Surprised Not!) after 2 years of being in the PTC I've decided to leave and go back to regular builds in the hope that I will get the mentioned features in the future, I would encourage everyone to do the same because like everybody else in the PTC we were completely in the dark as to new features that each PTC build had in it, with many a users headset becoming unusable. Different builds released to different countries, reported issues never being sorted out, no idea as to what has changed and what needs testing? Need I go on as to the total **bleep** show that the development team is ? Where is the discord server for this ? Most every software development has a discord thread going! We are being treated like blind mice and this needs to stop and the only effective way meta will take notice is for everyone to just up and leave the PTC as this would leave them with zero feedback and have to start testing there own software or at least setup a proper beta test group with direct commination with the development team.
In the immortal words of Douglas Adams... "So long and thanks for all the fish"
I know I've written this before but this program is disgusting. They finally put up the release notes. And I don't have any of the new features yet. I've been on V 66 for 2 weeks. Who the heck is running this program?
Since PTC v66 rollout and now on the latest public on i`m experience lagg in tracking and glitches in graphics after som video playback in the browser! (Netflix) it all starts ok, but som time in to the video it starts to miss frames and jumpy if you move your head. If i quit the browser the issue is still there, only way to get back to normal behaviour a reboot is needed. But it Will get back after looking/streaming a video! Some while graphic noice is also seen in the video is i move my head.
my feeling is that there are som resources eaten up, or a memory leak causing lack of resources to handle the other system functionality for tracking headset or decoding the video.
i have notice this mostly on the Meta Quest Pro. (Did also file an incident feedback)
Any one else seen it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
