Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v59 and the solutions for some have shipped, while others are on the way!
The Public Test Channel (PTC) for Quest v60 is starting to roll out for Meta Quest Pro and Meta Quest 2, with Quest 3 PTC coming soon.
If you're seeing an issue or bug after updating to PTC v60 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 v60" to the thread and in the title. This way everyone can look for just PTC v60 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 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!
Got v60 on my quest pro this evening, seem to update ok ? Went through all the menu's etc, can't see anything that's changed ? Is this just a bug fix build ?
v60 on the PC App prevents my D-Link Air Bridge from broadcasting it's SSID. It's really weird I gave it an factory reset and during the "pair it to your headset" to finish the installation - I did not see the SSID in my headset- I checked my phone as well and didn't see it. I performed a repair on the PC app to no avail also.
When I get home from work I'm going to uninstall it and re-install it but not join the PTC (assuming of course that leaves me on v59) on the Oculus PC app and see if running the setup on the Air Bridge is different.
I got PC App v60 (and Firmware v60 on Q2). Very disappointed. No AV1, no new setting both on Desktop App & Debug Tool, no image quality difference, still use toooo much VRAM, still Quality mode is meaningless.
Anyone get PTC v60 on their Q3 yet? I may enroll with both my QPro and Q3 but I want to keep them on the same update version (including oculus desktop app which normally need to use the public beta with headset PTC's). So, I don't want to enroll in one until the other is also available. Thanks mates.
Windows app updated yesterday and Quest 3 updated tonight to V60, both PTC. What did you change? For me this update is amazing, the headset is a lot cooler now with 120 hz, i know it is not officially suported yet but for me this update did wonders. 120 hz running super smooth and headset a lot cooler with less battery drain is a dream. Tested only Iracing and Rfactor 2 with LINK cable btw. Congratulation to the team.
Ever since I updated my headset to v.60 The Walking Dead Saints & Sinners Chapter 2 has been laggy mess in the hub area, going from 50-60 fps at most angles to what I would is less than 5 fps it has ruined the game for me. I have yet to try into the radius and see how that performs but I was already laggy so im betting its even worse now
@Frankalexandre Thanks mate! Unfortunately when I go to enable PTC on my phone app it still says PTC is full and not available. Same as before, so maybe it hasn't been rolled out in my area yet because it's hard to believe the Q3 PTC would already be fully enrolled. Anyway, I'll check again later. Thanks again mate.
@Delboy_was Please edit your post and list which Meta headset you're using. Thanks mate.
Been in the PTC for nearly 2 years with Quest 2 then Quest Pro, reported on many a problem and submitted a fair few idea's, and I get no notification that the Quest 3 PTC has opened (only found out through this thread) and by the time I get home from work and turn my headset on the PTC is now full !?? Would be nice that us long time testers got first refusal as a bit of gratitude ? But alas as with everything else in this world I am but just a number ! Ho hum! Moan over, for the few that have got it post your findings.
Hey @Okuda.IOI , the Quest 3 PTC hasn't really opened up yet. There are some folks getting it through development channels but I'll be sure to post a big announcement (and I'll let you know personally too!) when they open it up for a larger crowd.
@Ryanality Pretty silly that Q3 PTC is sooo delayed imho. I re-enrolled in PTC with my QPro yesterday (version 60.0.0.107.366) and oculus desktop app public beta (version 60.0.0.109.352). Still nothing for my Q3 but at least it seems to work ok with the public beta pc app. All seems to be working fine with both headsets. Maybe a little easier going in/out of PCVR.
Hello i am Q3 and V59 some of my games don't launch anymore since the V59 version and the openXR present in the headset i hope on the v60 version we will have a fix.
The game concerned is Rfactor2 having bought the Q3 only for simracing.
Does this version include any software fixes for the Q3 Elite Strap? Mine didn't work for days, but when I signed up for PTC v60, it got fixed after that... I don't know if there's a connection or if it just happened by randomly?
I hope the degraded overall graphics and awful jaggedness v59 introduced gets fixed in v60. Haven't been able to really enjoy any game since. Everything looked so much better before v59, it was all so crisp and clear, now it's a shimmering and jaggy mess..
Meta is gonna rma my quest3, but I'm still thinking that it's purely software related .
Quest Pro problem of tracking handcontrollers are back again with PTC v60.
Have serious tracking issus, controllers dissappears and are gone for a while, then gets back and are once again lost. Very unusable now.
After trying to reset them and pair them, the issue is still there!
So i took the decision to exit the PTC, reset the Quest Pro in a thought that it would be downgraded to v59, but it remains on the v60 PTC version!
So what would the next thing to do? Can i get it back to the latest public version to make it work again? All those tracking issues started after PTC v57…
@JohSm67 I haven’t had any problems with ptc v60 on my QPro. Everything seems to work fine. For PCVR make sure to enable public beta on the oculus desktop app. Otherwise contact meta support I guess.
I updated two of my Meta Quest 2 devices to PTC v60 version today and noticed that connected Bluetooth devices have huge input delay lag. Earlier today the Bluetooth connection worked fine on these devices The input lag is between 1-2 seconds when Bluetooth controller is connected. I have tried to factory reset the headsets but the issue still persist. I have also third Meta Quest 2 device which still has V59 on it and the Bluetooth controllers work correctly on that one.
I created new post on this here and send a bug report. Please try to fix this before making V60 globally available!
@PyryVuorelaHiab I got v60 on my quest 3, tried with a xbox controller via bluetooth and the latency was actually better than I was expecting, it might be a quest 2 thing
This issue seems to be specifically about BLE devices, the logs indicate that there is some sort of timer or timeout when reading data from the device. I posted the log information about this issue to post below. This is still working fine in V59 but not anymore in V60.
Hi, just tried to restore from the cloud the backup of some game scores saved from my old Q2 to my new Q3. I get a message, that v60 is required for that. It would be nice, if this restore will be working till Xmas, cause I need the Q2 as a present and would like to reset it before. Thank you.
Got another PTC v60 update on my QPro today (now version 60.0.0.144.352) plus an oculus desktop app public beta update (version 60.60.144.352). Tested out with a few Rift and Steams app plus flight sin msfs. All seems to be working fine. Don't see any significant differences. Maybe my Pro controllers are initializing a little faster.
@Ryanality Found a problem with PTC v60 on my QPro. With flight sims like xp11/12 or Aerofly FS2/fs4 I normally put my controllers off to the side and use my flight sticks. The controllers always stay out of sight where I put them. Since PTC v60 they jump back to center after about 30 seconds. If I grab them, get their position recognized again, and move them out of the way they pop back to center view again after another 30 seconds. Bit of a pain because they then block the view of my cockpit instruments. I have filed a bug report on this.
This doesn't happen with my Q3 which is still on v59 as long as I roll back the oculus desktop app out of public beta back to v59. My QPro still does this with the v59 app. So, must be a combination of the PTC v60 headset/controllers/PC app. I'd probably try opting out of PTC on my QPro but others have told me it doesn't properly roll back to v59. I really don't know why I bother with PTC's anymore, lol!
"com.metacam.MetaCamApplication" keeps crashing with the only options being to either close or uninstall. not sure if is related, but i will see the space sense button at the bottom of the physical space tab, then next time i look it's gone. my headset also seems to be having issues initiating passthrough. everything is in a black background for longer than usual after powering on or turning off the screen. any ideas?
Ptc v60 on quest pro white line in pcvr (5 line) i think this is the encoding same for the v59 how i fix that? this is really bad thing for the immersion
@Ryanality There is an issue that you introduced in v57 for Quest Pro. Controllers constantly freeze every 2 minutes or so for a longer period of time. It was a problem in v53/v54 that you fixed and v56 was good but you brought it back again. v59 made it worse and additionally introduced severe fps drop issues, headset displays very stuttery 20 frames or at least that's how it looks like after 30 minutes of gameplay. PC has flawless steam vr graph, wifi is the same as it was 6E. This issue is happening to multiple people on Quest Pro. My headset doesn't overheat, the battery clearly doesn't overheat either. Factory reset of controllers and the headset doesn't change anything at all. These are v53/v54 issues all over again. Not only that I heard on v59 some people already got their controllers fully bricked to the point of needing RMA. Same issue that happened to me in early versions of v56.
You guys have literally brought all the issues that you've once fixed and there is absolutely no aknowledgement from Meta about fixing any of this so far into v60 PTC. I had my Quest Pro for 8 months from which 4 months it was an unusable paper weight due to the software updates breaking it and painfully long RMA process that took 2 months to replace a completely bricked left controller.
Are you planning on fixing this in the nearest of future or am I going to wait till next year for dev team to kindly fix the issue making more than half of the time I had this headset unusable? Or maybe dev team doesn't have anything better to do so they just reintroduce same bugs on purpose so they have something to work on? At this point I could totally believe it considering how bad handling of software was from Meta this year.
@Ryanality Tried opting out of beta on my Quest Pro and it stayed on the same PTC v60 version as before, Still the same after doing a factory reset. The Meta support website says;
Note: Disabling Public Test Channel will automatically downgrade your device to the current public release. You may not be able to re-enrol if the programme is at capacity. If the PTC release is equivalent to the public release, downgrade and factory reset will not occur, and you will disable future PTC upgrades.
Sooo, this hasn't fixed anything with my QPro. Fortunately I'm still on v59 with my Q3 and it's working well. Only good thing about doing a factory reset on my QPro (only 2nd time I've needed to do this in over a year now) is it forced me to get rid of a lot of standalone apps I no longer need on my QPro, since all these now work better with my Q3/512Gb anyway.
Will I'll need to wait for V60 to go final before my QPro will get another update, or will I need to wait till V61??? I kinda doubt that I'll ever enroll in PTC ever again, lol!
So are you going to address the mess of the pro controller freezing since v57 and getting worse in v59 as well as introducing heavy performance issues in connection when playing PCVR with VD? I literally can't play any games because my freaking controllers freeze randomly all the time. And after 30 minutes my latency gets a spike and I get fps drops that don't come neither from PC not my router.
UPDATE US ON PRO CONTROLLERS ISSUE ALREADY. I AND MANY OTHER PEOPLE HAVE A PAPER WEIGHT DEVICE ON THEM RIGHT NOW FOR WHO KNOWS HOW LONG AGAIN.
@MountainIDrew I honestly can't believe this mess. I don't know about you but multiple people (me included) had the same exact issue in v53 and v54. Meta only addressed it late into v56. It was wifi driver issue (mostly connected to wifi6E functionality but not exclusive to just that wifi).
Right now I can't use My Quest Pro wifi 6E because of that. on Wifi 6 after an hour I didn't notice any freezing but that was just an hour. However I can't really play on Wifi 6 which is 5GHz band because I have 5GHz wifi networks around my apartment so interference gives me image delays when turning. I literally cannot use my Quest Pro at all. I'm not going to plug my headset to cable and using link that is heavy on performance.
Meta literally reintroduces the same bugs again after only 1 working firmware version.
I wonder how many VR newcomers are turned off by VR due to horrendous and inconsistent firmware alone. The fact the pc app has been abandoned and quest link not getting modern feature support or that integration into the native quest os/ui a few years back just shows the focus isn't there. Before you make an amazing new vr social media experience you need to make an affordable headset. Before you make an affordable headset, you need to make a great or amazing headset with a robust feature set. Such a headset needs great and well tested firmware. PTC should not be the main/only source of QA testing but that is exactly what it has felt like for years now. No one at Meta being bothered to put out a change list for the PTC despite me being on it for 2 weeks now on my Quest 3 is counter intuitive because how am I supposed to test out the planned changes for the full release if I have no idea what those changes are? I now hardware and software development are immensely complex especially in the VR/MR space, but I expect company worth billions to do more. Do better. Be better. At this rate whatever Valve has been cooking since the Index is going to clean Meta's clock.
Quest Pro with the Touch Pro Controllers still have serious issues If you use a 5GHz WiFi network. Problem do not occur If you use a WiFi on 2,4GHz only. But then you are limited with streaming.
Noticed that firmware update on controllers also have issues to complete to 100% if you are connected to a 5GHz network, switching to a 2,4GHz network and it will complete without issues.
Now using a complete new Meta Quest Pro and Touch Pro Controllers. (Same issues)
No other WiFi issues seen, Q3 and alot of other devices works fine. Tested different WiFi SSID`s using 2,4 and 5 Ghz bands (WiFi 4 and 5) using Unifi (Ubiquiti) Pro AP`s.
Since latest update of PC App, its library shows many PC programs... many running or resident process icons in library... annoying, what's the purpose?
What is the latest word on PTC for the Quest 3? I have never been able to turn on PTC in settings on the APP for the Q3. It says it is full and check back later.
No problem on the Q2 and it's on. I got V60 PTC on my Q2 but again can't even turn it on for the Q3. Will people be able to turn on PYTC on the Q3 when it becomes available?
