Blog Post

Announcements
1 MIN READ

PTC v67 Release Thread

neurodivrgent's avatar
neurodivrgent
Retired Support
1 year ago

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

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

If you're seeing an issue or bug after updating to PTC v67 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 v67" to the thread and in the title. This way everyone can look for just PTC v67 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 on the forums 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!

Published 1 year ago
Version 1.0
feedback
Headset
PTC
Quest 2
quest 3

23 Comments

  • ThatPaulAllen's avatar
    ThatPaulAllen
    Protege
    1 year ago

    Is there a way to get the update to push to my headset? I’ve signed up for PTC but nothing is showing up. I also haven’t seen the passthrough upgrades on v66. How do I get these features? I feel pretty helpless just sitting on my thumb waiting around. 

     

    Would love if Meta adopted a more Apple-esque approach with features and updates. The current approach is needlessly confusing for your users. I signed up for the beta knowing the risks. Just give me the features to test.

  • FrozenAlex's avatar
    FrozenAlex
    Explorer
    1 year ago

    The new window layout seems interesting. Couple of notes on them.
    - Add an option to curve those windows while they float
    - This limitation of 3 floating windows seems a bit small on Quest 3
    - Hiding menu should not hide the floating windows
    - Sizes of windows seem too limited
    - It would be nice to be able to pin windows to the position of the headset (to make youtube or a browser follow me in passthrough)
    - Pls keep the website fullscreen mode in browser separate from the window fullscreen mode

    Bugs I've noticed:
    - Windows seem to lose their size after you exit a fullscreen mode.
    - Browser seems to glitch out and lose the ability to be interacted with. (The page becomes not clickable, seems to happen when opening youtube in fullscreen mode)
    - Windows seem to be z fighting sometimes, The ones that are further away, show over the ones that are closer

  • sibir.lupus's avatar
    sibir.lupus
    Explorer
    1 year ago

    Is there any chance V67 fixes the 6Ghz Wifi issue (constant disconnects) that was introduced in V64 for the Quest 3? A large number of people have reported this issue for the Quest 3 and Quest Pro since V64 rolled out. I was having the same issue with my Quest Pro since the V64 update, but that issue went away when I updated it to V66 this past week. 

  • J40NYR's avatar
    J40NYR
    MVP
    1 year ago

    I've just found out that the keyboard tracking works with unsupported keyboards and it's fantastic! what an awesome feature!

  • wozhdal's avatar
    wozhdal
    Explorer
    1 year ago

    is there a roadmap time range for non qwerty keyboard layout support ?
    It's the last thing preventing me to really use it as second screen every day 😕

    All the rest is perfect ! Bravo!

  • mooland6's avatar
    mooland6
    Explorer
    1 year ago

    Bug - On v67 The quest pro requires wifi to always be online otherwise it refuses to connect or stay connected.  This bug kills the use of local dedicated routers.

  • RuneSR2's avatar
    RuneSR2
    Grand Champion
    1 year ago

    Just make sure the Rift CV1 Touch controller support is no longer broken in OpenXR games - that was a gigantic error with the v66! Not sure how such a massive error could go unnoticed before launching the v66. 

  • chryostasis's avatar
    chryostasis
    Honored Guest
    1 year ago

    It seems that when within the new 2D window fullscreen mode gamepad(ex. Xbox controller) inputs are disabled. 

  • bappity's avatar
    bappity
    Honored Guest
    1 year ago

    environmental lighting would be nice with the separate windows. always active as well, not just for videos