Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v64 and the solutions for some have shipped, while others are on the way!
The Public Test Channel (PTC) for Quest v65 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 v65 jump on over to ourGet Helpboard and search for any existing thread, if you don't find one, make a new thread. Please add the tag "PTC v65" to the thread and in the title. This way everyone can look for just PTC v65 issuestoo.
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!
On v65 and scoped storage is still unfortunately present.
Now when going into the power options (while in passthrough), instead of being in a gray VR environment, you stay in passthrough. When in VR environment however, you still get put into that grey place.
Wifi refresh cannot be disabled anymore in the experimental settings.
Hey MrBIO, there was a fix published in v63 for the issue that PTC users reported regarding scoped storage. The fix gives developers the option to allow access to scoped storage for their apps.
@Ryanality So you are able to access the files of the game on device only if the developer specifically allows it? I only have access to Android\Data and after that it wants access from the android file manager which doesn't give it because of scope storage. Is this only on my device?
Zero changes as far as I can see ? apart from the version number ! maybe under the hood change ? but what is strange or concerning depending how you look at it is the fact that normally my Quest 3 gets updates after my Quest Pro ???? So it looks like the end of the road for feature updates for my YEAR OLD QPro only a few bug fixes now again, before being consigned to the junk pile of tech!
I am on ptc and didn't even get the option for v65. Guess it's filled up but my passthrough from v64 is horrible. And I"m in a room with a ton of ligh as well as sunlight coming in. Not that normally it matters but if I decide I want to follow a new recipe I would like to be able to see properly.
Don't even bother opening a ticket. They'll just say they see nothing wrong with it even though the phone in your hand has a white out and you can't read unless you dim the phone.
And I even sent the the requested video showing that I had to dim the brightness on my phone in order to read it and "Your passthrough looks fine". Wasted an hour trying to get a video that yahoo would send to them.
Updating my older Quest 2 last eve... V65... Possible issue with Multiple Accounts?
On restart I see the quest logo spin... three dots overlaying passthrough... then nothing. I hear the menu rise up down but nothing displays UI wise.
Power Button reveals power down menu. And something I get lucky with controllers hitting the LOGIN of select account. Seems broken sorry if no more info to share but something I noticed. Yesterday update.
I finally got the PTC V65 and the halo affect in passthrough has not been resolved on my end. The same with videos being blurry and distorted. I took videos showing this and Meta sees nothing wrong. Didn't they themselves say that passthrough would be improved? And please don't say I need more light, I have lights at 1100 lumens coming from all directions, even when the sun is coming in the windows.
Has this fixed the issue with the battery saver mode being stuck on?
This should be top priority for Meta given how many people have been affected and pretty much have had their devices "bricked" (not literally bricked, but permanently downgraded to low res with no fix).
Not keen on this update, getting weird halo effects with pass-trough so looking something can look shaky, it affects UI elements so they ghost if you look at them... The pass-through quality doesn't have the quality that V64's PTC had, seems like a backwards step.
Finally, had my WIFI drop out on this update a few times now which wasn't an issue in prior builds.
Thanks for the reply..sad to hear that. Wi-Fi instability is a big deal-breaker for me. I’m going to give them a little more time then I have to move on. I have blazing internet and a beast router..none of that matters if the headset is dropping signal 🤦
Ryan, can you find out what is happening with this v65 ? I received the update 2 weeks ago now, and nothing has changed ????? No rumoured Flight Mode, no multimodal mode, no object detection in room scanning, no placed objects in MR, nothing at all not even a single visual tweak !!?? Come on throw us a bone here! Or are you keep totally in the dark like the rest of us ?
How can people test a release when you give them no build log, you don't tell them what's changed per any updates or indeed what they should be looking out for?
How many times do we need to tell you the same thing? Is anyone reading this?
While the passthrough is still horrible, and videos still terribly blurry, and I most likely won't use, the laydown mode is fixed so you can enable it and it won't be crooked or anything. That's all I can see though.
After playing with this for a week the passthrough is still horrible but the video blur has greatly improved. I never had the issue of being disconnected from my wifi so I can't report on that part of it.
How come, you tube reviews show multimodal (one hand and one controller) as part of V65 as I've had all the latest PTC versions of V65 on both my Q3 & QPro and neither have this ? Has anyone else got it ? Or as usual this is just another only in the USA thing ? (UK user) like the voice control.!
I have 65.0.507 and I have no multimodal from what I gather it is slowly rolling out and only a few YouTube VR channels have it some do not but say we should see it soon.
Maybe there's miscommunication. I want either both hands enabled or both controllers with no hands. Not sure of the purpose of a multimodal and why did YouTube even do such a thing?
The one YouTuber that days he does not have it. Wanted it for instances like holding a gun In your hand and using a controller to access menus. Seems to me this would be a bit of a learning curve.
I have put in 4 different support calls or chats and have not received a solution.
No matter what I do, my unit will not update to v65.
Its a 128 gig unit.. I have had it for well almost 2 months.
I have tried the following:
Factory Resetting (twice)
Checking for Updates via the Setup\system\Software Updates section (numerous times on my own and under the direction of Meta's Support team)
Shutting down the headset while on wifi to see if it prompts for an update.
For the first 3 times that I e-mailed (2) in or sent a chat (1), the first response from Meta team is always #2 above. Its like a repeated mantra.
I have gone so far as to send screenshots to their support.
My ticket # is 06981620
After executing #2 above, for some lady named Katelynn on their e-mail support, I responded back with screenshots... that was 3 days ago. I have not heard anything from her since. No followup, nothing.
Today, I had a conversation with Precious and another lady. the last lady asked me to wait and explained that she would reach out to Katelynn. She assured me that Katelynn is working with "the team" to provide a solution... but nobody has to communicated this to me... via the e-mail channel.
Hey @wphend00! Thanks you so much for your time and patience you took to get through all of those steps, we really appreciate what you have done thus far. In order to further assist you we would like to continue in a private message to gather your information and look into your account for available options. To do so, please select our name to get to our profile page, or click here: https://metaque.st/CommunitySupport. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.
We value your response and look forward to hearing back from you soon!
Hi there @wphend00! We just wanted to check back in with you to see if you still need assistance. If so please feel free to reach back out to us as we would love to help.
Do Not update to v65 if you use Airlink and Link cable interchangeably.
After you connect link cable and reboot, the OVR kernel is recompiled which omits the airlink protocols. The only way to fix it is to reinstall the firmware, but since Meta want's to track your every move that's not possible through a locked boot loader.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
