PTC v53 Release Megathread

 I don't like how when direct touch is on it's not a separate window from your menu bar also everytime you turn it on or off you need to restart the headset. (very Annoying)

i also feel like the direct touch window should be much larger than a window pinned to the menu bar. 

Hello Ryanality thanks for keeping us informed!

Is the dev team able to share any details about WiFi 6e which appears to be working for some people with this v53 PTC build?  Would love to be able to stress/test this and am currently unable to connect to my active 6GHz network while there's multiple reports on other forums of users having success with 6e.  If it's helpful to the team, my SSID is the same for 2.4/5/6GHz (with no option to split them due to this routers particular settings) and the reports I've seen of people having success claim their networks have a separate 6GHz SSID.

Where is the "Meta Quest build v51 release notes" and what could we find in PTC v53?

as for the desk and sofa issue am i the only one who can't see them again? Could someone be kind and check if sofas and desks traced with the room setup are no longer seen in the homes?
In the meantime I had to submit a bug report hoping they take notice.

I've found a bug with the Laying Down mode, in accessibility settings. (By the way, this is AWESOME. Been wanting it for a long time). I have a bug, and a request to accompany it.

Bug - Turning on Laying Down mode works great. But turning Laying Down mode back off, it doesn't actually turn it off. Any time i recenter, it sets the horizon based on my head position. I found that this continues to "stick" until you reboot, then it works again as expected with Laying Down mode off.

Request - This is a feature that a lot of people are going to use and want to easily turn on and off. Please add a switch for it in the quick menu off the taskbar.

v53 did something odd on the quest 2.  It seems to have broke Foveated rendering on ALXR causing artifacting on a version of the software the previously worked (jan 15th nightly release) .  v51 was fine.  I know you guys dont support this, but it could be symptomatic of a change that has been made that could affect other PCVR software.  I know, "use Airlink".  Would love to, but there is no masking passthough on Airlink for AR.  In the mean time. Also, since no one else on the net has posted about this, if someone else is haveing this issue, wanted them to know they aren't alone.  

Thanks everyone for the feedback so far! I'm working with the team to report up any of the bugs that have been listed. I'll follow up with people if the team needs more information.

Folks that were on PTC v51 should be moving on over to v53 and v51 is starting to roll out to non-PTC users. There aren't currently release notes available for v51, though it's mostly just the Android 12 change and some performance and feature improvements. I'll check in on the release notes publishing calendar, but they may get wrapped up into the v53 release notes when that build ships post-PTC.

I have a lot of new issues with v53

- using fixed channel on 5GHz or 6GHz wifi I have a warning about DFS been detected

- using 6GHz wifi, when rebooting the headset, it can takes up to five minutes to get connected to wifi

- when docked the headset can lose the wifi 

- the headset doesn’t wake up, need to press the power button to wake it up

- using Air Link with fixed 200Mbps, the trans time is around 30-40ms, the encoder graph shows that it’s unable to maintain 90fps, this in Oculus Home

- using dynamic bitrate set to 200Mbps, the actual bitrate is sometimes capped to 10Mbps

- using dynamic bitrate set to 200 with a 50Mbps offset, the bitrate never go above 120Mbps and trans time is 25ms (used to be 180-250Mbps with sub 10ms trans time with v51)

- when restarting Oculus service after some Oculus Debug Tool changes, you have to reboot the headset in order to get the headset to see again the pc

So right now Air Link is broken for me as the encoder can’t maintain 90fps (3950x with 4090), latency is all over the place (trans time is at least multiplied by three compared to v51), and bitrate is really low

Is there really no chance to switch back to v51? It was brilliant and now, with v53 the headset is almost unsuable. I'm facing a problem which nobody seems have reported yet - after the update my controllers keep constantly reconnecting (or they are lost for a second - I don't know). It happens once in 1-2 minutes, sometimes it happens a couple of times in a minute. One controller just disappears and reappears in about a second. And then the same happens with the second one. It happens both in standalone and PCVR (via link cable) modes. It makes playing any dynamic game almost impossible. It seems like they are periodically disconnecting and reconnecting (maybe this is some sort of sleep mode for controllers that is working incorrectly?)

I restarted and turned off the headset, restarted the controllers, but the problem persists. 

I  noticed that if you don;t do anything for a while in Oculus Home, your avatar puts hands fown from the controllers and puts them back after you touch a button ot a thumbstick, so I thought maybe that was the problem. But then I noticed that the problem occurs regardless of whether the avatar's hands ar on or off the controllers.

If it can help - the controllers were behaving a bit strange while updating - they were diconnected several times during the update process ("Controller updating" message appeared several times).

Please let me know if it's possible to do something with this problem? And it's strange that nobody else reported it. Am I the only one who faced it after the update?

Oh, I should have mentioned, I have these problems with the Quest Pro. I have all the updates installed - on headset, controllers, Oculus soft on PC - nothing is pending. I had about 80% batteries on everything before starting updating.

Anyway, I reported the bug just from the headset itself (had the controllers reconnected for a couple dozens of times while typing) and waiting for the support to reach me.

After reading that nobody else is experiencing this problem, I'm not sure anymore that it's related to the update, maybe it's just the coincidence. Anyway, probably I'll wait for v51 to become public and quit PTC - I hope it will downgrade automatically and it solves the problem. It's quite annoying to play anything when your controller can disappear in any random moment.

For me personally the only usefull thing in v53 is Brightness Compensation (it improves the picture a bit), and by the way there is also a bug with it, when it's reset to the default (Off) after you exit any app or Oculus Link. I know that there appeared a standalone local dimming but I don't want to bother connecting the headset to PC and running the ADB command every time I want to play standalone. So, I will be more than happy to downgrade to v51 when it's possible.

Meanwhile I'll try to unpair and pair the controllers. Not sure about the factory reset though - heard that it can brick the headset if something goes wrong.