cancel
Showing results for 
Search instead for 
Did you mean: 
Ryanality
Retired Support

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 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 v60" to the thread and in the title. This way everyone can look for just PTC v60 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!

90 Comments
erickzera
Explorer

DId they managed to fix the white artifacts? I forced my quest to stay at v54 because of this problem. (it runs with almost no artifacts). 

TheodonKhel
Expert Protege

@Ryanality @TheAntiSocializer Another day and still no response. Another day and my quest pro is still an unusable garbage. I guess you want me to hit half a year of being unable to use my quest pro. You’re doing a great job at it. Let me side load v56 back. I don’t want to see your garbage firmware updates ever again on my device. Let me lock it out on v56 that worked for me. 

Ryanality
Retired Support

Hey everyone, I was out last week and haven't had a chance to catch up, but I'll check in with the team and see what I can find regarding Quest Pro controllers.

 

While I'm connecting with the team, I'd encourage anyone having trouble with Quest Pro controller tracking to follow these steps from the support team, they've found that a lot of tracking issues can be fixed with these steps:

1) Make sure that your router or wireless access point isn't using WPA3 in the security settings, WPA2 or any other security settings should be fine. You'd need to login to your access point by going to the WiFi device's website.

2) Factory reset your Meta Quest Pro or Meta Quest 3 if that's the headset you're using and having trouble with.

3)Complete device set-up. 

4) Restart your headset after set-up is complete and test out tracking.

If you're still having trouble, I'd love to get some more details around what you're seeing so I can share that with the team. They may need some more information around the issue. 

 

JohSm67
Rising Star

@Ryanality 
I Think you have all the answers in previous posts! I did a factory reset on the Meta Quest Pro, same problem. I did change the Meta Quest Pro to another one, same problem. WPA2 in use! 5GHz WiFi is bad, while 2.4 GHz works.

a324260327
Protege

My quest pro controllers die on quest2 after v60 (details here) and became a 300$ e-waste now. I exit ptc but it can't comeback to old firmware. I hate it. I don't want to take any **bleep**ty ptc anymore. I just hope the firmware will always stop at v56. Since firmware updates always bring bugs, why not provide a way to downgrade firmware?

philmanagexr
Protege

@Ryanality I factory reset my quest devices pretty regularly, and recently it seems like the PTC is always full when I try to enroll it after a factory reset

Any way I can reliably have a spot in the PTC while also being able to factory reset my devices when I need to?

TheodonKhel
Expert Protege

@Ryanality 

Quest Pro

Since v57 controllers randomly freeze when playing beat saber for example. They will just get locked in air. I can still use the menu or oculus button on controller sometimes, sometimes not at all. Happens on WiFi 6E and Wifi 5 and 6 (5 and 6 use WPA2-Personal). today I was able to play without freezes for 20 minutes unlike in the last 2 weeks. There is another problem though that started happening right after v59.

After those 20 minutes (can be a random amount of time. Sometimes even right away or after 5, 10, 30, 40 minutes etc) the network latency shoots up when using Steam Link and Virtual Desktop and everything becomes  unplayable. Stuttering and low frames due to increased network latency. This was not happening before. I attempted router resets, PC network adapter of the mobo reset and many others. The only thing that helps is restarting the headset. I can actually even keep the game and Steam VR on while the headset restarts and once I connect to PC I'm right in the opened game and it works for another random period of time just to start stuttering more. Happens 100% of the time on WiFi 6E. Happened once on WiFi 6 but the performance of WiFi 6 is overall worse than it was before v59 and v57 updates. At this point even when I have luck to get less controller freezes I still cannot play for too long. Restarting headset sucks. Especially when playing multiplayer games or watching movies.

JOE.DANCEN
Protege

Don's know if its reported already but 90hz disapeard from the PCVR menu. Its still on 90hz in game but is this a bug?

 

Capture.JPG

dracula.571566
Honored Guest

@RyanalityPLEASE DO SOMETHING about WIFI 6E, it's nearly 1 year since 6E is supported and QPro still takes ages to see the network and random disconnects are still happening. This is RIDICULOUS for a company such as META.

tanubon
Heroic Explorer

bug.JPG

What? PC App 60.0.0.162.352.

TheodonKhel
Expert Protege

Yeah guys. Meta updates. Extremely good and all LMAO. Ruin quest pro controllers, ruin stability of wireless pc vr, mess up PC app and so on. You bought 500$ or 1000$ device and couldn’t use it for majority of the time you owned it? Who cares? Definitely not meta. They will scam you with unusable device and you can’t even do anything to get the money back from this scam of a device purchase. 

JOE.DANCEN
Protege

I don't share your opinion at all theodonkhel. My quest 2 and quest 3 gave me a thousand of enjoyable hours.....Happy standalone and pcvr user. Is there something to gain.?....yes there is always

phobos2077
Explorer

For everyone having issues with Oculus PC software, I recommend to try out ALVR. It's a FOSS alternative. Might not work properly out of the box, needs some fiddling around (for advanced users), but it has more settings than Oculus and you can get the same or better visual clarity with it, depending on your hardware. It even supports USB connection, although a bit clunky (you need developer mode and set up port forwarding), but it works.

TheodonKhel
Expert Protege

@JOE.DANCEN You were lucky enough not to be affected by their failed firmware updates. My quest pro is basically a scam. Not usable for more than half of the time that I owned it. Many people had multiple periods of time where theirs didn’t work either. So yeah I consider it a scam because it is. If I buy a device I should be either get support for it that will fix it or get it fully refunded if they are unable to do so. And apparently they can’t fix it because its not the first time the same bug happens. They don’t offer refund for the scam device they offer either. There was only one firmware version that worked since they started to cause problems. It’s unacceptable. 

TheodonKhel
Expert Protege

@Ryanality @TheAntiSocializer  I'm waiting. My Quest Pro is still unusable garbage that has controllers freezing in the middle of gameplay multiple times and starts having wifi connection issues resulting in massive latency spikes and fps drops in the headset after 30 minutes of playing. You planning on letting people roll back to v56 or are you going to make me wait 3 or 6 more months before I can use that headset properly? 

FIX YOUR CRAP.

tanubon
Heroic Explorer

When can we get inside out upper body tracking?

TheodonKhel
Expert Protege

@TheAntiSocializer Yeah. Sure. Thanks a lot for a like. I'm sure this like gives me whole lot valuable information. You guys seriously are approaching Pimax level support and quality of the software. And that you know - it's really hard to do. It's baffling how bad they are but Meta right now feels not that much better than them and you're shaping up to look even worse than them which is an achievement - in the wrong direction unfortunately. 

TheAntiSocializer
Meta Quest Support
Meta Quest Support

Hey @TheodonKhel!. I know it's frustrating not getting more information regarding the controller tracking issues for ptc v60 but at the moment there's no update that's been provided to me from the engineers to pass along. I have been checking in with the team but haven't received much recently.

JOE.DANCEN
Protege

Hey @TheodonKhel . I understand your sarcastic tone but I don't like it. Don't waist your energy here because it is useless. Wish you al the luck and hope your problem is solved soon

TheodonKhel
Expert Protege

@JOE.DANCEN Sarcastic? There is nothing sarcastic in it. I call it what it is. A scam. 

TheodonKhel
Expert Protege

@TheAntiSocializer I don't think you actually understand the situation here. The engineers you wait for information from have already introduced exactly the same bugs before. Many people were affected by it. It is 5 months total that I am UNABLE to use my headset normally without issues that make it practically unusable. All started after forced v57 update that I didn't want. v59 made it worse.

Now let me tell you the normal course of action that is being done by any company that cares at least a little about their consumers. You roll the firmware back or you allow users to install the older version themselves. A magical thing called rollback is really handy when things go wrong or when the team that develops the firmware messes up again by not learning anything from the past mistakes.

So kindly pass this to your team of the engineers. I want the package with v56 software sideloadable and I don't want to see any update being forced on my device. Or I return this unusable garbage that didn't work more than half the time I owned it because of firmware updates and Meta refunds me what I payed for it. 

If I bought a refrigerator and it were stopping to freeze food every other day for more than half of the time I have it - the store or producent would either solve this issue ASAP or they would refund me. 

It's very easy. I'm done waiting. I've waited long enough. This device's functionalities - majority of it are unusable. 

JOE.DANCEN
Protege

Just return it and go on with your life. This frustration and anger is not good for your health. Just lt return it and forget this adventure. 

FinlessBob
Expert Protege

Honestly my take is, you few that have issues and complaining here will get you no where.
I have a Q2, Pro, and a Q3.  I have none of these issues you all are getting nasty about.  AND let me say, there are thousands that do not either. 

I understand your frustration but, you are the EXTREME FEW not the majority.  You have some hardware or other issues going on because as I said, thousand are not experiencing what the 3-4 people here are raging about.  If everyone had these issues, imagine how bad it would be on social media, etc.  But that is not happening.

So you few should reflect and realize your ranting here is not going to help, nor tell the other thousands of happy people to be concerned.

I wish I could tell you what to do about your issues.  None of these raging complaints are a problem I have.  If you have not used Meta support for a replacement, then you need to.

In the end, you all are a very few...  Take it somewhere rather than polluting a thread here that should be focused on helping Meta get their future releases as best they can.

Sorry my .2 cents....

TheodonKhel
Expert Protege

@JOE.DANCEN I can't return it because I bought it 8 months ago. I wish I could and get my money back. At this point Meta should refund me. Because I couldn't use this headset most of the time. 

TheodonKhel
Expert Protege

@FinlessBob No. You have no idea what are you talking about. Just because a few are mentioning this doesnt mean it's a few having this issue. Not mentioning it's NOT A HARDWARE PROBLEM. This issue was introduced by Meta in v53 update for the first time. They did confirm it's a known issue as well as it's their fault for messing with WiFi drivers and controllers sleep states or something along the lines. It was affecting significant number people but not everyone and not majority either but it was a problem caused by Meta development team. 

Same goes for people who couldn't connect to WiFi 6E networks when 6E was unlocked for Quest Pro at same time as v53.

Same goes for people getting their controllers fully bricked and massive lags when turning your head around. All this was firmware issue that affected a portion of users. v56 fixed this for most if not all people affected. 

Then v57 came and all went to crap. Again same exact problem. So it is Meta update that messed it up and it's a software issue not a hardware issue. Your ignorance is absolutely astonishing. You come here with your goody 2 shoes attitude defending a company that in their incompetence reintroduced the same bug that ruined experience for people for months. But sure. It's easier to jump to conclusion and blindly defend Meta without doing even 5 minutes of basic research. If you spent your time looking into the issues history instead of playing white knight, internet justice warrior for a multi billion company you wouldn't even write this in the first place

Edit: Also someone in another thread actually got a brand new quest pro/replacement and has the same issue with controllers. so again. It's not the hardware issue 🙂

JOE.DANCEN
Protege

Let's move on with the v60 thread please 🙏 

 

Anagan79
Expert Protege

Since the v60, on Quest Pro, if you change FFR level in game, the pass-through just freeze until you restart the device. FFR level set to dynamic and Off are okay but low, medium, high and very high make it freeze.

You can reproduce with sidequest for example or any adb command

This doesn't appear on Q2 and Q3

Benuno
Honored Guest

"Since the v60, on Quest Pro, if you change FFR level in game, the pass-through just freeze until you restart the device. FFR level set to dynamic and Off are okay but low, medium, high and very high make it freeze.

You can reproduce with sidequest for example or any adb command

This doesn't appear on Q2 and Q3"

Confirming this, had no issues with v59. Currently, FFR Level changes besides dynamic/Off unusable on a Quest Pro due to this bug.

 

 

 

TheodonKhel
Expert Protege

@JOE.DANCEN Sure. Let’s forget meta made people headsets unusable for months and give them the pass to continue scamming people with absolutely 0 repercussions or compensations towards affected users. I’m pretty sure they need even more money. 

STUPIDfirestorm0174
Honored Guest

some of these so called updates make you wonder if they have full time developers or just some amateur doing it in his/her spare time after a hard days work . Then you read that 50 billion (omg)has been spent on something .....clearly not on genius whizz kids or experienced masters .....but hey keep up the good work .

TheodonKhel
Expert Protege

@STUPIDfirestorm0174 that’s what happens when you lay off over 10000 employees and people who take over testing have no idea what they are even testing. Or developing. 

imagine causing the same exact bugs that have been fixed before. Bugs that make many headsets unusable for weeks or months. It is either utter incompetence or people who have no idea what they are working at, taking over and making the same failed changes without looking at the past mistakes. 

and even if it is a case that bugs happen and couldn’t be avoided: meta knowing these issues turn headsets into paper weight should allow users to install software version that is bug free for them. But we cannot downgrade to versions that worked for us reasonably well. It’s a massive joke that company like this doesn’t know a magical thing called rollback

Cloakedman
Protege

As soon as my quest 3 updated to v60, I started having occasional rainbow artifacts (lines and dots that flash briefly on the screen when moving in game) appear when streaming pcvr games using virtual desktop. I haven't tested thoroughly but this seems to be an issue only when streaming games from pc, not with standalone games as much.

Virtual desktop people say it's an issue on meta's side. This needs to get patched soon or atleast give people the option to rollback to v59. 

FinlessBob
Expert Protege

The random pixel flashing is not new to V60.  It started on about V53 on the Q2 and I see it as well on the Q3.  This is not just a PCVR thing either it happens on native games.  It's never been fixed.  Not sure if it's the same thing you are seeing in PCVR as I have not tried PCVR yet on V60.

ravindra.sonavane
Honored Guest

Hi Guys, Need some help. I am VERY CONFUSED

I have two Oculus Quest 2 devices. And I updated one of them to the latest quest update version available. However, one of the Unity VR game that I have developed does not work (fps is really low and huge flickering) on the updated version, but works perfectly fine on Quest 2 with the older update Version. 

Quest 2 details with new quest update:

Version - 60.0.0.173.366.544898056
RunTime Version  - 60.0.0.175.366.544897891
OS Version - SQ3A.220605.009.A1

 

Quest 2 details with older quest update:

Version - 59.0.0.173.706.535795449 
RunTime Version  - 59.0.0.172.706.535797236
OS Version - SQ3A.220605.009.A1

 

I am not very sure why is this happening, I have also resetted the Quest 2 with newer version but it encounters the same issue. can someone please help ? Created a thread on developer forum for this.  

https://communityforums.atmeta.com/t5/Unity-VR-Development/Unity-Vr-game-encountering-low-fps-and-ji...

erickzera
Explorer

They did not fix the flashing pixels bug. I've updated my Q2 yesterday, after being on v54 (which was running almost with no artifacts) for a while. And that's really sad, I was considering the upgrade of my Q2 to Q3, but i was reading that this is a problem even on the newest headsets, so...

 

I'm starting to lose my hopes about this. Thanks guys.

 

JohSm67
Rising Star

I posted this in another thread as well, but to be sure that it's addressed i do another Post of it on the V60!

Meta Quest Pro has serious tracking problems with the Touch Pro controllers!
This issue has been seen since v57, now i'm on PTC v60 and the problem is still there even worse!
Controllers are lost during usage (Oculus button still works)

Problem is not seen if I use 2.4GHz Wifi or no Wifi!
Problem occurs only if you use 5GHz Wifi.

I have tried to use a dedicated WIFI accesspoint as well as accesspoints with roaming and there is no difference. Using a Unifi WiFi network with AC Pro AP's (WIFI 5) that has been working flawless with the Quest Pro, and I have not see any issues with the Meta Quest 3 or any other WIFI devices. 
Quest Pro seems to be connected all the time, but Touch Pro controllers are lost randomly and dissappears for a while and then might be appearing after some time.

Had the Quest pro and Touch Controllers replaced, but that didn't help, same problem.
Have tried to reset the Touch Pro Controllers and re-pair them and also reset the Headset, same problem.

When the touch pro controllers are lost they do reconnect if you disable and enable the Wifi connection, but they will be dropped by the Quest Pro again at a regular interval.
 
Did now exit the PTC release channel as I need a stable release as it's impossible to use the 5GHz WIFI network. (But I guess it won't help as I did this once before and was unable to get back to the public release.)

Systemversion 50134520056800330
Version 60.0.0.191.366.547773830
Running version 60.0.0.193.366.547773779

OS version SQ3A.220605.009.A1


Headset-version 50134520056800330
Touch Pro FW 1.32.2

Would be interesting to see if there are any available release notes / bugs or bug fixes available for this issue? (Are we able to get some feedback on what's known issues or whats been fixed in PTC releases?)

Also any guidelines to do more debugging or access to log files that may bring more clarity to the problem.
Can you get any more information about Touch Pro controllers and why they seems to stop working for no reason, any other reports or findings from support? I have reported using the bug report tool, but you do not get any feedback on those so i'm a bit blind right now!

How do the Touch Pro controllers communicate with the Quest Pro?
(Why do the Oculus button work when controllers do dissappear?)
Are there different FW versions on the Touch Pro controllers that might be an issue here?

Really need some support or feedback here now!

tanubon
Heroic Explorer

Recently I often get tracking lost error on Q3. Until recently, tracking was possible even in a room with the lights off.

OldTarget
Protege

I have a Quest Pro controller tracking issue in PCVR (Using Virtual Desktop) after long period of use.
Everything is working perfectly for the first two to three hours. 
Then the controller tracking stop working. You can restart as many time the controllers, the tracking will be lost every one to two minutes.
Maybe it comes from the controller overheating.

zbnc
Explorer

posting here to echo  ravindra.sonavane's  issue regarding our live app suddenly tanking performance on Quest 2 with the v60 update. We've confirmed internally that devices with v59 do not experience this issue. Any insight would be appreciated, as this issue is live and affects users. 

alexvr2024.2023
Honored Guest

De cand OQ3 meu a trecut la versiunea V62 am nimai probleme.

Din 2 in 2 minute se apare notifificarea ca are a PO a si gunoi in usb🤔. USB este curat ca lacrima **bleep** era si inainte sa faca update . Eu o folosesc conectata la baterie externa si sincer nu mai pot folosi bateria. Inainte mergea perfect si doresc sa instalez o versiune fara probleme ca sa ma pot bucura de el. Vreau o adresa unde gasesc firmwarele vechi sa pot sa scap de mizeria asta