Skip to main content
Ryanality
Honored Contributor
April 19, 2023

PTC v53 Release Megathread

The Public Test Channel (PTC) for Quest v53 is starting to roll out for Meta Quest Pro and Meta Quest 2. Thanks everyone for all your feedback in the past, PTC for v51 uncovered some key issues that we were able to address quickly. 

Let's use this thread for collecting feedback on v53. Share your impressions and let us know if you see any issues. Please make sure to also send in bug reports along with posting here if you notice anything going wrong. 

Thanks again to everyone testing out PTC and sharing your feedback! We appreciate your help testing out the core functionality of software as we develop!

221 replies

Youtuberguy
New Participant
April 29, 2023

Why is the PTC for V53 is out even though neither V51 or V52 are released yet

Moriarti4
Up and Coming
April 29, 2023

The PTC for V51 is rolling out now, had it on one of my headsets a week ago and another updated today as for V52 for whatever reason they skipped that number and V53 is very buggy so needs a lot of testing.

Participant
May 1, 2023

is there any way i could get a direct link to update to the v53 i was just now able to join via the mobile app and update 51 has completely erased months of work and has continued to halt all development
waiting much longer for a fix so that i can restart 9 months of work as if it wasnt already a huge kick in the gut already

pantainn
Participant
May 1, 2023

Issues I experience:

* Apps: Version v51 already broke VRNOID (still works on my first quest stuck at v50) and Pigasus Media player crashes when I want to see something via samba connection on my PC PTC v53.

* UI: The items on the menu at the bottom  don't look well aligned.

* Some controller issues lately and when pointing a finger to the menu while holding the controller, the virtual representation stays resting on the controller (so to speak) but is responsive.

* PCVR: so much issues on lagging I needed to reinstall and go out of PTC, no more PTC on my PC  ;).
Now it's v51 with local dimming on in the debug tool. When using my Pro there were too much issues with particularly Steam VR games. I think it is solved by now by not opening those apps and games in the steam vr environment because if you do it's all stutters, many lag and I get a horizontal line at 30% of my FOV when 5 minutes in and everything below looks poorly rendered.

Up and Coming
May 2, 2023

I don't understand how people ended up losing months of work due to trying out the PTC, but people should only join the PTC if they are willing to risk experiencing issues.

Participant
May 5, 2023

i didnt lose months of work by joining the PTC the update 51 bricked a boot looped my system. forcing me to factory reset. 

Up and Coming
May 5, 2023

Oh sorry to hear that man. I just assumed you were on 53. Good luck with all of that.

Up and Coming
May 2, 2023

Select time zone and edit time

You will now be able to select the time zone on your headset and manually edit the displayed time. To do this, select the date at the top of the Quick Settings panel.


Has anyone been able to test this feature?  Maybe I'm at the wrong screen but nothing happens when I click the date at the top of Quick Settings panel.

Moriarti4
Up and Coming
May 2, 2023

What is going on with the UI in the home ? Who at meta approved these updates ? Have they ever worn a VR headset ?, Why move the window close button to the top ? It's not Windows or a Mac it's VR all controls should be in line of site (straight ahead as much as possible) and stop making it look like it's made by Fisher Price Toys! How about menu's and HUD's that are semi transparent in the home and horizon's, now don't tell your limited by the hardware ! If you've played Iron Man you know what the hardware can do if coded right.! 

StainlessLobster
Participant
May 3, 2023

I'm seeing the same issue with lost controllers that I had with v51.

Rebooting the controllers and rebooting the headset didn't rectify the issue.
I tried turning off PTC for the headset. That caused a new update to appear. Applying it didn't bring the controller back.
I then factory reset the headset. This caused a download of firmware to the left controller. The right controller required a hard reboot for the update to start.
The controllers are currently working and the headset is still on v53 (even after turning off PTC and factory resetting it. I'm still installing applications so I haven't rebooted the headset yet to see if will loose the controllers again.

StainlessLobster
Participant
May 3, 2023

My controllers are gone again. Same issue as with v51. The controllers disappear after the headset comes back from suspend. Factory resetting the headset brings the controllers back but they will never again reconnect after the first time the headset goes into suspend.

There appears to be no way to roll back v53 to the working V51 so I'm kind of stuck with a hand tracking only headset.

Any suggestions for a workaround?

Honored Contributor
May 3, 2023

Stainless_Lobster  I'm not sure if going back and forth, and forth again is going to help.  If I were you I'd re-enroll on the v53ptc and see if you get both controllers to update properly.  When you update/restart you need to look a but up/down to see that your controllers are actually updating, finish, then reboot.  If you miss this and try to bypass it you may not be getting them updated properly.

I'm not having any issues with my QPro controllers with v53ptc.  Anyway, I'm just a simple user so I cannot say for sure that this will help.  Otherwise, I suggest you contact Meta support and start a ticket, including your log files.  I guess there could be a problem with your controllers and they may need replacing.  Good luck mate and cheers.

 

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers
Ryanality
RyanalityAuthor
Honored Contributor
May 4, 2023

Hi everyone, I wanted to give you a heads up that PTC v54 is going to start rolling out soon (as soon as today if all it gets all the right signoffs). The official build for v53 is already deployed, but not everyone has it quite yet. I think the 100% push for it should be soon though.

There are still a few issues reported already from v53 that are being worked on which might not make it to the first version of PTC v54, but it does have a fix for a some of them. I'll start up the v54 feedback thread so it's ready when people start getting it.

Help others find great discussions and answers by adding kudos and marking solutions to your questions.
Inspiring
May 5, 2023

Waaaaaaaaaaaaaaaaiting!! πŸ˜—

StainlessLobster
Participant
May 5, 2023

Hi Ryan,

I just want to report that the v53 update broke controller pairing on my Quest Pro again.

This happened with v51 as well and I ended up replacing it under warranty.

I happened again with v51 under PTC but after a lot of back and forth with multiple factory resets I got it back to v51 and it was working again until v53 (public release) hit it today.

The pattern that I’m seeing is that it happens when an update is applied when the headset and controllers arent plugged into the docking station. As long as the update is app  lied when the device are docked it seem to work fine.

 

I’ve had no issues with the Quest 2 headsets and their controllers (have several in PTC and outside)

 

I’m looking at just swapping this one out too under warranty but would prefer a software solution to get the controller versions in sync with the headset (or whatever the root cause is)

Let me know if there’s a way to re-load controller firmware that I can test.

djfigs1
New Participant
May 12, 2023

I think I have a lead on this. I have two of the same WiFi router that I use with my Quest Pro. Interestingly, I had the same issue of the controllers refusing to connect afterward until a factory reset, even with an RMA'd device, but with just one of the routers. I was so confused why I was only getting this issue with one and not the other, but then I realized that the one I had issues with had WPA-3 enabled (specifically, both WPA-2 and WPA-3 enabled). When I forced that router to use WPA-2 only, so far (it's been a couple of hours so this may change), I have not had issues and I have been able to restart the Quest and still have the controllers connected. It could still be very well the case that they end up breaking, but I distinctly remember the controllers falling after a single reboot with WPA-3 enabled, and this is no longer the case. Hopefully, this could help you out.

EDIT: I also made a Reddit post about the fix.

Participant
May 13, 2023

WOW! It actually works! Thanks so much! 

Participant
May 8, 2023

In addition to the disappearing controllers, caused by Wi-Fi 5, which I mentioned earlier, I'd like to mention one more problem I noticed - regular incorrect capacitive fingers tracking. It did happen occasionally previously, but with v53 it happens every day - every day either thumb or index finger tracking is not working at least on one of the controllers (I have Meta Quest Pro). It either doesn't recognise when I release the finger or when I put it onto the controller. Restarting controllers (holding menu button for 10-12 seconds until they vibrate) help, but only temporarly. After a while (1-2 hours) it occurs again. Restarting the headset doesn't help - only restarting the controllers. I think this is a software issue, because after restarting controllers everything is fine, but then it seems something interfers capacitive tracking.