Honored Contributor

Meta Quest build v53 release notes

65 replies
21035 views

These features and enhancements will become available starting the week of April 27th, 2023 and will be pushed to Meta Quest Pro and Meta Quest 2 headsets.

Parental Supervision content filters for Meta Quest Browser

We are adding the ability to block access to certain website categories in Meta Quest Browser (examples: adult content, alcohol/tobacco, weapons, etc.). Once you’ve turned on Parental Supervision, parents can enable these content filters from the Meta Quest mobile app.

WIFI 6E support for Meta Quest Pro

If you have a Quest Pro, you can now connect to WiFi 6 GHz networks for lower latency and faster, more consistent download and upload speeds.

Advanced camera settings leaving Experimental Features

Advanced camera settings are moving from Experimental Features to the Camera tab under Settings. You can use these advanced settings to capture VR gameplay videos at different frame rates, aspect ratios, bit rates, and with image stabilization.

Stereo audio for video recording

We are beginning to roll out stereo audio for video recording. All video captures will record stereo audio instead of monophonic audio.

Update apps during shutdown

When you shutdown your headset, you will now have the option to update apps before the headset powers off. This will help minimize the number of app updates that you have to complete the next time you want to jump into a VR app or game.

This will be rolling out gradually.

Text readout on system keyboard

A readout will show up when you are using the system keyboard. This will allow you to quickly glance at what you’re typing in VR and make easy edits and should reduce eye and neck strain.

Select time zone and edit time

You will now be able to select the time zone on your headset and manually edit the displayed time. To do this, select the date at the top of the Quick Settings panel.

VR notification grouping

Multiple notifications from a specific app will now be grouped together, allowing you to more efficiently interact with them.

Twitch.tv on Meta Quest Browser

You can now log in to Twitch.tv from Meta Quest Browser. Access content, chat with friends, and watch and subscribe to your favorite Twitch streamers in VR.

release notes

S

Stugabaranda

Up and Coming

hello Ryanality and thanks for the announcement!
net of the important improvements of which I pleasantly note,in megathread v53 ptc I reported the following problems on my Quest 2, for which unfortunately I have not received any feedback:
- sofa and desk that were no longer seen in my house,
- gray armrests are back also in direct touch mode (instead of transparent hands) -
completely disappeared mixed reality menu in guardian panel
- couch mode switch and desk mode switch disappeared.
when i got the official v51 all these problems are gone.
can you please update me on the real situation of v53?
honestly i have blocked updates but only because im worried about loosing the stability and peace i found by exiting ptc and getting the official v51 and i hope the above was just a temporary issue while testing v53 and not a radical change of the system decided by Meta, such as the one concerning the disappearance of the link to the home from the Oculus Link dashboard which took place without any notice to users and has still remained without official clarifications.

Meta Quest 2 256GB, GC Nvidia GeForce RTX 3060, Intel 12th Gen Intel i5-12400F, 16Gb RAM, Windows 11 home 22H2. Connected with dedicated router via ethernet cat 6 with pc and to Quest 2 on wifi 5 ch 36

RyanalityAuthor

Honored Contributor

Hi! I'm working on getting some more details for you around what mixed reality changes were included in v53. I'll follow up with you in our PM conversation when I've gotten any news I can share.

Help others find great discussions and answers by adding kudos and marking solutions to your questions.

I

ImXL

Up and Coming

I am having the same issue. Couch disappeared after V53, along with the Mixed Reality setting altogether.

D

dojjah

Participant

Hello Ryanality,

I'm on v53 and my Quest Pro will not connect to my 6GHz network. My device is enrolled in PTC, should I expect another update which may resolve this issue before v53 is deployed to production (disabling PTC currently gives a downgrade option to v51) or should I reach out to Meta store support regarding the problem?

I have worked with my router's support team to determine the 6GHz network is functioning properly, they have suggested there's an issue with my device, but it's unclear to me where we're at with this PTC cycle and if the current build I'm running will be the same as a final release. Any clarity would be greatly appreciated, thank you!

RyanalityAuthor

Honored Contributor

Hey dojjah! I've been chatting with the engineering team and they would like to get some logs from the Quest Pro to see if there's a band steering issue or something else causing this behavior. I'm going to have the CS team reach out to you here in PM first to create a ticket so that a technician can follow up via email.

Help others find great discussions and answers by adding kudos and marking solutions to your questions.

D

dojjah

Participant

Hi Ryanality ,

As an update to this, the Meta support person who is currently working on my ticket has just suggested that I'll have a better experience trying to use a USB-C cable with my PC in regard to my Wifi 6e issue...

I hope you can understand that saying I'm frustrated with this is an extreme understatement. I agree with your thoughts this is a band steering issue - I'd really like to help you and the dev team solve this problem as currently your Wifi 6e implementation is broke, but support is telling me not to use it instead.

The release notes of v53 clearly state Quest Pro now supports Wifi 6e, is it a non-standard implementation? Do I have a defective Quest Pro which can't connect to 6GHz networks? Is support implying that the Quest Pro only works with certain Wifi 6e routers? Which routers if that's the case? Clarity would be appreciated, from myself and others. Thank you.

B

Buetigame

Participant

No pinned release threads anymore?
Wrote this on 26th April:

I've found the (reitail!) firmware 51.0.0.182 on my headset (Q2) today...
(along with desktop app 51.0.0.168.269 by the way)
What's up with it?

No words on v51, updated my device and desktop app just one day before next release?
Sorry, but that's not understandable anymore.

Anyway, there are other things aroud the release of v53 mentioned:
* neues Dashboard Design
* contrast slider (also for Quest 2!)
* "lay down" mode - perfect for movies!
* display brightness compensation (Quest pro)
* native eye-tracking for VR-Chat (Quest pro)

Nothing ist metioned here...

D

Dosker

New Participant

The native eye-tracking of VR-Chat is a update of VRChat, not from this update.

And Eye-Tracking was already working before v53 PTC, any app or game can make updates to suport it.

Moriarti4

Up and Coming

I'm on the PTC for v53 and as far as anyone there is concerned it's far from ready for release so what gives with this thread ? People have reported lots of bugs and glitch's since the second V53 was pushed out in the PTC and yet we haven't received another update since ? Have these bugs been fixed ? When will we get another update ? Does anyone connected to meta bother to read these threads anymore ?

D

dojjah

Participant

I just got another v53 update today by disabling PTC in the mobile app and checking for update in headset, which I believe to be the "final" release version. Be careful though, if you disable PTC in the PC app it will downgrade to v51 which does not work with v53 in headset - learned that the hard way.

All of that said, my issues still persist - it will not connect to my 6e 6GHz network and some apps/games have terrible performance, RE4VR is unplayable running very choppy/low frame rate. I am working with Meta support on the 6e issue.

B

Buetigame

Participant

My Quest2 updated to v53, Desktop-App stays at v51 and everything works like it should.
Both release channel, no PTC. So I don't know, what you are taking about?

Got no issues, but also no features except of the new menu design.
I really would change the time, which is 2h off... since release of the Q2.
(a matter of a wrong timezone which is fixed to UTC obviously)

But where are the features of the v53, as I've mentioned before:
* contrast slider (also for Quest 2!)
* "lay down" mode - perfect for movies!

Very stange...

T

tanubon

Inspiring

Version number of official v53? I'm on PTC now, does it update automatically to official v53 version?

CookiesNScream

Honored Contributor

I found an article about PTC and updates, if you wanna check it out here. Basically, if you're on PTC you'll be ahead of or equivalent to public release.

Through the darkness of futures past, the magician longs to see. One chants out between two worlds: Fire... walk with me

O

ohdubya

Up and Coming

So frustrating. V53 is causing issues with proximity sensor on my Quest Pro. I have to physically cover it, or disable it via ODH.

Issues first started with V53 PTC, but went back to normal with V51 Public, which caused a factory reset. Then I got V53 Public got pushed onto my HMD and proximity sensor is acting up again. I re-enrolled in PTC to see if there'd be an improvement, but it wiped my headset again and the proximity sensor issues continue.

Controller tracking also seems inconsistent and often appear offset through multiple sleep/wakes. My lighting has been consistent since buying QP at launch. Sooo frustrating.

RyanalityAuthor

Honored Contributor

Hey ohdubya, there's a fix for a proximity sensor issue rolling out now for v53 users now. It's slowly rolling out, so just make sure your headset is powered up and on the charger and it should get the update automatically when it's deployed to your Quest Pro.

Help others find great discussions and answers by adding kudos and marking solutions to your questions.

R

RinkZea

Participant

Some Quest Pro users (including me) have been experiencing issus with the controllers not being able to connect to the headset at all since v51 PTC, which still isn't fixed in v53 Release.

I am pretty sure it is not a hardware problem because: 1. I have tried to pair these controllers with my Quest 2 and everything is working perfectly after several sleeps/reboots. 2. Ppl who have replace their device with a brand new one through RMA still experiencing the same problem.

Hope Meta could locate the problem and fix it asap while I am currently not living in a country where I can get RMA.

you can find them in these threads:

https://communityforums.atmeta.com/t5/Announcements/PTC-v53-Release-Megathread/m-p/1047315/highlight/true#M4181

https://communityforums.atmeta.com/t5/Announcements/PTC-v53-Release-Megathread/m-p/1044478/highlight/true#M4011

https://www.reddit.com/r/oculus/comments/126nddy/v51_update_broke_quest_pro_controllers/

https://www.reddit.com/r/QuestPro/comments/12pw45s/quest_pro_v51_controllers_will_not_communicate/

J

jdawg461976

Participant

Anyone that is posting anything about that they got a version update but is not posting the version they have. Stop it. Like how hard is it to check?

T

TheodonKhel

Up and Coming

After v53 got released officially my controllers went haywire. They freeze often for 2,3 seconds making any game unplayable. Happens in standalone apps, Air Link and VD. Guardian clearing, pairing controllers again, factory resets didnt solve this issue. Nothing in my environment has changed (light, WiFi, PC software etc)

J

jdawg461976

Participant

Finally got the v54 update. Will keep an eye out for release notes. Not sure what has changed just yet.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO