These features and enhancements will become available starting the week of September 11, 2023 and will be pushed to Meta Quest Pro and Meta Quest 2 headsets. You can always find the most updated release notes on our official release notes page.
Expanded Locomotion in Horizon Home
You can now freely teleport within your Home, similar to how you can teleport to move around in many VR apps. Press your controller thumbstick forward to bring up the teleporter, aim at a spot in your Home and release the thumbstick to teleport. You can also use the pinch gesture with your hands by touching your forefinger to your thumb to bring up the teleporter.
Meta Horizon group links
We’re making it easier to invite friends to join your group. Now you can generate a link to your group and share it in VR or copy and paste it into any messaging platform you want.
Inviting a Meta Horizon group to an app
We’re making it easier to meet up with your friends in VR by inviting your group to different experiences. Now you can easily invite your group to an app from your People tab. Also, when you invite a group from within an app, the invite will display in the group chat so everyone can see it and easily join you.
Unsend image messages
You can now unsend image messages in VR and in the Meta Quest mobile app by hovering over or tapping on a message and selecting Unsend.
Direct Touch added to Hands tutorial
We’re updating our hand tracking tutorial to show you all the ways in which you can use your hands as controllers in VR, including Direct Touch. You can find the updated tutorial tutorial in the Guide app.
Contact list
When you turn on your Meta Quest headset your contact list will automatically open. This makes it easy to chat with and meet up with your friends, no matter what you're doing in VR. If you close your contacts list, you can always reopen it from the People tab.
Video recording improvements
You can now set a default option to include or not include microphone audio when recording video.
Introducing Horizon Feed
Horizon Feed is replacing Explore. Horizon Feed is the landing surface in VR where you can find apps, entertainment and community. Discover your new favorite app, watch Reels from Instagram or Facebook, and travel to popular destinations.
Multitasking improvements
You can now use multiple apps simultaneously in a near and far configuration, allowing you to interact with your hands or controllers. To switch between views, select Switch view from the Quick Settings panel.
Avatar editor updates
You can customize the color of your avatar’s hair, eyebrows, and more, using the real-time avatar editor mirror available in select Home Environments.
This feature will be rolling out gradually.
Mixed reality and boundary
Some apps with mixed reality experiences no longer trigger a boundary warning when you approach or pass the boundary area, allowing people to safely enjoy the experience without interruption. You’ll know the boundary is turned off by a notification when you launch the app.
Removing Meta Quest casting mobile camera feature
We are removing a casting feature from the Meta Quest mobile app on iPhone which allowed you to simultaneously capture your VR experience and your real-life experience using your phone camera.
NIce to get these improvements ???? NOT ! i'm in the PTC running the latest version I haven't got half of this stuff and my avatar still stands in front of the mirror with it's back to me with his arms out not moving, no improved avatar editing ?, no horizon feed on start up ? No contact list opening ? So it none of this is working in the PTC how the hell is this released ??????????
@Okuda.IOI I think it would be more useful for you to include the actual version #'s you currently have installed with PTC V57. For me it's 57.0.0.236.669 on my Q2/QPro headsets and 57.0.0.238.153 on the oculus desktop app public beta. That way, those that get the non-beta V57 can properly compare notes.
Also, as usual with all releases, new features are rolled out over time.
Sound like a few quest users have reported that there is a problem with the latest V57 final so I thought it may be useful to post my reply regarding this;
OK, while I also normally use Air Link I switched of to my usb3 Link cable (Kuject powered Link cable I bought from Amazon +1.5 years ago for my Q2) and all worked very well with both my Q2 and QPro at 650mbps bitrate. I tried a number of Rift and Steam games and these all worked great. Also tried the flight sim msfs and this also worked great. I actually forgot how distant objects look quite a bit better with Link.
I am on PTC V57 on both headsets (version # 57.0.0.236.669) and on the oculus desktop app public beta (version # 57.0.0.238.153). Maybe check both those version numbers and see if they are the same as your final V57. You may want to opt into the oculus desktop app public beta and give that a go (settings/beta tab). BTW, I've been on the PTC's on both headsets and the oculus desktop app since V51 and haven't had any problems.
While I can't say for sure if non-beta versions work or not, I'd be kinda surprised if they didn't. Maybe someone with v57 final issues tries just opting into the oculus desktop app public beta they can report if this fixes things with Link or not. If not, then they should file a bug report and also lodge a support ticket including their log files so Meta support can identify and fix this. Simply ranting about it without suppling details isn't very useful imho.
@vaizor Since the latest ptc v57 update, including oculus desktop app public beta update (version #’s mentioned in my previous post) all those issues seem fixed with both my Q2 and QPro, standalone and PCVR with Link and Air Link. The pixel sparkle I’d occasionally see, mainly on right eye is gone, hopefully forever, lol!
@vaizor and @TomCgcmfc , Unfortunately vaizer is correct the issue is still there on latest v57 ... and completely constant on various apps that have achieve a certain level of graphical fidelity. It is extremely pronounced with video decoding applications, such as Virtual Desktop and immersive media apps that do 360/180 video playback. When I say constant I mean every 1 to 2 seconds there's is a flashing pixels artifacts across the right side of the screen and sometimes even screen tearing along with it. The result is not acceptable or implementable - it causes too much visual discomfort. This never occurred before v53, and the graphical settings are within the Quest 2 specs.
Users of Virtual Desktop complain daily on their discord about it (both new members seeking answers, and established members) - it has not been fixed even with the latest ptc v57.
In the AVPro forums, a VR media player plugin solution for Unity that almost everyone uses, many have had to abandon the Quest platform and develop for other HMDs. Some are trying to develop a UE alternative themselves, but there is no telling if that approach will still produce artifacts at the same graphic setting. We have been trying to impressive upon Meta engineering ( @Ryanality ) that using one of these Video Decoding application will immediately highlight the issue... its impact is undeniable, consistent and striking even at low graphics.
If Meta have solved it for Link/Airlink specifically then that's truly great for those users, and a step forward, but it should not be treated like it has been solved because it still currently exists (I check everyday) and is impacting both end-users and businesses. There are some video decoding app players like DeoVR that remain completely unaffected, even at extremely high graphics settings, and some of us are trying to work out what those developers have done (seemingly inadvertently by their account) that completely eliminates this issue... even though they are using Unity and the same AVPro plugins, but there are too many variables and its nearly impossible if we don't even know what the root cause maybe other than a GPU/Memory software issue.
I'm posting about the Flashing Pixel artifact problem above here because the official v57 is now out, and the specific PTC v56+v57 thread for the issue has become something of a siloed ghost-town.... becoming a Megathread in itself and now with so many people giving up on waiting for a fix and leaving the thread conversation (after about 12K views and 22 pages of comments). It's been a promient issue since April/May.
@Dave200S Thanks for all that mate. Fortunately I mainly just use my QPro for PCVR with Air Link so I don't see this problem anymore. Also including with Link and Standalone. Hopefully your issues with other apps like Virtual Desktop can get addressed soon. In the past this has normally required Meta and app the app developer to work together, rather than just point fingers, in order to resolve this. I had issues with one of my flight sims X Plane 11 a couple of years ago and both parties managed to get together to resolve this, fairly quickly I might add, and I believe also included some help from one of our own mpv's @kojack
In any case, I hope this gets resolved and doesn't ruin your VR experience in the meantime. Cheers mate.
@TomCgcmfc Hehe, good old X-Plane. They did eventually fix it. Although neither side would listen to me when I found out the exact cause of the problem (X-Plane passing a not allowed value to an Oculus SDK function) so I released a fix for it before them. 🙂
I belong to a group that gathers every night in the meta home before heading to an app. One of us just got v57 and now can join the call with audio only. Most of the rest of us just got v56 very recently and wonder if this is fixable while we wait for our updates. If there's a better place to post this, direct me.
I believe there are some Pro Controller improvements too? Apparently they snap into place much more quickly on initial boot. I'm guessing this is the software Quest 3 will launch on!
With less than 2 weeks to the launch of the Quest 3, I really hope v57 isn't the firmware that is being released with the headset ???!!! like i've stated before most of the release note features are still missing and even features from previous builds are still missing like being able to use just one controller and touch..!! Apart from legs v57 has given me none of the listed features. I bet nobody from meta answers this!!!
Hey @Okuda.IOI, you've probably heard this already, but not all features that are going to be an a release are enabled right away. And sometimes features will roll out slowly, and separately from the software version. It usually takes some time before all features in a release become available to all people. This is done so the team can get signal on if a feature isn't working right before it goes out more broadly.
We're skipping v58, but v59 should be heading toward the PTC folks fairly soon. I'll make a post when that's getting sent out. But as you know, PTC is used to test out core functionality and doesn't always have features turned on that will become available with the full release.
Not all features ??????? Out of the 11 YOU'VE listed I have "ONE" and like I said before features from previous builds are still not present.! That's like going to buy a car with all the mod cons and finding when you get it, it doesn't have any wheels or an engine or doors or seats or steering wheel...!!! and as for rolling them out slowly don't get me started on voice control...!!!?? What build was that again somewhere in the v20's ?????? laying down mode that disappeared with no explanation why a feature that nearly ever youtube review jumped on as what the people have been asking for. Or is it simply if you want these new features you'll just have to buy a quest 3 when it's released...? if so then don't list them as features the Q2 & Pro will have, as in a lot of cases we never get them anyway! Besides I thought the idea of being in the PTC was to test these new features out before release to make sure and get rid of bugs...?? I ask anyone now have you got more of these features than me and more important where are you located.?
I know it's hard being patient when you're eager for new features, I feel that too all the time.
The laying down mode is a great example of a feature that was tested out in a PTC release but didn't make it out the door. It had several bugs and things that weren't working right and it was pulled from the official release while the team is working on it. It will likely return in the future once they've got it ready for prime time. And that one never even made it to an official release notes page, since it never made it out of PTC.
Also, it's good to note that some features can't be brought to certain countries for regulation or other concerns.
It's also possible that you're still using the PTC build which doesn't have the feature you're looking for in this release unlocked. v57 hasn't been pushed out to all headsets yet, and I'm not certain if all of the features have been unlocked in PTC either.
I hope you don't have to wait too long to get the features you're craving!
It's not about being patient or craving for features, when a PTC release drops we aren't told what the new features are ! (It's like an easter egg hunt!) and then 2 to 3 weeks later you post the features that are in the release version and us in the PTC are sitting here thinking what the HELL..???? the real question is if we aren't testing all these new features (and i'm sure most will agree with me we ain't!!!) what's the point in the PTC ? We joined the PTC not only because we like to get the latest updates early, but we also enjoy bug finding and discussing improvements and being part of a community that will make things better, yet all you read on here is people moaning about being left in the dark about issues that have been reported many times (sparkles on the screen etc). If meta isn't careful the community will just go and find something better, it doesn't matter how good a product is, if the support is crap people WILL go elsewhere.!
Thanks for the info @Ryanality , has there been any progress on the long-standing flashing pixel artifact problem that is going to be addressed in this upcoming PTC v59?
I'm hoping the reason you're skipping a release is because the engineers found a fix and want to implement it asap, thanks
Since updating to v57 I have noticed an appreciable pause in folder content displays. For instance using a video player such Skybox, Pigasus, or DeoVR when I open the file browser in the apps there will be a pause up to around 5 or more seconds before contents are displayed. In the case of DeoVR the app will freeze and the touch controllers be come unresponsive. It doesn't matter if these are local files or networked via DLNA or SMB. This pause was not noticable in v56 or earlier.
Oculus App Version 57.0.0.254.153 (57.0.0.254.153)
My headset is updating as well, but this update seems to be taking much longer than any of the previous ones. Ready to call it a night but I usually don't like leaving the headset plugged in overnight. Is the update really taking this long, or is something stalled? Been going probably 2+ hours.
@Recluse205 I also got updates on both Q2 and QPro headsets (plus Pro controller updates) and also for the oculus desktop pc app. I'm still enrolled on PTC V57 and oculus desktop app public beta so I'm not 100% sure that these exactly correspond to non-beta V57 but I think they may. You can check out the version numbers against mine and maybe let me know. Thanks.
Headset update version 57.0.0.261.669
Oculus desktop app 57.0.0.254.153 (looks the same as was reported in the post above)
I didn't find these updates took any longer to download/install than usual (about 5 minutes for Q2 and about 10 minutes for QPro because of the controller updates). I have pretty good 100mbps internet so that probably helps. Sometimes local servers can get a little bogged down.
I tried both headsets with standalone apps and PCVR with Link and Air Link with a few Rift and Steam apps plus my flight sim msfs and everything seemed to work fine. Also, all face, eye, and hand tracking options in standalone seemed work fine.
For Link I used 650mbps bitrate and for Air Link I used 200mbps Fixed. Everything was smooth and stutter-free. I had been using 200mbps Dynamic plus 5mbps offset bitrates prior to this update but now 200mbps Fixed seems to work slightly better (but not a lot in it tbh).
Only minor issue I found was that poor old Toybox from the Rift store still does not display the controllers. They are there but they are invisible, lol! Filed another bug report on this.
So, all's well so far and I hope these updates fix the current issues some were having with Link. Cheers mates.
Edit: A bit more time with all this, mainly with my QPro and Air Link. So far, no pixel sparkles! I used to occasionally see them in the dark SteamVR void, but not anymore.
Edit #2; my Q2 headset battery will still not charge above 97% and will never show the green charge light when connected to its charger. If I connect it to my Elite battery strap when it's below 80% the headset battery never goes above 80%. If I charge separately for a long time, then connect and charge both the green light eventually goes on but when I start it up the headset shows 97% max and elite battery 100%. Still a bit of q mystery, lol!
Thanks for the info!! I checked my headset about 3 hours after my post and it was STILL GOING. I cancelled and reset, and it showed the same version as you, 57.0.0.261.669 and no additional update available, so I guess something got stuck, but the update ran successfully.
I never thought about this before but now I am paranoid about every update breaking SOMETHING 🙂
@AdiePDeva You are probably best to contact Meta support imho. I'm not having any problems connecting with Bluetooth with either my Q2 or QPro and my iPhone 12 mini with the same latest v57.
Edit; you also may want to start a separate thread in the Get Help VVR forum subforum. That way, more will see it imho.
Also, if you search this forum for Bluetooth Problems you may find something relevant like maybe this;
Ok, so now I can no longer pin and unpin apps from the Universal Menu. Why does this feature keep coming and going and the number of apps that can be pinned keep changing?
And why do I get random flashing of parts of the avatar torso and arms flipping around usually when the browser is open or just the home environment and UM
I'm surprised that no one above has mentioned the widely reported v57 bug that has killed 6DOF tracking of the Quest Pro Controllers for Quest 2 users!
To be more precise, what appears to have happened is that the v57 update triggered a Quest Pro Controller update that claims to have started but never actually installs/completes, leaving the Quest Pro Controllers paired but in 3DOF mode, thus only partially operable. For anyone wondering, yes, reboots of the HMD and controllers as well as unpairing and repairing the controllers will not resolve the issue.
One poster on Reddit claimed that Meta was aware of the issue, which I hope is the case, but I've seen no confirmation from Meta about this, yet.
@DrBobtastic Hmmm I wonder if that is the reason my update seemed to go on forever and never completed. Haven't done anything but PC VR since things were working again, so I haven't had occasion to use the controllers much besides point and click to establish my LINK (and I use my hands for MOST of that anyway)
Hey @DrBobtastic Can you let me know what build version you are on? You can find this in your settings. Let me know if you run into any trouble finding it.
@Okuda.IOI I feel exactly the same for PTC. What is the point if we don't know what we are testing. We DON'T know what we are looking for, therefore it takes longer to fix and report what features are broken because we have to find them. Meta could get new builds out faster and more efficiently if they simply just tell us what is new as soon as PTC releases go out to anybody so we know what to inspect.
I hope they consider what we are saying and actually put some thoughts into it.
Hi All - I just posted the following message in another thread, since that where the Meta Support team responded to me about the same issue. I'll repost here, with the hope y'all will experience the same resolution I did this morning...
Thanks for the quick reply! Good news to report regarding my Quest Pro controllers...
Presumably due to another overnight update, when I put on my Quest 2 this morning, I received a notification saying that the update for my Left Controller -which was no longer visible- had failed (which wasn't good, but at least it was something new), and my Right Controller reported that it was currently updating and showed 0%... then changed to 1%... then, very slowly proceeded. After finishing, the Right Controller disappeared completely also. So, I rebooted both Controllers. No Controllers came up. Then I rebooted the headset. This time, the Right Controller showed up and was fully operational! I then rebooted the Left Controller. Nothing. So, I unpaired the Left Controller via the app, then re-paired it. Then I rebooted the Left Controller and the headset again and when it finished, I received a notification saying that the Left Controller was now updating... and proceeded through the same process as the Right Controller had. After it finished, I rebooted the headset one last time, and everything came up correctly, with both Controllers tracking normally! 😁
For reference, both of the Quest Pro Controllers now report Firmware Version 1.28.3 on the +phone's app, which is definitely different than it said yesterday. Within the headset's Software Update tab, it's reporting Software Update/System Version 50623410060800150, Version 57.0.0.261.669.517337457, and Runtime Version 57.0.0.261.669.517337474.
Hi All - I just posted the following message in a separate thread, in which @FunkyTanuki was kind enough to respond to me about the Quest Pro Controller issue. I'll repost here, with the hope y'all experience the same resolution I did this morning...
Thanks for the quick reply! Good news to report regarding my Quest Pro controllers...
Presumably due to another overnight update, when I put on my Quest 2 this morning, I received a notification saying that the update for my Left Controller -which was no longer visible- had failed (which wasn't good, but at least it was something new), and my Right Controller reported that it was currently updating and showed 0%... then changed to 1%... then, very slowly proceeded. After finishing, the Right Controller disappeared completely also. So, I rebooted both Controllers. No Controllers came up. Then I rebooted the headset. This time, the Right Controller showed up and was fully operational! I then rebooted the Left Controller. Nothing. So, I unpaired the Left Controller via the app, then re-paired it. Then I rebooted the Left Controller and the headset again, and when it finished, I received a notification saying that the Left Controller was now updating and proceeded through the same process as the Right Controller had. After it finished, I rebooted the headset one last time, and everything came up correctly, with both Controllers tracking normally! 😁
For reference, both of the Quest Pro Controllers now report Firmware Version 1.28.3 on the phone's app, which is definitely different than it said yesterday. Within the headset's Software Update tab, it's reporting Software Update/System Version 50623410060800150, Version 57.0.0.261.669.517337457, and Runtime Version 57.0.0.261.669.517337474.
I just updated my Quest 2 to v57 and the firmware downloaded/installed successfully but when I restarted the headset I got a black screen. I've tried a hard reboot, checked the sensors, and other suggestions from the online community to no avail. I finally did a hard reset but the problem persisted. I am still able to cast to my phone though so I can at least navigate to Settings if a future update comes along that will fix the problem.
I wrote to support and they just said my device is out of warranty but they offered to sell me a refurbished unit...While I understand my device is out of warranty but it was their firmware/software that bricked it in the first place. Hopefully there's a fix for this.
@cgwu Just a suggestion, but if you can still access the device settings on the phone app, then you could join the PTC channel in Advanced Settings. The when the next PTC update occurs (likely now PTC v59) it will install new firmware sooner. If that still doesn't work you could then leave the PTC in the phone app, and your headset will factory reset and install v57 again fresh.
@Ryanality Is there any changes or updates to DRM protection, Our app heavily use it and suddenly the DRM L3 and L1 start failing. Can you direct me to change logs for this update and if you know any changes added please let me know. Thanks
I usually just put my headset to sleep without a shutdown. Today I shutdown and then restarted it.
And, when it did, I was sooo happy to see the Explore menu that was wider and had the left side navigation and the right side friends list. I was like yes it is back and functional. I went to play an airlink game and returned and the Explore menu was back to it's newer format that doesn't show much content and isn't very functional. I shutdown/restarted again and no luck returning the one I would actually use. Is there a setting I can set to get the wider version with the navigation back in action? For now I am keeping it closed.
Airlink note - more and more often I have to completely close the 3 running oculus tasks and reopen the PC app before the airlink connection/my headset is recognized. I shutdown my computer every night, but do leave my headset in sleep mode. When I turn my laptop on again I have to shut those 3 tasks down or it can't find my headset. It is pretty consistent, in case that helps figure out the issue.
@LuvinLife Up to you but I always fully power down both my Q2 and QPro headsets at the end of playing for the day and putting it on charge. This helps avoid updating I prefer to check for myself the next day.
Same goes with my PC as well. I never put that to sleep or hibernate. I think that fully shutting down helps clear ram memory. A restart can also do this.
@TomCgcmfc I always shut down my computer, but sometimes don't know if I am really done playing with the headset for the night... 😉 I did setup a .bat file that closes all 3 tasks instead of having to open task manager, but didn't have to do so as often before and my (quasi bad) habit hasn't changed since I've had the headset.
Also, thanks for always having productive feedback on here. 🙂
@Recluse205 This Update was a "full release", so on Q2 it lasts very long to download und afterwards it does a full flash, not only an update. Also with the update of the desktop app new windows driver come with it, which schould be installed afterwards... only the TouchController (Q2) itself weren't updated with this release 😉
@NomadsAnIsland Sorry, but I couldn't confirm SMB delay of 5 seconds or more (Q2).
And thank's for the info about the avatar mirror... hopefully the will implement another trigger for deactivating "arms and body" 😉
After updating to v57 the menu switched to "direct touch" and all pinned apps (2 if i remember correctly) are gone. Afterwards it was possible to pin exactly one app to the menu bar. So maybe you need to unpin a system app... only "store" and "explore" are fixed, so a maximum 5 apps (2 fixed, 3 custom) on the menu bar are possible (+3 last opened).
As "@CGWU" stated above. This is exactly what happened to mine but just for the record:
"I just updated my Quest 2 to v57 and the firmware downloaded/installed successfully but when I restarted the headset I got a black screen. I've tried a hard reboot, checked the sensors, and other suggestions from the online community to no avail. I finally did a hard reset but the problem persisted. I am still able to cast to my phone though so I can at least navigate to Settings if a future update comes along that will fix the problem. I wrote to support and they just said my device is out of warranty but they offered to sell me a refurbished unit...While I understand my device is out of warranty but it was their firmware/software that bricked it in the first place. Hopefully there's a fix for this."
@kevinnicholson3d Did you try using your phone app to enroll into the PTC beta program? This seems to have helped some. If that fixes things you can always try getting out of PTC later, which should take you back to the current non-PTC version.
