Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v63 and the solutions for some have shipped, while others are on the way!
The Public Test Channel (PTC) for Quest v64 is starting to roll out soon for Meta Quest 2, Meta Quest Pro, and Meta Quest 3. Please note that there is also a test for PTV v63 that is still ongoing, so don't be surprised if you find that you get a new version of that instead to begin with.
If you're seeing an issue or bug after updating to PTC v64 jump on over to ourGet Helpboard and search for any existing thread, if you don't find one, make a new thread. Please add the tag "PTC v64" to the thread and in the title. This way everyone can look for just PTC v64 issuestoo.
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!
As a software developer myself, I think it's ridiculous to open a Community test platform and then refused to tell the people who are doing this work for you... What to test!
To all Meta / Oculus users . . . noteworthy discoveries!!! - DCS 2.8 stopped supporting OpenXR runtime and introduce their own version built in the game. (CORRECTION) - - - DCS incorporated OpenXR into the game and no longer required users to download "OpenXR.runtime" separately as a standalone runtime.
- If you created a shortcut for DCS Open Beta from the bin-mt and added --force_enable_VR --force_OpenXR as instructed by many Tubers, you probably had a lot of stuttering and performance issues. - Reason: Both OpenXR and DCS's runtime were active and working against each other. (CORRECTION) - - - Open XR running natively in DCS and the Standalone at the same time creates conflicts. - Now Meta Quest Link updates to 63.0.0 (Not the same thing as the HMD update 63.xx.xx.xx) and no longer supports OpenXR and does not recognize the DCS version either. Thus, the crashes we are all seeing. (This statement is not accurate please disregard. Meta does support OpenXR as the standard.)
Support for this observation: This conclusion is based on the many days of reading DCS and Meta forums/support teams and Reddit. I have over 15 years of Software Release Management and testing and can read between the lines. Point is, this may not be entirely accurate due to non-disclosed talks and info but I am confident it is accurate based on the given information.
Meta Quest Link for PC has updated to v64. my Quest 2 still on v63 and I'm getting constant random disconnections from this link. When will it launch on headsets too? I've already ruined a few gaming sessions due to disconnections. @Ryanality please let me know something because if it takes a long time I will do the downgrade on pc. Thank you
Good day I'm still experiencing white transparent band on my quest 2.if I turn sliced encoding off in the debug tool app transparent bar goes away and causes snowy/white flashes in black areas. Anyone else experiencing this? Headset version: v63.
A strange bug with Air Link on my Quest Pro got introduced with this update. Now after some minutes or right after starting some specific game the image freezes, the connection is lost and I can now longer reconnect via Air Link until restarting the headset. When this happens I can also no longer browse the internet without waiting for ages and the Virtual Desktop app also won't see my PC anymore. Streaming via Virtual Desktop however works fine, so sth with Air Link must be broken now. I am using Air Link since 3 years or so.
I am also having issues with AirLink on v64 on Quest 3. WiFi keeps disconnecting and performance is very unstable. I am using a UniFi U6 Enterprise AP connected via the 6GHz band with WiFi 6E.
The new pass-through mode in v64 (PTC)is excessively dark and has a warm (yellow) tint, which represents a significant downgrade from the brighter and more neutral pass-through in the previous version. Please consider revising this feature or making it only an optional setting.
I have upgrade to PTC V64 my Quest 3. Since, I am experiencing crash and reboot. Also, when it reboot, there is nothing more than a dimmed black screen. I cannot do anything. When I keep pushing the power button, I can hear the device rebooting, but still nothing showed. Once it reboots, I can see the Meta logo turning, but then again, black dimmed screen.
As @patfish pointed out, the quest's 3 passthrough is significantly dimmer in bright scenes which sucks. However the adjustment for bright objects is much better. Now it is possible to read something on a phone in dark. Fix the brightness in bright scenes please.
I have really dark passthrough with yellow tint, so much so can barely see anything. Also, no 120hz mode and even though the usb-c debris warning has gone the usb connection is so slow and unstable that wifi smashes it hands down. Ridiculous regressions.
PTC v64. I see others here saying that passthrough is excessively dark and too warm, but mine seems an improvement from before. WB looks spot on in my house and image isn't too dark, I would say contrast has been lowered a bit more similar to the Vision Pros passthrough which has the benefit of reducing noise grain. Text is now much clearer and readable both on paper and on my phone screen, also dynamic range is much better if I look out my window the outside is properly exposed instead of being washed out.
Only negative I have noticed is a stutter motion blur presumably due to a slower shutter speed, which also shows a flicker from my kitchen lights. Overall I prefer this compromise
The real problem with this PTC is first and formost we are not told what has changed, I believe I know why this is ! Certain features are rolled out to certain groups of users but never all features to all users..! basicly its a blind case study, lets take this so called pass through improvement ? Well I'll tell you this mine looks way worse than it did before anything more than a few feet away looks fuzzy as hell where as before it was fairly clear! Now are my group getting a different bit of code than others that have reported improvements? Why have some peoples units been bricked by updates and artifacts on the screens and i've had nothing even close to these issues on both my Q3 & Pro ? different code??? So they can't tell us whats changed per say as they are so many different versions all released to the PTC at once.
For me the passtrough looks worse on v64 than on v63. It's darker and fuzzier and has bad ghosting when moving quickly. Phone and pc screens are maybe a bit easier to read, but I really didn't have problem with them before.
Edit. The headset seems to also go to sleep immediatly when taken off from face. It doesn't respect the turn screen off and go to sleep delay options.
Anyone else's 120hz option gone from the display settings menu or am I the only one? All I have now is the night display and display warmth options. The 120hz toggle has disappeared.
I get less nausea at 120hz so I often turn it on but it can make some apps unstable so I also disable regularly too.
The update is good but it has completely stopped stand-alone moding games such as BONELAB, Blade & Sorcery :Nomad, Pavlov Shack, and Battle Talent. Update v64 has put a stop to all moding platforms from accessing you're files to mod in developer mode . Mobile VR station is completely cut off which is the main file loader that quest supports for mods . Update v64 has ruined most if not all meta quest moding for all the games that are made to mod. Meta needs to fix this it Damages all meta quest platforms hundreds of people have the same problem due to the most recent update
Please fix scoped storage. I am an average modder who loves code mods in BONELAB but can’t do that because meta won’t let apps access files all the way? Once again please help with this!!!!!
Hi there. But of feedback on the full, non PTC Build I was just pushed.
Lying down mode isn't there. 120hz mode has disappeared from the menu. The universal menu is now wonky and off centre, as are menus in other apps, with no apparent way to reset this. People are reporting issues with the mic during casting...and the new passthrough filter is very yellow.
I haven't seen a debris error, but it is concerning that with every build, new bugs appear to be pushed to headsets, especially after the debris USB debacle. Who is testing these builds before pushing them to live?
V64 bring improved pass-through to quest 3 ! What about the Quest Pro ??? and don't give us it's a hardware thing rubbish! Even your boss stated in an interview the Quest 3 pass-through will get better with SOFTWARE updates/improvements! So why can't the Quest Pro's get a little bit of love? or simply like most tech now days gets consigned to the scrap heap when a new device is launched..??