Skip to main content
Ryanality
Ryanality
Honored Contributor
October 11, 2023

PTC v59 Release Thread

Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v57 and the solutions for some have shipped, while others are on the way!

The Public Test Channel (PTC) for Quest v59 is starting to roll out for Meta Quest Pro and Meta Quest 2 soon. 

If you're seeing an issue or bug after updating to PTC v59 jump on over to our Get Help board and search for any existing thread, if you don't find one, make a new thread. Please add the tag PTC v59" to the thread and in the title. This way everyone can look for just PTC v59 issues too.

It's best if you can post each bug you spot in its own thread, to keep track of individual issues separately.

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. 

We know it's tough when you run into a problem on a PTC build and want to thank you all again for testing out PTC and sharing your feedback! This feedback is extremely helpful to our engineering teams. We appreciate your interest and persistence in testing out the core functionality of software as we develop!

    63 replies

    Show previous replies
    WarrenBoofit
    New Participant
    October 21, 2023

    When using the Quest 2 via Link, although having both 120 hz set to enabled in both the Quest 2 Native menu and in the Oculus PC app, in any game it seems the Oculus Debug Tool is reporting my refresh rate to 90hz.

    I don't believe this is a bug in ODT either, as it feels like 90hz. Below is my ODT settings. I have tried setting encode bitrate to 0, with no change. 

     


    This is starting to genuinely annoy me, because I thought I was just paranoid about the frame drag, but it's become increasingly apparent in my racing sims I easily get 120+ fps on (12900K, RTX 3080, 32 GB of RAM, so the performance headroom should be there). 

    I have Oculus App Version 57.0.0.254.153 (57.0.0.254.153), but I have seen the version 59 mentioned, hopefully that's the one on the PTC channel because theoretically this app should be updated at all times.

    Any advice?

     

    Piklepie
    New Participant
    October 22, 2023

    Okay It happens again

    I'm on V59, face tracking is not working on home interface and everywhere else once again.

    If you turn native tracking off, eye movement would tracks

    but if you turn native tracking on, everything wouldn't work anymore

    How can I fix this? sign out from PTC? or just wait for the next update?

    EveryDay10
    EveryDay10
    Inspiring
    October 22, 2023

    I have never said anything about this but when my headset would heat up and thermal throttle  CHROMATIC ABERRATION

    (A rainbow ish filter that messes with color)

    was a huge problem!! It would turn on and off for no reason and I would have to restart my headset every time!

     

    But after the 59 update my headset runs cooler and hasn't done any of that stuff so good job Meta!!

      BOLNICHKA39
      Participant
      October 22, 2023

      I received firmware 59 for quest2 and lo and behold, the meta finally tried to fix the problem of white artifacts, they are still there but there are noticeably fewer of them, I hope with the release of version 60 they will get rid of this bug completely

      BOLNICHKA39
      Participant
      October 22, 2023

      Also, my avatar in the house oculus still has his hands separated from his arm

      tonyselon
      New Participant
      October 23, 2023

      I'm in UK and got v59 on Q2 last Friday. This apparently finally provided voice commands to UK.

      I went through the voice set up process, declined data storage and used a few commands to test out including 'open Hubris' which immediately launched the brilliant Hubris installed on my Q2.

      The next day I was keen to try more voice commands but although Q2 still on v59, the action to trigger voice commands ( double click Oculus button on right controller) did nothing, not message nothing.

      What gives?

      Lordubuntu
      Lordubuntu
      Inspiring
      October 23, 2023

      Would someone kindly check if meta has finally removed the lock pattern when restarting the quest?

       

      Reference: https://communityforums.atmeta.com/t5/Ideas/Remove-quot-Admin-must-unlock-headset-after-it-restarts-quot/idi-p/1048420/page/5#comments

        FinlessBob
        Up and Coming
        October 23, 2023

        @Ryanality, any word on Quest 3?

        My phone app says PTC full for quest 3.  I assume it's because no PTC is open yet?

        Ryanality
        RyanalityAuthor
        Honored Contributor
        October 23, 2023

        FinlessBob the PTC hasn't been opened up for Quest 3 yet, probably with v60 it'll become available, but we'll be sure to announce it when that happens. 

        Help others find great discussions and answers by adding kudos and marking solutions to your questions.
          nanortemis
          nanortemis
          New Participant
          October 23, 2023

          It's finally possible to enable USB Ethernet on Q2. You need to set "debug.usb.ethernet.enabled".

          Tested on RTL8153 based device. Unfortunately Unitek U1323A (AX88179A) does not work (it has a USB-C port for charging).

           

          Ryanality 
          Please enable Unitek U1323A by also loading the cdc_ncm kernel module. Thanks!

          Show more replies
          Terms & ConditionsAccessibility statement