PTC v66 Release Thread

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, MetaStoreHelp 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!

I just wanted to ask when is modding coming back as I'm on v66 and don't have it

Removed the background sounds option for 2D applications from the Experimental tab. 😡

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!!