Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v67 and the solutions for some have shipped, while others are on the way!
The Public Test Channel (PTC) for Quest v68 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 v68:
1) For issues: Go to our Get Help board and search for any existing thread on the issue, if you don't find one, make a new thread. Please add the tag "PTC v68" to the thread and in the title. This way everyone can look for just PTC v68 issues too.
2) For bugs: If you come across a bug, please post each one you spot in its own thread, to keep track of individual issues separately.
Share your impressions in the comments below 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!
Every PTC release we have to ask what it is we're supposed to look for and they don't tell us. It really is hard to test something if we don't know what we're going to be testing.
This question has been asked on every PTC build release and NEVER has it been answered by someone that works for Meta!! Nope not once! Never!! don't believe me, go check for yourselves! The only answer I ever came up with is because they release so many different versions all at the same time with different features for different sub groups it's next to impossible to do a release list as most people will be sending in bug reports saying I don't have this or feature and they would end up spending days checking release numbers against, they zone codes etc etc etc etc....!! I have no idea why they do this? maybe it limits the amount of bricked headsets from a random bits of code, so just remember by being in the PTC you are rolling the dice on bricking your device, trust me the last one bricked my right quest pro controller (lucky still in warranty so got it swapped out! otherwise ouch!!)
I thought when new PTC version out we get it, so we can test it ....but still sitting on V67....unless it's like live official versions they are staggered.
Since updating to v68 my Right Control has cut out on me twice--seems like the only fix for this is to pullout the "good" battery and put it back in. Never had this behavior before 😞
An hour after posting this both controllers went out... Could only fix by re-booting 😞😞😞
All of the new movable windows, including the floating onscreen keyboard, need to save their position and size when you place them--so that when I return from an app or reboot the device they all display where I want them.
If I have to keep re-setting their positions I'll probably just turn the feature OFF.
Still having issues with using gamepads(Xbox, Playstation, etc...) in fullscreen mode. It seems that when I turn on the controller while in fullscreen mode it USUALLY works, however if I have the controller on before I go into fullscreen mode it is very inconsistent with whether or not the application will continue to read my inputs. In both cases I'm still not consistently able to use my controller in fullscreen mode.
I just got v68 and I am really glad for the fixes and improvements.
I would love for the three floating screens to have the ability to be anchored to their position in space when I take my headset off and put it on again or when I press the meta button to recenter, while the three docked screens will still reappear right in front me in accordance to my changing position.
In addition, I think the UI will greatly benefit from giving the ability to resize any screen, not just the browser windows or just by pushing them away, because sometimes the screens can feel too small when they are close and shrink automatically.
I have v68 but I still don't see the function to hide apps, I would also like to see in a future update the possibility of deciding the distance of the windows by moving the stick while holding the bar under the window in order to adjust the distance to your liking. Besides that I would also like to see that windows like youtube follow you as you walk around with the passthrough
Since loaded v68 when I shut down it updates as before , but when done it shuts off and when I remove power the green light stays on. I have to restart with no power applied, and then shut down again before I have no light. When it stays on my power keeps draining
Meta Support Team told me last week that the USB-C known issue that disables the port and requires a reboot to reactivate would be fixed in the next release (v68) but I'm still having the issue and seem not to be the only one.
I'm also seeing controllers cut out similar to the issue @VR-JoeF mentioned here on my Quest 3 and Quest 2:
Since updating to v68 my Right Control has cut out on me twice--seems like the only fix for this is to pullout the "good" battery and put it back in. Never had this behavior before😞
An hour after posting this both controllers went out... Could only fix by re-booting😞😞😞
I can't figure out steps to consistently reproduce it, but I've seen it a few times now. Here were a couple situations:
A) After letting my headset go to sleep and picking it back up an hour later. When I picked it back up, the controllers wouldn't activate.
B) I've seen it while playing around with casting/using home button presses.
C) I've seen it while pressing the home button during the Boundary Setup process.
Result:
Basically, my controllers just completely stop showing up on the screen, I cannot select any icons whatsoever. And even when I press the power button on the side of my headset to get to the 'Power Off' Menu, I can't even select any of the options there (such as 'Restart', 'Power Off', or 'Apply Updates'.
And to be clear, the only way to get my controllers/cursors to start showing up again is to completely turn off/restart my device.
It sounds like you're having some battery issues, that's definitely not ideal for gameplay. Why not reach out to our support team to explore some options?
A few times I've had to hold power button for like 15-20sec for the Meta logo to pop up and power on headset. This started after PTC v68. It doesn't happen always. Quest 3 512gb.
How do I remove that boundary if I plan on using passthrough to go from living to kitchen and so on? No matter what I try I'm still be forced to set a boundary. I'm on PTC V68.
I am also experiencing some of the same problems listed above. 1) This is an issue where the controller completely disconnects from the device when the controller is not moved for a certain period of time, such as while watching a video. In this case, there is no solution other than removing and reinserting the battery or pressing the power button to reboot the device. 2) When turning on the device, you have to press the power button for about 15 seconds to turn it on. This phenomenon has been occurring since the beginning of v68, and for the past few days, it has returned to normal, such as turning on by pressing the button for 4-5 seconds, but it has started happening again since yesterday. Since there have been no additional updates in the meantime, it is unclear what rule is causing this.
Can't confirm the @maxstep report, v68 PTC - Beat Saber starts just fine in Meta Quest Link OpenXR environment. Whatever issue @maxstep experiences is not related to v68 - or is not as simple as that.
Good version with several new features, but I notice a real problem with scanning the room. The floor level is consistently 50 cm below the actual level, requiring manual adjustment with the controller. Similarly, I have to redraw the room boundaries.
After downloading the additional update for v68 a few days ago, the issue of having to hold down the power button for more than 15 seconds seems to have disappeared. However, the issue of controller disconnection still seems to occur, although less frequently.
I apologize - I should have clarified. The issue pertains to Pavlov VR title in OpenXR mode - I naively assumed the error is with all OpenXR titles as stated by Pavlov VR developer. You are absolutely correct that some OpenXR applications work correctly - I apologize.
When 68 rolled out, I was so excited about the idea of audio input levels. Unfortunately, this does not appear to be working. As you can see in the screenshot below, There is an entry for audio input levels, but there are no settings under this entry.
After the 3rd v68 update things are getting smooth.. it seems to run faster even.. I didn't notice anything to do with the meta AI or the graphical enhancements It talked about though ?
I just had an update to v68 and now in accessibility - mobility adjust height now has a slider to set height this is something I have wished for before. It could be very useful to me and others.
I got the non-beta v68 update yesterday on my QPro (v68.0.0.480.365) and meta-link PC app (v68.0.0.433.361), but still not on my Q3. So far everything seems to be working ok.
One thing I noticed is that the PC app update reset my device graphics back to defaults (72Hz with res slider at 1.0x). So I needed to change those back to what I had them on (80Hz with res slider full right). Also, it changed my Air Link bitrates to default (100mbps dynamic) and I needed to change that back to 200mbps dynamic. The PC app update was a bit different as it didn't go through the usual updating process, just happened and then required me to sign in again and update drivers.
Anyway, hopefully now that the stable, non-beta versions are out now Meta will startup a new V68 With Release Notes thread. Cheers.
The v68 that you forced upon us with no way to not use it has made a bunch of PCVR games fail to load in VR and they just play on a flat screen.
I really can't stand the way Meta does things. If we have to wait for V69 to play games like EA SPORTS WRC in VR, well thats just crazy.
You don't tell us what is in the updates... If you are not abandoning PCVR link then you end up breaking PCVR link and don't seem to even care. Starting to think you like doing that to be honest.
We need a rollback feature for the PC app for when you totally mess things up, you do it often and its really annoying. No way would i recommend anything from meta. I bought the quest 3 because it was advertised for 120 hz pcvr... well thats gone to! Just straight up horrible!
Why is there no hotfix for the Controller going sleep/cutting out/overall tracking issue?
Some ppl say thats not related to v68? Only because he dosen't have the Issue? Well you are wrong.
I recomment pretty much everyone who watch my Stream to upgrade on v68 because the performance boost was insanely good and the first 2 Days it was fine but then you updated the version (like 150 mb) and it starts struggle like crazy.
Pretty much everyone had the same tracking issue like me (told me in chat)
+Sometimes i can ONLY cold start the Quest 3 (15 seconds push of the Power button) ++AIR LINK STILL NOT WORKING++ OVER A YEAR NOW Always lagspikes when i move IRL after version v55 or so it starts and i never found a fix for it. ++++DEBRIS IN USB IS STILL THERE++++ <---- Makes my Quest3 not Counter charge. (restarting the Quest3 solve the issue and comes back when you above like 80%
so stop developing AVATAR / AR Stuff nobody is interested in and start fixxing THE CORE ABILITYS of the Quest 3.
Although working for my particular use case (MSFS), the performance of the updated OpenXR runtime seems to be reduced. (Alongside the known bug with other OpenXR API Layers)
My non-PTC/non-beta just updated on my QPro (v68.0.0.507.364) and meta-link pc app (v68.0.0.474.361). All’s working very well with my QPro/rtx4090 using Link (without OXRTK). Actually seems to work slightly better but it might just be a placebo thing, lol!
I still haven't got this non-PTC on my Q3 yet and still no new V68 Release Note Thread.
After reading what everyone else has said so far in the thread, I think v68 might be giving me the same controller issues. I'll post my issue just for datas sake in case it isn't.
Essentially, they'll work for about 5 minutes on initial startup but then start cutting out every couple of seconds, can be either the left or the right controller.
What happens is:
1. The controller will disconnect (status light on controller turns off, quest 3 doesn't show controller, practically off) then...
2. It'll reconnect (status light turns back on, virtual controller snaps back into view on headset, tracks and behaves like normal).
3. This will happen multiple times in less than a minute. But after a minute or 2 of that, they sort themselves out and everything will be good for another 5 minutes only then to start the loop all over.
I've tried replacing batteries (ive got lithiums in them if that matter, only mentioning because I seen another thread mentioning putting "good alkalines" in, of which I have none), ive done the re-pair shuffle, factory resetting the controllers with the "X/B button held down, menu button 5 times" trick doesn't work, reapplied the update with the software update tool, etc.
Im at a loss at this point, im pretty sure its not a hardware failure at this point because 24 hours before my issue occurred, I had zero issues over the course of a 7 hour play session and had placed my controllers in their normal spot, so i can only assume the v68 firmware update on either the controller side or headset side has caused this.
After the V68 upgrade on my Meta Quest 3 last night (8/2/2024), it failed to connect to the right controller. Trying out the new battery, power on/off not fixing it. Today I tried to use my Meta Quest 2 as backup. The same thing happened and it also failed to connect to the right controller.
@wolfb1978 I’m still having the same issue. The voice input level entry has no setting problem. I’m a bit worried about it, so I’m considering factory resetting my Quest 3 to see if it’s a bug. What do you think?
