Skip to main content
DwightMc25
Inspiring
January 25, 2025

PTC v74 Release Thread

Hey Everyone,

The Public Test Channel (PTC) for Quest v74 started to roll out today for Meta Quest 2, Meta Quest Pro, Meta Quest 3 and Meta Quest 3S.

If you're seeing an issue or bug after updating to PTC v74:

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 v74" to the thread and in the title. This way everyone can look for just PTC v74 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. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong.

Share your impressions in the comments below and let us know if you see any issues.

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!

 

247 replies

stereoman
Up and Coming
March 17, 2025

First off it's the weekend, nobody has any idea how many people are having issues with v74 right now apart from Meta support and the majority of users who are havving issues probably aren't going to post about them on a community forum, the fact that you see more than a few people posting about these issues is more of an indication that there maybe a larger problem with v74 and what we need right now is less posts trying to deflate this situation as it undermines the users who are having these issues including myself as all people want is to have thier headsets working properly again.

Appreciate the tips tho, personally already tried dropping from PTC and resetting m,y headset to factory made no difference, still can't charge beyond 76% and still get the weird flickering once I get to 76% charge, I've sent a report into Meta so all I can do now is wait.

New Participant
March 17, 2025

In my quest 2, anytime I'm trying to play a game on my secondary account, the controller outline is overlapping the hands in-game. This is genuinely so annoying especially in games like into the radius and other immersion games and hinders my experience.

I don't know If anyone else is having this problem but it just started with v74. I do have app sharing enabled between the primary and second account.

Honored Contributor
March 17, 2025

stereoman   Said; ' the majority of users who are having issues probably aren't going to post about them on a community forum, '

Mate, the majority of posts in all user forums are those having issues, lol!  On forums like Reddit it's probably +90% imho.  I think a large portion of those are from Reddit kiddies who always have exactly the same problem and/or and meta-haters (eg. Meta software always sucks).  In many cases I don't think many of them even have a Meta headset.  That's the main reason I stopped posting there and eventually got rid of my Reddit account.

If you've recently actually unenrolled in PTC and Developer mode, done a factory reset, and avoided any and all 3rd party mods, then I guess that's about all you can do for now. 

I'm sorry I can't be of any further help mate so I'll sign off and avoid posting/replying to any of your current issues on this forum.  Again, I hope you eventually get your issues resolved.  Good luck, bye, and cheers. 

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers
Honored Contributor
March 17, 2025

H0TD0G2134   This issue was also noted earlier in this thread by Choleni  ;

https://communityforums.atmeta.com/t5/Get-Help/V74-update-issues/m-p/1303834#M359890

Like him, you should fill  bug report on this and hope it gets resolved soon.  Cheers.

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers
stereoman
Up and Coming
March 17, 2025

TomCgcmfc
What I mean is not everyone who has issues with thier headset posts on forums, some people go straight to official support lines rather than posting on a forum and all I'm saying is nobody knows how many people are having issues with v74 right now apart from Meta and speculating on it doesn't really help anyone but yeah I'm appreciative of any help from anyone on this forum if it can possibly solve these issues, I'll give anything a try but right now I've pretty much exhausted every avenue as far as being able to solve these issues myself.

d0gg
Honored Contributor
March 17, 2025

stereoman 

Wasn't trying to deflate anything.

I am one of the people that posts issues when they come up to share them with others here and at other forums. I also share when the issues are fixed and try to offer suggestions to help others to get past the problems.

I was just commenting on the fact that if there was a very widespread issue there would be articles in mainstream media about it. People LOVE to talk about the big tech companies messing up things.

There is definitely a problem. And it is a big problem. But it is something that is happening to a smaller number of users. Which SUCKS because when it is a smaller number of users that means there is less reason for Meta to move quickly to fix it. (when I say smaller I am saying a couple thousand rather than tens or hundreds of thousands)

When the issue came up with the update a few months back, that was causing Quests to go into a boot loop, Meta made good on that within a few weeks (it takes time to set up an actionable plan to care for customers).

If you just dropped from the PTC, it won't help because you would have just gone to v74 again (v74 is now in public release, you can't get v72 anymore). The drop from v74 that fixed issues before was because it brought the system back to v72.

One other thing I did read about the charge level. When you are seeing that it is stopping at 73-75%, it might actually be at 100%. Someone that connects to PCVR using oculus Link saw that the battery level in the on screen oculus link status shows that the quest is at 100% even though the quest reports 73-75%. So it might be just an error in the reporting of the battery level that needs to be fixed (hopefully).

Here's to hoping they get this stuff fixed for those that are still dealing with the errors.

Quest 3-[512GB] - v.78 (non-PTC) {PCVR} Predator Orion 5k (i7-14700F - Noctua NH-U12A Cooled)-64GB Crucial Pro 5600 (16GBx4) 8TB SSD (2x1TB Predator Helios PH18 SSD - 2TB WD Black SN770 SSD - 2x2TB Samsung 870 EVO SSD) Predator Nvidia RTX 4070 Ti Super - Win 11 Pro AXE5400 tp-link - Virtual Desktop
stereoman
Up and Coming
March 17, 2025

d0gg 

Fair enough I probably just got the wrong end of the stick as this all just a bit of a frustrating situation and as I say I do appreciate any possible solutions

last time reverting to v72 fixed it but as you said it's no longer an option and I've pretty much tried everything else apart from completely draining the the bettery which I am currently in the process..

Anyway hopefully this will all get sorted out sooner than later.


Honored Contributor
March 17, 2025

I found an interesting option today on my non-beta v74 with my Q3.  The boundary settings now include an option to adjust the stationary boundary size (small, medium, large).  When you adjust these it immediately shows you the corresponding floor circle size.  I think that small is pretty well what we had in the past.  The Large option is very large and I think you'd need to be very careful using this.  I've set mine to medium for now.  Overall, I think that this is a great option.

One thing I noticed is that during my Q3 startup (or restart) I don't seem to get the Confirm boundary panel, just the stationary circle, that then disappears when the startup is complete.  I don't currently have any room boundaries setup so maybe you'd get a confirmation panel as to which one you want to use.

I don't see this option on my non-beta v74 with my QPro (and still get the boundary confirm panel during startup).  Maybe because it hasn't been rolled out yet, or maybe it's just going to be a Q3/Q3s thing.  Who knows?

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers
PenguinInChicago
Inspiring
March 17, 2025

Anyone else noticing issues like:

  • Controller issues like becoming hard to control cursor.
  • Tracking Issues especially connected with horizon worlds 
Thanks, Derek aka Papal Penguin https://www.papalpenguin.com https://twitch.tv/papalpenguingaming
Honored Contributor
March 17, 2025

PenguinInChicago  No controller or tracking issues with either my Q3 or QPro.  If you post this on Reddit I’m sure you’ll get lots replying that they have exactly the same problems, lol!

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers