PTC v53 Release Megathread

I also experience the problem with Quest Pro controllers described above, they disconnect/restart every minute or even more often. I am on v53.

After updating to v53, airlink and virtual desktop both havimg horrible lag spikes. Even standalone games are having shuttering issues but not as bad as pcvr. V51 was working flawless for me, v53 feels like it broke my pcvr experience 😢 

Router is a Netgear RAXE500. All things otherwise being the same and 5Ghz working fine for me, simply flipping between 5Ghz and 6Ghz makes both the Link Home and any steam game a complete stuttering mess when launching on 6Ghz. If I put my phone on 6Ghz I can run connectivity tests and have no issues on the 6Ghz network. I'm within 1 to 2 meters of the router so it's a clean signal (headset wireless status also shows good signal).

I also get a DFS warning no matter what channel I choose, even those that I know to not be DFS channels. 

For those having conflicts with WiFi and their controllers, I don't have that issue. Maybe it's a channel thing. I've only tried 36 and 40 with my 5Ghz but both have been fine for extended play so far. Not that it probably matters but my 2.4Ghz is channel 6.

Ryanality 

BUG

Headset will not show in my computer at all tryed multiple times checked that it is connecting to my pc via ADB used 2x different cables to confirm it was not a cable issue also made sure that i was accepting the prompt inside the headset. Also checked with a 2nd headset currently on v50 to confirm that this was not an issue with my pc and the 2nd headset connected everytime and allowed access to the headset via my computer on each and every connect.

Having trouble keeping my Pro awake, proximity sensor doesn't seem to register properly causing the headset to fall back asleep. Bummer that we can't roll back, my Pro is basically inoperable until the next firmware push.

Just out of curiosity. Has anyone just tried resetting the quest2 and or the quest pro to factory default to see if any of these issues clear up? Im going to try it latter, but my thinking is some of these issues may be a result of meta data that may be left behind from a previous build, kind of common with android phones in the olden days of the XDA forums.  Just a thought

Could it be that v53 started using Wi-Fi channel 36 for controller connection (my Wi-Fi scanner shows that that’s the case), but previously used some DFS channel, so now it is getting interference much more often as channel 36 is much more commonly used? That might be the reason why people started getting DFS warning even though they don’t use DFS. That also might be the reason of the degraded AirLink connectivity problem many including me experienced.

EDIT: it turned out controllers always used the same Wi-Fi channel as the main Wi-Fi connection channel, and on v51 (my Quest Pro reverted back to it) it doesn't cause any controller disconnections for me.

I've noticed unusual lagging in some of the game after upgrade to v53. It's hard to re-validate as there is not way to downgrade, but couple of favorites titles literally unplayable now due to periodic lag and frame drops. It feels like headset lost 10-20% of power and not able to handle now.

Hey I recently received the v53 update and have been finding it to be a great update up until today, when going to use my Quest 2 headset I realized that it was lagging and stuttering, so I rebooted my headset, same issue. I then noticed after multiple reboots, a factory reset and reinstalling a application that the issue was linked to having too many guardians saved. (Thanks to a member of the Meta Support team for helping me realise this)