Thanks everyone for all your feedback on our previous builds, we several bugs were identified in the last PTC and the solutions for some have shipped, while others are on the way!
The Public Test Channel (PTC) for Quest v56 is starting to roll out for Meta Quest Pro and Meta Quest 2 soon.
We're going to try out something new this time around! Instead of a single megathread, we'd like to gather feedback for specific issues in their own separate threads.
For example, if you've installed PTC and there's a sticker of a pink elephant unexpectedly following you around the room, jump on over to our Get Help board and search for "pink elephant PTC" or something like that, if you don't see any existing threads, make a new thread in there, put PTC v56 in the title and something like "Haunted by Pink Elephant", and post it. If you add the Label and Tag PTC it'll help everyone search for just PTC issues too. If anyone else is seeing the same thing, they can find your thread and jump into it to share.
Moderators will also help merge topics that are the same together so keep things consolidated.
It's best if you can post each bug you spot in it's own thread, that way we can all keep track of individual issues separately, and can notify everyone seeing the problem when there's news, or we need to collect details.
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!
I got the version 56 update tonight. I see local dimming as an option under experimental which is nice. Going to test my wifi 6e and do as you suggested. Create a theead, etc.
can say that I tried Iracing which was great. Also jumped into horizon work rooms. Since v54 any web page I would visit while in workrooms the white background on web pages was so bright you could barely read the words. After tonight’s update it’s perfect. Not sure if that is the local dimming but it’s absolutely perfect. Could easily work for hours in that. Will update and create a thread with any issues. So far so good.
I started a separate PTC v56 thread for the ongoing Flash white/colored pixel artifact issue as per the instructions from @Ryanality above, for which the issue is still occurring for me even after the update.
I tagged it with PTC so people should be able to find it using his link for searching "just PTC issues" at the top.
I'll see about creating a thread on this after some further testing, but in this build Meta Quest Pro doesn't seem to be able to remember Guardian Boundaries after headset restarts. I get a prompt saying "Boundary Not Saved" and it advises me to restart again to fix it, but this seems to have no affect.
@arc_101 Tried Lone Echo 1 with Air Link and it all looks fine to me. Maybe make sure your Oculus Desktop app is also on v56. I'm on the settings/general/beta tab public beta enabled. Mine updated earlier today.
So far everything is working great with my QPro/rtx4090. Local dimming in a few standalone darkish apps like Cosmic Flow look very nice. Tried a few Rift, Steam, and VivePort games and flight sim msfs with Air Link and all seems to work well. Might just be placebo but the overall clarity seems a bit better, and going in/out of Air Link seemed a little better as well.
Now if only my Q2 battery management will work properly again. On charger now so I guess I'll find out soon, lol!
... Now I'm getting a "critical error " saying that it could not update the meta quest and to restart my computer but the problem persists after I restart my computer...
But it says it inside the headset when I tried to use Oculus air link... Now idk what to do
Holy cow... Testing this release now and it is seriously BAD.
I have like 50 purchased games and only a few work. Like Real VR fishing works but almost nothing else.
When V53 came out and the Android level upgraded, I had to reinstall 90% of my games and apps as they did not work. All fine. I just did a factory reset and started over. BUT IT TOOK HOURS to reinstall all my stuff. For instance Medal of Honor took hours. WDSS etc took huge amounts of time. And I am sure the stores bandwidth was getting hammered by people having to do this.
Please don't do this to us again!
I understand a PTC release is going to sometimes do things like this... But this release is SERIOUSLY jacked up!
FinlessBob: what you described doesn't seem to affect all Q2s. I can run purchased and sideloaded apps no problem on v56.
Unfortunatelly Beat Saber still exhibits micro hiccups. It happens like once or twice per playing a level but even that is enough to cause stupid misses and brings frustration. I first noticed it in v55 and there were numerous reports of others too. Not sure if it is related to Beat Saber update or Quest update.
@FinlessBob Tested earlier with my QPro/rtx4090 and all worked fine with standalone apps (don't have any sideloaded ones and don't play BS) and PCVR with Air Link. V56 PTC and v56 on the oculus desktop app public beta.
I just finished testing my Q2 and everything also worked well with standalone apps (all Quest store with a few applab ones) and PCVR using Air Link (I don't use a Link cable anymore) with Rift, Steam, and VivePort apps. Also tested with MSFS. Everything is working very well so far. Unfortunately my headset battery still does not seem to charge above about 85% but not a big deal since I can use an external 10000mahr battery pack for longer runtimes if need be. Plus, I'm not really using my Q2 much anymore, preferring to use my QPro.
I still see the very odd pixel sparkles but they seem few and far between and don't seem to bother me.
@FinlessBob I'm sorry that you are having issues. I have seen a few with problems on Reddit related to some sideloaded apps and mods so maybe that may be part of the problem, who knows? Maybe search Reddit for v56ptc and see if you can gleam anything from those posts.
OK so I tested something. I uninstalled a game that would not run. When I say it would not run I just get the 3 dots and it hangs. I have to reboot to get out of it. Anyway I uninstalled one (NFL Pro) and reinstalled and it runs now.
So I see some people did not have this problem but I do. Not sure why?
Thus I have choices. 1) OPT out of PTC and see if my store bought games run again.
2) Uninstall anything that does not work and reinstall. This is a bummer because not all games backup to the cloud and restore saves. 3) Factory reset and just reinstall everything. Again loosing saves for some games that do not cloud backup.
Which choice should I do? I don't want to OPT out of PTC to be honest.
When I try to launch a store bought game Coaster Combat, all I get is the scrolling white dots and it hangs there. At that point, If I hit the power button once to put the Q2 to sleep then I hit the power button again to turn it on, I see a quick flash of a screen. It looks like a circle with an arrow through it and the text says "No google play store key". The next line says something about no OOB found but it flashes so quick I cannot read it all.
OK so based on my post above this gave me a clue, I plugged my Q2 into the PC and opened the Q2 removable drive that appears. In the /android/oob folder all the oob folders for almost all my games are GONE!
So this update for some reason deleted the oob folders.
So that's it. Nothing I can do. I have lost all games saves that do not backup to the cloud.
Bummer. I might as well factory reset at this point 😞
FinlessBob: Oh that's nasty. I believe user related app data like game saves usually reside in /android/data not in /android/obb. Both folders can be backed up and restored manually or via SideQuest PC app. So there is a chance your game saves have not been deleted, unlike obb data.
@tomas.vala, yes I checked Android/Data and those folders are gone too. I know /data can be backed up and maybe I should have done that but I did not. Lesson learned and from now on I will back it up.
OK so I have not factory reset in a long time. Possibly a year. I just did and I really like the new wizard that lists all your games and apps and lets you decide what to reinstall or not.
That is pretty cool.
Now I WISH they would allow us to "hide" games and apps from the main launcher screen. I get tired of seeing in that "default" list demo's and what not I just do not want to see anymore. Yes I know I can filter but those filters do not "stick" and I am constantly getting the default filter that shows all that junk.
Hey hey everyone! Friendly reminder that @Ryanality has us trying a new method for PTC feedback with this one. This is not a megathread for issues with the PTC, but rather an "un-megathread". Instead of the normal PTC megathread, we want to see you all posting in separate threads for the specific issues you're experiencing to be able to better track them.
Make sure you read @Ryanality's original post for some details on how to make sure you search for any existing threads before creating your own so we don't have any duplicate threads clogging up the Forums!
Yeah. BIG EFFFING THANK YOU META. I was FORCED to install PTC v55 because v54 broke my controllers tracking to the point it would freeze controllers for 2 seconds every 10 seconds. Unplayable. I opted out when I heard v56 is starting to roll out. Unfortunately I STILL GOT THE V56 ANYWAY on my headset and of course now my left controller is bricked COMPLETELY. It doesn't pair at all. I got the update back to v54 (yeah it seems v55 didnt roll out for me yet) and still it doesn't pair neither through the first setup phase after factory reset nor when using phone app. I heard one person before having that happening a few weeks ago.
YOU MADE MY HEADSET UNUSABLE THROUGH YOUR FREAKING PIECE OF CRAP UPDATE. NOW GIVE ME AN UPDATE THAT WILL FIX THAT FREAKING PROBLEM RIGHT FREAKING NOW. I HAD NO ISSUE WITH CONTROLLERS AT ALL BACK ON V51. IT WAS PERFECT. BUT NO YOU HAD TO RUIN IT ALL WITH SUBSEQUENT UPDATES AND NOW TO THE POINT NOT EVEN SOFTWARE REVERT WORKS. BIG FREAKING THANKS.
UPDATE: ITS EVEN WORSE. RIGHT CONTROLLER NOW KEEPS RESTARTING AND ITS HARD TO GET IT TO WORK. GOOD EFFING JOB META. AMAZING
> This PTC release should have never been distributed. It's THAT BAD.
Negative statements like that show a profound lack of understanding of how software works. They need lots of people to test precisely because updates do not work the same on all devices. If the update being that broken was common, they could not have pushed it out.
@JorgTheElder I understand that nobody should deploy any controller updates that deal with controller connectivity if the controller design doesn't have a failsafe in case update bricks the connection and pairing of the controller. Since the only way to update controller software is by having it paired (no USB-C port so even if there was a firmware to upload with PC there is no way to connect). It's the complete omission of any logic in the development process. Updates like that should not be deployed at all before testing internally for a long time.
So one of the goals I think I read moving into quest 3 was focusing on mr/ar….well it would be nice for it to just work in general…like when you record mixed split reality from a cast…why does it not save when it decides to quit working….why?…I have to do the same thing sometimes 3-5 times and it’s only always possible to recreate an epic moment …this update has caused things to just decide not to work.
Thx for the great changelog Meta, must have cost you a lot of time 🤣
As long as we spend time in reporting bugs you dont care in trying some real communitcation with youre customers i guess
When will the Epic Failure of the Wifi 6E support get fixed, since youre faulty implementation of a standard doesnt support al lot of brands like TP-Link Deco's , Ubiquity , etc...
I have lost my left controller a few times along these update paths, and based on what I read i always get scared, but re-pairing it while it was a pain always seemed to work. took a lot of getting it into pairing mode, sometimes 3-4 times or even more, and clicking a lot of buttons but it always ended up working. i am sure you guys have tried the things i just said, but i think its patience and re-trying. i think the only bricking that would occur is if the controller died while it was upgrading - i doubt that is happening.
it always seems the left controller is the most delicate but i bet anyone that is having the issue with enough patience it would end up working again.
@jdawg46.1976 I tried pairing, reseting, factory resetting so many times. No matter what I did it just wouldn't pair. I even left it in pairing mode for like 20 minutes and still failed. Meta screwed up big time. Not even pairing during first setup works. Not mentioning entering pairing mode on left controller through phone causes my right one to disconnect and needing restart to connect back. It's freaking stupid and the developer that put out the change like this should be held responsible for bricking the controller with dumb software update. It takes some real talent to hard brick something in this day and age with a software update.
I’m a quest 2 user I’m using quest pro controllers since I updated to V56 I started to have problem with my controller right joystick has started to drifting, I’m wondering if someone more than me that has started to get this problem also?, I don’t remember if it started before or after V56 pro controller firmware update
@Skaveny Stick drift is a mechanical problem. It happens even to the Q2 controllers. I have had to fix it myself more than once over 2+ years. On one controller I had to tear it down and replace the joystick which I bought on Ebay. There are some good youtube videos on how to get at the internals of the joystick and spray it with tuner cleaner. However with these new controllers there may not be videos on doing this yet. I would think they are still under warranty so get it replaced.
Personally with the amount of people I have seen on Facebook groups fighting stick drift, Meta should use better joysticks.
Hey hey everybody! Thank you so much for taking the time to test out v56 for us, and continuing to share your feedback about what you're experiencing with this PTC update. Your feedback helps us with identifying and tackling issues before they're released in the next official update, and we appreciate it so much!
To ensure we don't miss anything, we're asking everyone to chime in on the existing threads in Get Help for your unique issues. And if a thread doesn't exist for your issue, please feel free to create one, just don't forget to add the PTC tag! This will be the best way for us to track issues and raise them up to our team to get a fix before the update gets rolled out to the rest of the public. Thanks for all of your help everyone!
They added new mode (Quality mode) of Link Sharpening. Meta says it's using Snapdragon Game Super Resolution. But it doesn't make better pixel density on Link unlike Virtual Desktop's SGSR. And much more blurry than Normal mode except edges, worthless for me. People who think Normal is too sharp may like Quality mode.
Link needs more pixel density... VD has clearly higher pixel density on the same render resolution despite using only 1/3 VRAM usage. Link uses too much VRAM, but lower pixel density.
I appreciate the idea of the gethelp for major issues, but honestly I don’t have time to hunt down ticket items. I am hoping there is a way to link those to the side of the main v56 PTC site for easy viewing if this method continues.
I work with systems for my job and hope to provide productive feedback each time like I would want to have for my own. Here are my latest notes:
Close X’s keep switching sides, now on the right side. I’m not sure why, but adds another relearning step with each build. Please pick a side and keep them there.
Pointer now has a circle selection function. I can see this being a fun add for the devs, but not necessary for users vs other changes.
When the taskbar/explore window first appears, it is really close to my body now and I constantly have to move it well over a foot away so I can use it without bending my wrists. It was never like that before this release, so whatever coordinates/location it is using have changed and should be changed back.
Application default sort/view option that was in the setting section (& wasn’t functioning) is removed. The default app window sort/view wasn’t set to most recent, but seems to be staying after I used the search box to set it. It still shows all apps vs just installed ones, but the most recent sort at least puts the ones I use a lot on top.
Explore window still isn’t as useful as previous version that was wider and had left side navigation options that made me curious enough to use. Current view/size sometimes only show one item on the left side and I just close it most of the time. If it remains as is, I would opt to disable it and just use the menu selections on the taskbar.
Suggestion across all the taskbar menu windows – make them as wide as the Store window so more content can appear and as previously mentioned, add the left navigation pane back to the explore menu.
Also, when not in Multi-Window mode, it would be a user friendly function to close each menu window when you click on another one on the taskbar. This would be a much smoother transition between windows vs having to close each one before clicking on the next one (or having to go back to close the last one).
When posting to a facebook group, the last group you posted to doesn’t appear right away. I use the same facebook group to post pics instead of offloading them using sidequest all the time. Having the last one I posted to present as a default with the ability to select others was a really nice function. It was like that in the past several builds.
Passthrough seems to be activating a lot easier than ever before whether playing standalone games or via airlink.
Lately I have been playing Asgard’s Wrath using airlink and twice I activated the passthrough and could not get back to the game. Instead, there was a black screen with the guardian showing. The game was active/paused on my laptop and I had to restart the headset and reconnect to the airlink to go back into it.
Personalized skybox is not always automatically present. Sometimes it is a black skybox and other times it is the default one. Usually going into a game and back will refresh it/put it back in place.
I cleared my guardian history and re-setup my boundary when I received the new version. For a few days it was ok, but recently the floor level has been off again sometimes by over 20 cm without any lighting or other changes in my physical playspace.
Q2 headset starts to heat up on the outside of the headset more and more. I have also noticed a decline in battery life where even 30 minutes of standalone game play = 61% battery life left. This was not the case before recent 2-3 releases and I play the same standalone games. It started ~2 versions before this release, but I have noticed it more so with this one. Wondering if some of the increased resolution, etc. is heating up the chipset in ways the Q2 isn’t setup to handle.
I am having to use a back up battery more and more. When using airlink, the battery will show 100% upon returning to the main Q2 menu as long as the battery pack is attached. When I remove it, the battery goes down to real % immediately, which could be close to 0%.
went off ptc due to the major issues with v56 and my headset went to official v55 release which is great, however my oculus app on PC went to v54 for some reason. I was wondering why airlink suddenly went to **bleep** again when it was briefly so good on v55. Repairing now to hopefully get the update and will use VD if not, but thought I'd share for anyone else who downgraded
quest2 has now been updated to v56.0.80, I did not run airlink, but I already noticed that when opening windows in the Oculus house, white noise appears for a moment in the middle of the window, similar to airlink. The function of typing with a finger without looking up from the keyboard seemed to be a useless function, because. quest2 has a large delay in determining hands and inaccuracy, which is why such input is very problematic for me.
I also want to note that the process of turning on the helmet became noticeably faster and became about as fast as on v4x firmware, I don’t remember the exact figure, but it was the time when the meta began to release the 128Gb version of quest2. I also didn't like that with the performance increase, the resolution of the oculus home remained the same, its resolution needs to be increased at least a little, because. he is very soapy
As long as I have been in the PTC you don’t get notifications of new releases. They just come when they are ready. Your best bet of a notification is in this thread by other members or in the Reddit forums.
@g0dmak3r This could be caused by Mobile ASW. You can disable it in the Oculus Debug Tool located in: C:\Program Files\Oculus\Support\oculus-diagnostics
I just got a v56ptc update earlier today with both my QPro (56.0.0.114.656) and Q2 (56.0.0.115.656). Tested both out with standalone and PCVR using Air Link (don't bother to use my Link cable anymore). Tried a few standalone and PCVR titles from the Rift, Steam, and VivePort stores, plus my msfs flight sim and all seems to be working great. This is with the latest nvidia 536.67 driver with both HAGS and Game Mode off.
I did still notice the odd white pixel sparkle on the right lens but these were very few and far between. These seem even less than previous updates as far as I can see and don't bother me whatsoever.
I'm not sure if my Q2 battery management issue (never fully charging to green) is fixed yet. Its on the charger right now so I guess I'll find out soon, lol!
Edit; Nope, my Q2 headset battery will still only charge up to about 85%. Oh well, at least when I plug in an external battery it seems to hold that charge level and just draw from the external battery. While I'm pretty sure this is an Android 12 battery management related issue, I guess it could just be that my +2yo Q2 headset battery, like me, is starting to show its age, lol! If I contacted Meta Support I'm sure they'd help me out with a refurbished headset. But, since the Q3 will be coming out soon, and I intend to buy one, it's probably not worth the effort right now.
Has anyone been noticing that the mirror in the home environment sometimes randomly turns black and stops working until i restart? Also has anybody's face been freezing when looking at the mirror in the home? my eyes completely disappeared from my face once, which is a little spooky. There has been also a weird figure with arms detached (about 1 ft foward from torso) (completely black, void like) after leaving a party when in home with a person? This update has spooked me alot from these bugs, and it doesnt help that sometimes when changing stuff in the menu this loud static plays for about 0.2 seconds and the menu turns black. I'm very scared from this update and i am about to uninstall it. please help (edit: forgot that sometimes i get stuck in a void with notifications and my avatar still there.)
@Persvicx Sounds like your Quest is haunted by the ghost of Oculus Past, lol!
Actually, since the last few PTC's, starting up in my Quest home (one with a mirror) my controller arms are black or missing and the controllers have a white outline around them. If I look at the mirror there is a really scary skeleton/ghostly figure staring at me. This usually only takes about 10-20 seconds to automatically revert to my chosen avatar/arms and the controllers then look normal. This happens with both my Q2 and QPro, but seems to take a bit longer to fix itself with my QPro.
Also, occasionally when I use Link or Air Link (one I mainly use) and get into the Rift Home void/dashboard the controller/hands do not show up at all. In those few cases I find I need to exit link, go back to the Quest home and restart Link. Then they appear again ok. Again, something that seems to happen with my Pro controllers more than with my Q2 controllers.
Anyway, I think that the best thing to do is to file a bug report (bug-looking icon on your quick menu). I have done this over the last few PTC updates. Maybe eventually these minor bugs will get squashed, or in your case, Exorcised, lol!
@TomCgcmfc Another weird issue that i seen with only this PTC, changing the Camera values in the Meta Quest Developer Hub. If you change the camera quality to a 16:9 ratio (or one with a higher fps) it results in a weird RGB colors coming off of objects for 1-3 seconds until it changes normally. One time it got stuck on it, and the RGB colors kept getting bigger, Bigger, AND BIGGER! I held the power button, it showed the meta logo, but with the weird edgy colors, and then BAM! I saw the android shut down prompt on my screen (I have never seen 2d android element overlays while using quest. Looked like this.
It was layered between the two eyes, didnt look correct, and i think it was not meant to be shown. Layered over the meta logo, i could see the borders of the logo.
This is definitely a bug, but I like these types of not seen errors. Infact, I'm trying to log every hidden app and every error on the quest, its very fun to find
(if you have any screenshots of errors or just weird stuff happening PM me to add to my Mega Quest Error Log)
I'm new to the beta test, I understand that the release version of v56 has come out, and I'm now on PTC v56.0.0.115, will my quest2 be updated to the official full v56 or just the next PTC?
