Skip to main content
Ryanality
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

    Show previous replies
    kerolosheba
    New Participant
    April 23, 2023

    is there any method to return to PTC v51? 

      VanGohman
      Up and Coming
      April 23, 2023

      If they release 51 to the public we can downgrade to 51. Right now the public is on 50, so we can't downgrade yet.

        Eternalsound1
        Participant
        April 23, 2023

        Guess my quest pro will gather dust intill that happens, they officially release v51.  I'll never ptc again once I can downgrade

          kerolosheba
          New Participant
          April 23, 2023

          I found a solution for the quest pro 5ghz wifi bad connection, I disabled the firewall, parental control, and onemesh settings in my router and now I recieve 1200mbs signal no problem and airlink works perfectly, I think it's the firewall that is the problem but I am not sure

          but still the controllers problem occur but my solution is just turn off the wifi in the headset itself then turn it back on and this fixes the problem completely

          I hope this helps 

            Eternalsound1
            Participant
            April 24, 2023

            Is it possible I can just turn off the headsets firewall? Seems like a big risk to turn off the wifi firewall completely  from the router

              kerolosheba
              New Participant
              April 24, 2023

              I don't think it was about the headset firewall, I think something is blocked in the router firewall, I don't know if you can whitelist the connection to the headset or even if it was the right solution, but these were the things I did to make my Airlink connection work flawlessly 

                RinkZea
                Participant
                April 24, 2023

                I've been having an issue with my Quest Pro since last week when it was still in v51 PTC, but the problem persist in v53 so I think I should report it here:

                My controllers cannot connect with the headset after a sleep or a reboot. I can still see them in the mobile app and their battey levels are shown as normal, but in headset they appear as "Not Conected". If I turn off Wi-Fi in the headset, the controllers will be connected but in 3DoF mode. It will disappear immediately as I turn Wi-Fi back on. 

                I had tried all the routine troubleshooting methods for controllers issues such as reboot, re-pair and factory reset but with no luck. I also tried some suggestion in this thread such as disable the DFS, change the channel of my 5Ghz Wi-Fi, switch to 2.4Ghz Wi-Fi or disable Wi-Fi in my router completly, but none of them fix the issue.

                So far, the only temporary fix of this issue is making a factory reset for the headsets itself, but the problem will still appear after I put the headset to sleep or reboot the headset. 

                I have seen that others have experienced this issue here and on reddit, even to a reddit user who did not join the PTC. I am wondering if it is merely a software issue so we can expect a fix, or a hardware issue so we can only apply for an RMA.

                  JoseLuisEstell
                  New Participant
                  April 24, 2023

                  Quest 2 in V53 keeps rebooting when pussing oculus button or headshet button. Of all the beta versions i´ve used, this is the buggiest one, very unstable.

                    Exius86
                    Participant
                    April 24, 2023

                    By the way, I googled about the DFS - how the hell 2.4 GHz Wi-Fi can trigger a DFS warning if DFS channels are only for 5GHz and higher Wi-Fi?

                    One more problem emerged, but it's not connected to Wi-Fi - the headset started giving "Tracking lost" and guardian error every time after I play any game in standalone mode. I have to reboot the headset to solve it. The error doesn't occur in the PCVR mode though.

                      aostang
                      aostang
                      Participant
                      April 24, 2023

                      Not even "and higher".. 6Ghz doesn't use DFS. That's why I know they have some kind of WiFi driver issue going on and I'm not going to try to even bother debugging this any further.. I get the DFS warning *only* on my 6Ghz network (5Ghz works fine without the error and even that isn't set as DFS channels so I'm not using DFS at all).

                        Nebouxii
                        Participant
                        April 25, 2023

                        Update went through a couple minutes ago. Hopefully it will solve some things.

                          TomCgcmfc
                          Honored Contributor
                          April 25, 2023

                          I also just got another v53ptc update (headset firmware and controllers) plus another v53 public beta update for the Oculus Desktop PC app.  Tested out with Air Link and apps form the Rift, Steam, and VivePort stores. plus flight sim msfs.  All seems to be working fine so far.  Seemed a little more stable switching into the Rift void/dashboard.  Plus I didn't get the detected DFS channel warning (using non-DFS ch36). 

                          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
                            Bladerah
                            Up and Coming
                            April 25, 2023

                            Just got an update but unsure of what it was for. I see my avatars arms again now. Also laying down mode toggle off still doesn’t work correctly.

                              aostang
                              aostang
                              Participant
                              April 25, 2023

                              Got the 2nd release of v53. Seems pretty rock solid for me now, though I only got to test it for about 10 minutes. No more DFS warning and 6Ghz connects perfectly now. Virtual Desktop and Steam VR performance are stellar. 100% smooth gameplay with no noticeable latency. 5Ghz was great for me before this update but I still had minor blips here and there simply from not being the sole device on the 5Ghz band. Now that I can use 6Ghz for my headset only, this looks to be perfect so far! Will test more tomorrow but so far now I'm a happy camper!

                                lFlolliel
                                New Participant
                                April 25, 2023

                                Currently, this version is unusable for me. Every 30 seconds to 1 minute the controller seem to lose tracking, first the one, followed by the other side. Check this short that shows what is wrong:

                                Quest pro controllers bug 

                                I am using a Quest Pro, I have tried standalone as well as PC-VR. Rebooted, over and over again. In the end, I have paired my Quest Pro controllers with a Quest 2 and everything is working fine now.

                                The headset version is 50000390045200320

                                Software version is: 53.0.0.106,132.467675283

                                Runtime version is: 53.0.0.111.132.468252061

                                I am in the PTC because I wanted to try out the local dimming feature, I have oculus app version 53, checked all settings.

                                As of now local dimming is still a complete Myth for me at least.

                                  Exius86
                                  Participant
                                  April 25, 2023

                                  So, even the second v53 update doesn't fix it? I had this problem - your Wi-Fi network messes with headset-controller connection. Switch it from 5GHz to 2.4GHz or try another channel. If it doesn't help - disable the Wi-Fi network at all. Seems something's wrong with Wi-Fi drivers in v53 firmware.

                                    Show more replies
                                    Terms & ConditionsAccessibility statement