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

Participant
April 22, 2023

I hope Meta is on top of this, tryed a full format and all, wifi settings, no luck. Would suck to use my geek squad for a replacement due to a beta firmware. Never trying ptc again. Hope a hot fox patch or something comes out soon

Up and Coming
April 22, 2023

I was able to make things better by using the 2.4ghz channel for the Pro. It's not ideal, but at least it stops fluctuating wildly. Now at least I can stream videos again.

Inspiring
April 22, 2023

Hello and Happy Saturday !

I am happy to confirm that the QuestPro now works with the AirBridge dongle (D Link).  Both my QuestPro and PC are using the latest PTC v53 software.  So a big thank you to the Quest/AirLink teams at Meta.

That said, compared to my Quest2, the AirBridge experience on the Pro is about 90% as good as it was on the Quest2.  I've noticed the occasional stuttering and buffering issues (gameplay lagging and taking a few seconds to catch up).  I assume this may be due to the wifi issues ppl seem to be having with v53.  I'm using AirBridge at 200 mbps fixed bitrate. On the Quest2, I can use the same 200 mbps fixed without issues.

Thank you !

-------------------------

Attached video is not part of the report/feedback process, it's just to show that the AirBridge dongle can deliver a smooth 200 mbps fixed bitrate experience (Quest2):

StormlandVR - D-Link AirBridge 200mbps (fixed) demo. Meta/Oculus Quest2 AirLink via AirBridge - YouTube

 

i7-7700k, Zotac RTX 3080 AMP Holo (10G), QuestPro, Quest 2 Previous: Oculus GO, Oculus RIFT - 3 sensor Room-scale, Oculus Rift S
New Participant
April 22, 2023

My main issue at the moment (Quest Pro) is that the controllers give an overheat warning every few minutes, and eventually shut down. I have to just quickly place them on the dock for a couple seconds to wake them back up and reconnect, until I have to do it again a few minutes later. I'm just playing standalone, the same way I always have, and never received an overheat warning until v53. Hoping to see it fixed soon!

New Participant
April 25, 2023

I'm having the same issue - try holding down the oculus button or menu button (depending on the controller) until you get a little haptic buzz. That reboots the controller for me and gets me playing again. 

Participant
April 22, 2023

Unfortunately PTC 53 is half baked, we will have to wait for a new update as they changed something with airlink that screwed everything up. this is part of the testing of a test channel, for something stable its best not to be on this channel.

On version 51 airlink was working perfectly for me on the pro. This is most likely a wifi driver issue (bug) and not our headsets or network setups.

So now alas we wait, grab a snickers and hope for a fixed version soon. 

I9 13900k @ 6.0ghz AC (water), Asus Z690 Apex, 64gb gskill 5800 DDR5, Aorus 4090 Waterforce @ 3ghz
Participant
April 22, 2023

It's not just airlink. I have number of titles which started lagging just standalone. Yes, v51 left me with the great impression and I even noticed some better performance, but v53 just opposite.

New Participant
April 22, 2023

niceee

New Participant
April 22, 2023

nicee

New Participant
April 22, 2023

niceeeeeee

New Participant
April 22, 2023

Issues general:

Since v51: Each controller randomly disconnects once per session. After a second, the controllers reconnect and continue to function without issue until the headset is restarted. This has not improved in v53. I have factory reset, repaired, and even used a new set of Pro controllers. 

v53 specific issues:

Poor airlink performance

The headset loses tracking functionality randomly and gives the error 'Your headset cannot track your surroundings.' Turning headset tracking on and off or rebooting the headset several times will resolve the issue. The issue can occur on the first boot (and become a nauseating nightmare) or after waking. In the short term, I've set the sleep time to be several minutes which seems to help prevent it from happening during session breaks. 

LuvinLife
Participant
April 23, 2023

A few things (Q2/Q Pro Controllers) - I both shutdown and restarted today to make sure headset was updated:

- The app library view installed setting still doesn't work with this version. The setting is set to Installed, but the app library shows those that aren't currently installed.

- Guardian floor still needs a lot of adjustments even between game plays. This is not something I had to do before with other builds nearly as often and have the exact same setup. Tonight I had to shut my headset down because when I went to reset it, the floor grid line was at the top of my headset height and I couldn't lower it at all using the buttons or the joystick.

- I map for Audio Trip and do so for hours in a row. Each time I leave the guardian to check my computer (1 ft outside the guardian grid) and return to the game, I see the home environment with no sign that the game is still active (no blue line under it or quit/resume screen). I click on the game icon and it comes back up where I left off and position is off centered and backwards.

Participant
April 23, 2023

Hi Ryanality  After I get V53 I encounter passthrough issues with both my Q2 and pro.
I'm inside the guardians, but the blue lines and passthrough still appears frequently, seems like the room-setup(outline walls and objects), guardian and passthrough are conflict with each other and out of my control.

The lay down mode can't be really disable unless I reboot it.