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

The Public Test Channel (PTC) for Quest v55 is starting to roll out for Meta Quest Pro and Meta Quest 2 soon. 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!  

Let's use this thread for collecting feedback on v55. 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!

282 Comments
NorbertNoBacon
Protege

I was referring to those reporting the charging issue (which happened around the time of the Android 12 update), not the entire userbase. @jdawg46.1976 reported a similar issue with a 2 month old headset in this thread.

jdawg46.1976
Protege

These posts seem strange. I have been on the version you guys are referencing since last week. Maybe Tuesday of last week. Would that be normal that I got mine that much sooner? I have seen a lot less issues just wondering the timing. 

FinlessBob
Expert Protege

"I still get a ghost image upon startup looking at the mirror and I get an outline around my controllers (both headsets).  These seem to fix up by themselves and stabilize after about 10-15 seconds."

 

I see this too but I think it is a feature as the passthrough is on and 'fades" out to the menu each time waking from sleep.  At least I thought it was some kind of feature.

erickrlima
Explorer

I got the new build, but i dont know what changed. Flashing Pixels still a problem running native, Airlink and VD.

I started to get the battery percentage bug as well. It charges up to 97% and stops. The led won`t turn green. 

But if i remove the cable and reconect again, it goes to 100% and the led turn green. This still a problem with the latest build on my unit.

 

Do they usually post any changelogs of these beta builds?

jdawg46.1976
Protege

they post release notes a little closer to release. it would be nice if they posted them at initial release so we knew what to look for, what to test, what its supposed to fix but we should see release notes probably closer to the end of the month.

Ryanality
Retired Support

Hey everyone, thanks for sharing and helping us test out this PTC! There are some reports that are still being worked on, but the v55 release is going to start rolling out to more people and out of PTC soon. It'll roll out slowly so that we can gather more feedback from folks regarding any potential issue that's still ongoing. I've published the release notes here. There will be some more fixes coming to v55 and others that might be moved into v56, so please do keep on reporting bugs and let us know what you're seeing! The community team will make sure it gets to engineering for you.

FinlessBob
Expert Protege

Good to hear.  For me, other than the band of white pixels that appear from time to time, I am pretty happy with this release.  The other stuff is annoying but hasn't effected my game and App experiences.

 

i0ntempest
Honored Guest

I opted into v55 ptc 2 hours too early… it seems to be public now but to opt out I have to reset my device. Is there a way to opt out without resetting?

jdawg46.1976
Protege

unfortunately no. but i have done it so many times at this point, it seems a natural event. i may opt out just to do a factory reset and get a fresh public release of v55.

oursoul
Protege

Just a quick note to the devs that all the images & thumbnails in the Explore window seem to have lost their connection to the colour space and look flat and crappy.

tanubon
Heroic Explorer
BisonTruffle
Explorer

Swapped Quest Pro controllers out using Quest 2 and it improved lag on WiFi. Still having some lag and now tracking issues, it starts to pull the guardian up and down or slowly move it away and caused me to hit a wall literally. 

Ryanality
Retired Support

Hi everyone, thanks for sharing all your feedback! The engineering team has been hard at work tracking down issues causing lag and stuttering with Air Link. There's a fix rolling out to systems on v54 and v55 now which should make some major improvements for anyone running into the issues they've been working on. If you've been having trouble with Air Link stuttering or lag, please reboot your headset to make sure that update hits and installs. 

The fix is in build 5004863.3140.330 for PTC v55.

FinlessBob
Expert Protege

Hi Ryanality, how about a fix for the random white pixel bands?  I am sure this is a rendering GPU issues and I can explain why I think that.  It only happens in new scenes that are being rendered.  Once the scene has been full rendered in all angles, it stops.  So for me this is the largest annoyance with V54 / 55..

Ryanality
Retired Support

That's in the works too! I'll be sure to update everyone when the team has a solution for that one.

FinlessBob
Expert Protege

THANKS!  While it is just an annoyance and does not really effect my fun.  I am glad to hear that is in the works 🙂


Dave200S
Expert Protege

Thanks also, a fix for the random white pixel bands is crucial for our immersive VR180 video app (built in Unity) -  where visual quality and consistency is essential for an enjoyable experience.

Cassbunny
Honored Guest

I am on build 5004863.3140.330 and i am still having massive airlink issues.
My screen had weird black edges and wobblyness, and terrible lag that made it impossible to move my controllers or click anything.

And now the view is even flashing in and out with blackscreens spamming my eyes. Its quite impossible to use.
I havent had these issues until v54 + v55 and personally i wish i could go back to v53 and below.

my entire quest pro is unusable and im kinda sad about it at this point.
It's hard to describe the issues im having other than... screen tearing kinda. flashing black screen. Wobbly images. massive lag. Cant move controllers or select any button. Its just completely unusable.

M0RIATY
Adventurer

Since the update a couple of days ago (Quest Pro) has anyone else noticed a sort of lag when opening or closing a window in the home environment for about 5 minutes after booting up ? then it slowly fades away and seems almost normal with a few little jitters ? The lag I mean is sort of the whole screen follows the animation of the window closing direction it makes you few dizzy seeing it. ?

jdawg46.1976
Protege

i also dont see any improvement on airlink. i am on the "fixed" build as well, but my issue seems related to wifi but its not my router, i am within 7 feet from my router. my wifi 6(5ghz) is not as bad, but wifi 6e, which i have mac filtered to only my quest pro device will often jump me off and give me a message that my access point is temporarily full - even though i have one device on it. been happening since the "support" of wifi 6e. but i get the black jagged edge and get kicked out of airlink just like the post above and this new "fix" does not seem to do anything. how are you guys testing this? on devices that are not having an issue, and then think - "we fixed it" its not fixed. 

Edit:wanted to post an update so i am not misleading. I noticed my runtime was not set to Oculus. it got changed to steamVR - not sure how, but it may have happen when the app updated. I set it back to Oculus and have not had an issue but only tried a couple of game sessions. 

FinlessBob
Expert Protege

Yes I am seeing that as well.  It's annoying but I do not sit in the home environment and do a bunch of that but yea, its there.

Ryanality
Retired Support

Thanks for sharing @FinlessBob, and @M0RIATY! I've reported that up to the team to look into.

 

@jdawg46.1976 What router are you working with over there? Any other details on what you're seeing that you might be able to share? I'll get it over to the team to look into. We've been looking into some WiFi 6 related things and I wonder if you might be experiencing that. Those issues could cause similar trouble to what you're describing and not be related to the fixes for Air Link connections which just went live.

Unstable Air Link is more of a symptom, much like a runny nose or headache. There's always an underlying issue that's causing the problem which usually isn't obvious. Because of that, there isn't one fix that can solve it always, all the time.

jdawg46.1976
Protege

i have an Asus GT-AXE16000, and honestly after setting my runtime correctly in the Oculus app i have not seen anymore issues. my wifi was pretty spotty when v53 hit, had to stay on my 5ghz band, but today after correcting my oculus runtime, airlink has been wonderful. Not getting kicked off my 6e wifi either. im typing this message via Horizon workrooms and its been wonderful. going to keep my fingers crossed my issues are gone. Thanks for checking in. 

Ryanality
Retired Support

Great to hear! I believe the Asus AXE11000 is one of the routers the team has on the naughty list, but they're working on some fixes right now. I'm not sure if it the 16000 is also afflicted similarly. In any case, thanks for testing and let us know if you see anything else!

FinlessBob
Expert Protege

Not using Wifi 6.  Router is a Netgear R6260.  
Okuda is talking about the built in home environment not airlink home (I believe).  When you first boot up and for a few minutes after, opening any window in the home environment there is a little "jump" left or right and that jump also causes the entire environment to jump as well.  After a few times of this it stops.  Kind of like something is running in the background causing some lag or something.

As for Airlink, I have not been using it.  I use Virtual Desktop and have no issues.  But I certainly can try Airlink which I will do today.

Ryanality
Retired Support

Sorry, my messages got crossed. I've reported the issue you and Okuda mentioned over to the team, they're looking into it but it likely isn't due to the routers at all.

That was just the trouble jdawg mentioned which might have been router related.

Web4aintgay
Honored Guest

What's with the Code: -6100 -- ovrError_XRStreamingGeneralIssue error when using pcvr via link? The error appears in the OVRServer console when the visual suddenly gets wobbly and laggy, then most annoyingly the entire image wraps around my view every time I turn my head around causing black edges to be seen, sight increased latency of the controllers is also present when moving them around during the error spike. This lag spike only happens in some specific areas of a game, and resolves when I move to another location despite having a consistent framerate of 90FPS+ wherever I am; Is using bitrate higher than 500 still broken? FYI I'm running it off a 4090/13900K machine with bitrate set to 850Mbps. This was not an issue months ago when I was still rocking a 3070/10700 combo.

FinlessBob
Expert Protege

What is the final version numbers for V55 release?
So I know if I am on it or still on PTC?

Thanks!

Cassbunny
Honored Guest

Okay im basically getting @Web4aintgay 's exact same issue only while airlinked via oculus, virtual desktop, or cable. Cable less so, but still there.

I turn my head, black edges seen. Latency of controllers impossible during lag spike. Visual always wobbly and laggy.

HOWEVER mines start right off the bat, immediately after connecting to link. I don't even get a chance to hop into a game or anything. If i ignore this, and use my pc to start up an app, it goes through. But even that app is still getting these issues.

I want to say it could be a wifi/router problem. Cause my setup is a little... unconventional.
However my setup was working fine up until the recent updates and i dont know what else it could be.

My setup is kinda; Router > Wifi Extender w/ Ethernet Cable > Ethernet plugged into my pc.
Quest pro connected to routers wifi > Quest pro sees my computer via airlink, gives me the total green light since, my connection is stable (which it is? and its worked for months until now).

I'd rather not buy a whole router or VR headset if i can help it to be honest.

jdawg46.1976
Protege

@Ryanality 

wanted to mention something. my experience has been greatly improved since the last update but not without issues. what happens about once every 6-10 hours is I will get kicked off my wifi 6e network with a message on the headset that says "access point temporarily full" even though I have only one device connected on this beefy wifi router - my quest pro. I have it locked by mac address so only my quest pro can get on, but i get that message. it does only last a moment but if i am in a game session i get kicked off airlink, then i will see the wifi not be connected with the message. I am not sure if the AXE11000 issue you mention is similar but I have spoken with others and they also get that same message. Its not my router, but may be the headset talking to something on the router. 

Last thing to note, prior to the recent updates the 6-10 hour thing used to happen about every 2 hours, so i can say the situation is improved but not fully gone. 

TomCgcmfc
MVP
MVP

@jdawg46.1976  Maybe try switching your router settings from 160mHz to 80mHz.  I understand that 160 ends up taking 2x80 channels, without any benefit but may be causing this interference issue.  This has recently been brought up in the VD discord.

jdawg46.1976
Protege

@TomCgcmfc 

ok i may try that. whatever the last patches were they have greatly improved things, today i have had 0 drops. if i get any drops though i will switch to 80mHz. Thank you for mentioning. i just also read something on reddit forums about doing the same thing so will do that if i experience the issue again. 

LuvinLife
Protege

v55 notes - added to main v55 release notes as well, in case this page is no longer being monitored.

Explore Menu feedback:

->Please put the Explore menu/window that was wider/showed more content and had really nice left navigation options to hop to different sections back. The new one requires a lot of scrolling to see content, which doesn’t make us want to ‘explore’. It is something I would expect on a small phone, not a 360-degree headset.

Reproducible oddities:

->When I am using airlink and have a battery pack plugged in, the charge level reads 100%. When I return to the main Q2 menu and unplug the battery pack it instantly changes to the more accurate %.

->When I side load a file and then put the headset on, the Home environment shows the default skybox instead of the personalized skybox. The personalized picture still shows as being present when I check on it in the options section. Then when I go into a game and then return to the Home environment, the personalized skybox is back.

Several times/week oddity:

->I wake the headset (it hasn't been shut down) and can see the blue grid of my boundary, but the rest is black. I can step out of the grid and the passthrough appears. When I step back into the boundary, the same blue grid/black everything else is still present. I have to restart/shutdown before I can use the headset.

jdawg46.1976
Protege

@TomCgcmfc 

so even changing to 80mHz does not stop the drop, its pretty much every 10 hours. My headset I leave on pretty much all the time, it sits in the charge cradle. when i pick it up, I see a notification that my wifi lost connection 10 hours ago, sometimes its 1 hour depending on when i pick it up but it reconnects like everything is fine. but the drop does not make sense to me. 

erickrlima
Explorer

That 100% bug when using airlink, it happens in v54 as well. I've opted out of PTC channel and got downgraded to v54. This bug is consistently reproducible. 100% of the time.

AsbestosMcFlave
Honored Guest

Hi there, I am on PTC v55 and have some feedback to share.

  1. Quest Move now works once again - for me, this was broken completely in v54 PTC and it wouldn't count time or calories. Thank you!
  2. PTC v53 supposedly brought out Lying Down mode for some folks. At the time that v53 was available, I had not been in PTC yet and was instead in the live channel v53 and did not receive this. Since then, people who have updated it no longer have the option. I too still do not have this option despite now being in PTC and being 2 firmware versions newer than v53. Please bring this back.
  3. Performance on Airlink appears better than v54 - seems WiFi issues may have been somewhat resolved.
  4. Home menu is still difficult to work with compared to the Oculus software. It is frustrating to not be able to move the home menu anywhere on screen that you'd like, it's frustrating that you can't re-size windows using analog sticks or pinch-grabbing corners, and it's frustrating that you can't scale and move the keyboard independently of the menu window.
FinlessBob
Expert Protege

So wait... I am still on PTC.  You would THINK that as PTC participants, we would get the final V55 before most others.  I got a friend that got V55 yet I am still here waiting on PTC.

What motivation should we as PTC people get if we do not get V55 first....

Please resolve that. 🙂

Stugabaranda
Adventurer

with v55 Meta decided to eliminate playing background music? 
I recently realized that the switch is missing from experimental functions.

pete.lurie
Explorer

Firstly, I would like to take a moment to express my admiration for the work that you do. The recent opportunity to test out V.55 through the Public Test Channel was too tempting to resist, and I am more than glad that I made the leap. The wait for the roll-out may have been long, but the experience thus far has affirmed that good things indeed come to those who wait.

I have been using the Link cable and the enhancement in quality and performance has been phenomenal. The transition to V.55 via the PTC on the headset has brought a significant improvement, even without the need to download the PC app for Oculus. I am intrigued about what changes made this remarkable upgrade possible and would be grateful for any insights you can provide.

My primary use for the Link cable is with MSFS (Microsoft Flight Simulator), which has been utterly transformed by this update. The game now runs more smoothly and rapidly, significantly enriching my gaming experience. However, I am somewhat puzzled about resolution settings - should I always follow the recommended options provided by the headset, or is there scope to push the boundaries and go higher?

Also, I've been noticing an intermittent issue where a dot representing mouse movements appears within the headset, sometimes unresponsive to my in-game commands. I am unsure whether this is an issue with the program or the headset itself and would appreciate any advice you can offer.

Finally, as a PTC participant, I am curious about potential future updates. If another update is released on the PTC soon, will I be at a disadvantage? Furthermore, is there a way to stabilise my version at V.55 without the need to stay on the PTC?

I am eagerly awaiting your response to better understand these queries. In the meantime, please accept my sincere thanks for your excellent work and the fantastic strides you continue to make in this field.

SciborgNinja
Protege

PC Streaming DID NOT get fixed with this update for Quest 2. I have a $400 paperweight. I returned my Quest Pro Controllers. Not buying a Quest 3. I can't believe you guys broke your own product. What a joke.

MusicForL1fe1
Explorer

I have been having lag and stuttering since v55 even though it is faster now  there seems to be more glitching and for pcvr I have white lines that will pop up and screen glitching through official link cable , also have wifi 6,never had a problem before and I tried factory reset on my quest pro and some things were better while it made others worse  also will get complete freeze ups   

 

QKRTHNU
Honored Guest

V55 has introduced significant performance issues when playing Beat Saber (regular store version). On nearly every song I've played it will stutter and drop frames a few times per song. I've never had that happen in the previous 100+hours of play.

erickrlima
Explorer

I got this problem in every single one of the v55 PTC builds. And that's a big reason i opted out. I play Beat Saber on a daily basis and was really unplayable for me. Freezes, crashes, stutterings, frame drops. Sometimes the songs wouldn`t start at all and a infinite black screen appeared. I rolled back to v54 and these never happened again. For now, i disabled auto updates and i'll wait for v56. Even with the network lag problems in v54, at least i can play beatsaber without a hitch and use Oculus Link properly. 

igenvector
Explorer

Yes, I did the same. Mainly issues with performance started with v51 and up to v55 it only getting worse. I hope all this will be fixed somehow in v56.

TomCgcmfc
MVP
MVP

OK, I got a new v55ptc update earlier today (firmware and controller updates) on my Quest Pro/rtx4090 (I'll try my kinda retired Q2 later today).  The new version went from 55.0.0.111.713,xxxxx to 55.0.0.130.713.xxxx.

After clearing  and resetting my Guardian (I just use stationary) and doing a restart, all seems to work fine.  Tested with a few Quest standalone and PCVR/Air Link with Rift, SteamVR, and VivePort apps, plus msfs (flight sim).

Pro controller finger actions seemed a little faster, but maybe placebo.  In any case, they worked very well.

Everything is working well so far.  Thanks Meta and cheers.

Edit/Aside; Not that it probably matters but what I always do with Quest updates, going back since my Q1 days, is to leave my headset on while updating. I don't leave it in sleep mode overnight like some do for updating, I always power down after use and manually check my Quest quick settings/settings/system/software updates to see if any are available.

I then leave it on during the restart and wait for both controllers to update/reboot. When it restarts if you shift your gaze up/down a little you can see the controller update progress. After all that, once my controllers are recognized again (sometimes need to push a few buttons) I clear my guardian history, and set it up again (I only use stationary), then do a restart.

Again, I'm not sure if all that's necessary but it seems to work well for me and I think it may help avoid getting corrupt updates. Anyway, just my $0.02 worth. Cheers.

nalex66
MVP
MVP

Huh, was just checking, and I have 55.0.0.130.713. Pretty sure I had 55.0.0.111.713 before, so seems I got a new (but different) update.

I'm trying to figure out if the GPU clock boost is in effect yet, but I don't know if I'm experiencing placebo effect. Walkabout Mini Golf feels like it could be using the new dynamic resolution upscaling, but again, not sure if I'm fooling myself looking for it. (Also, I've been going back and forth between Quest 1 and Quest 2 setting up private matches, so the difference between the two headsets might be making the Q2 feel extra sharp to me right now.)

TomCgcmfc
MVP
MVP

@nalex66 wrote:

Huh, was just checking, and I have 55.0.0.130.713. Pretty sure I had 55.0.0.111.713 before, so seems I got a new (but different) update.

Typo on my part, sorry about that mate, lol!  new one is same as you 55.0.0.130.713 (corrected that now).

ikarus1111a
Explorer

 I am also on this version and can confirm the new clock rates aren't in force. yet.
 You can check it with OVR and QGO using Insane preset on GPU or CPU.

 As for the DRS I haven't searched actively for performance improvements, resolution or quality to comment on it.

barabba9174
Protege

I’m going mad.

My Quest Pro doesn’t connect to Oculus pc app via AirLink anymore. Tried on v55 111 and v55 130.

It founds the PC, but it never triggers the passcode to pair.

I have never had this problem before. Any suggestion?

AS1C
Protege

I got the new update 55.0.0.130.713. What I want to say is that the problem with graphical artifacts or white sparkles or pixel glitches is still there, but it has become less noticeable. Today after work I will try to reset to factory defaults. I'll let you know if anything has changed.