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!
I would love to hear how you're using your Quest Pro for productivity with a keyboard! (off topic I know, do we have DM's on here?)
I do work in Workrooms every day, but it seems like "mouse + keyboard" support in the headset itself is useless. Maybe if I 100% worked in Google Docs it might be good? But as an engineer, I bought a logitech keyboard and I tried to use it and the "windows" key is mapped to "Oculus button" and that alone ruins me as I can't do any key commands that use the windows key when connected to an app...
I tried: Immersed (too messy) Workrooms (pretty great now, but since I'm connected to my computer I just use THAT keyboard which unfortunately isn't rendered in VR) Virtual Desktop (windows key opens oculus menu which I mentioned above) Remote Desktop (works great an I love being in Oculus OS but again, I'm using my PC's keyboard here)
So I honestly can't wrap my head around WHO is using mouse/keyboard and WHY (unless Meta is just keeping software from me). Inspire me?
To Meta Team, I have tested V54 via Airlink followed by Air Bridge. Both presented similar tearing/lag issue. No improvement. While inspection of performance metric via HUD I can see bitrate stuck at 10. Changing settings in debug tool or in AirLink app made no difference.
Ok so I have managed to fix the flashing pixels on my Quest 2 unit and our own Unity built Immersive Media Player. I can only guess at the reason for the issue and I hope the fix works also works for others, and gives some insight for Meta Engineers. I have restarted my unit about a dozen times now and the fix seems to have stuck.
First I left the PTC V55 and returned to V54. Doing this factory reset my Quest, and I reinstalled my essential apps, including the OVR Metric Tool overlay I previously downloaded from over a year ago. When I retested our app the flashing pixels remained. However I noticed that the OVR Metrics Tool Overlay graph remained on even after a restart... therefore a restart was not affecting this app overlay. I remembered a problem a few years ago where the Metric tool overlay used to cause rendering artifacts on our VR video playback if it was on while the video played - simply turning it of fixed it back then. I decided to update to the OVR Metrics Tool to the Latest (1.6.5 - May 2023). After doing this the flashing pixels on our video app has stopped.
I don't know if this will work for games or VD/ Link, as some people may not even have the OVR Metrics Overlay installed... but if you have an old version installed on your device I recommend uninstalling it and updating to the new one (and restarting). The logic I'm putting on it is that an older version of the Overlay tool is interfering with the rendering, and even if you disable the overly it will continue to interfere (as it is proven to be still running in the background - as the overlay graph remains ON if you restart with it still ON).
I hope this can help some of you get rid of the flashing pixel problem at least.
I just tried this method and really hoped it would help. But no miracle happened, the artifacts on V54 are even more noticeable than on V55 PTC. So I will continue to wait for the update. I hope that the problem with Flashing pixels/white sparkles will be fixed as soon as possible.
It's a pain but this is what works for me. In the Oculus phone app do a factory restore. You will have to wait for file to download again, as well as go through the setup process. But for me this removes the issues until you power down the unit. Oddly enough when I power down the headset it doesn't all come at once. Eventually white pixels comes first followed by airlink cutouts. I also notice hitching in the mobile environment. Anyways it's a pain but i am playing again smoothly. I have to do it every time. About a 10 minutes process. For me though I play for hours straight so i put up with it.
This is some kind of torture. I have a hidden SSID. For me, the biggest pain is entering the password and SSID of the Wi-Fi network. Why couldn't it have been implemented as follows: you connect the helmet to the Meta Quest app on your iPhone, and it sends or offers to send the data of the Wi-Fi network?
You were correct, it works until a restart or power down. Oddly enough it doesn't all come back at once for me. First i notice white pixel in the right lense. then eventually airlink cutouts. Did a factory restore with headset again and it didn't resolve the issue this time. I decided to factory restore with Oculus app on phone. It made it smooth again. I'm sure I'll have to do it again, but that makes the process somewhat easier. Also to add if I notice hitching during the Gaurdian setup, I know something is wrong. Also to add, when i notice the hitching, turning off the phone's Bluetooth takes care of the hitching, but not the white pixels. We put a man on the moon, we can figure this out lol.
Just as an update to the procedure I took to have a lasting fix with the flashing pixels on my Quest 2 unit - I can continue to restart my Quest 2 and playback the immersive video on our Unity based app after returning v54 with no flashing pixels. I am sorry if this has not worked the same for others in other apps.
However I have discovered that if, at any point, I set the Quest to sleep with the single press of the power button... then if I wake the headset and the VR video starts playing again, then the flashing pixels return. Therefore it is unlikely to be related to the old OVR metrics tool as originally guessed, and for me at least is entirely related to if the headset goes to sleep while the I'm in the app (*edit: also the main menu). Only a reboot then fixes it for me (quitting and restarting the app doesn't work). So for me the key element is if I allow the Headset to sleep at any point in the running app or in the menu... then the flashing pixels return if this occurs and I have to restart. I've tested this about a dozen times and it always rings true.
This might explain why some people say the reset/restart fixes works for a time but then returns later for some unknown reason.
Again I hope this helps Meta engineers have some more insight into the problem... and if this is also true for others then is probably a fairly easy fix - if its something to do with the sleep and wake function.
The huge performance when looking at the mirror persists. If you get too close to it, the fps goes down by half. And no matter how far you are from the mirror, everytime you look in it's direction, the frames starts to drop on every environment that have a mirror.
The flashing pixels problem persists. It doesn't show up in screen recordings for some reason, but i will record externally to show the difference between the native recording and external. The issue seems to get worse when you open the oculus menu over an application. So maybe it's something to do with spacewarp? When the fps is low, it starts to trigger and some airtifacts shows up, idk.
Flashing pixels shows up mostly in dark backgrounds, but not exclusively.
Network latency spikes didn't return, airlink and vd runs as usual for me.
I just got a new PC and Q2 build tonight. I noticed that there is a 'Time' category in the Settings\System menu and not sure if Power got added as well. I am used to seeing the System Update category and now have to scroll to see it.
I'm still trying to understand why someone changed the Explore window to be half the size. Now 2 squares/options appear on the left side and when I hover over a friend's name their name disappears so that the chat/call functions can be shown - not the name connected to them.
I think a reasonable size (if not given the option to resize them) for a window would be the same size as the current Store one or how the Explore window used to be prior to this release.
This is a question for any user that can code even a little bit (I can't) how long would it take you to change the default icon attached to a piece of software ? I think you can see where i'm going with this !?! November 2021 Oculus was rebranded as Meta and still Oculus is plastered everywhere ! Now I know a lot of people preferred the Oculus branding (me too) but for new people (non tech savvy) are going to get into VR then do it under one banner otherwise they just get confused ! I had to explain to a friend that Oculus and Meta are the same and when asked why not under the same name all I could say is LAZY I guess! So please Dev's sort out the naming on the next build we want more people to buy into VR as this encourages investment and development.
Annoyingly, PTC v54 wifi worked perfectly for me. Then the public v54 broke wifi, and v55 ptc made anything reliant on wifi unuseable unless I set airlink to 10 mbps.
I'm experiencing really bad passthrough performance with v55. The cameras fall out of sync quickly and easily and it can't quite seem to stitch the scene together properly resulting in a warped image and "drunk" feel. Within minutes of turning it on even only for a background using the web browser I begin to get motion sickness - which hasn't happened to me in VR in a very long time. If I switch to a VR home instead of passthrough, I don't get the same feeling.
That's the problem i was talking about. These flashing pixels doesn't show in a native recording, only on the display. This is the place where i get the worse experience. The app is Walkabout Minigolf in Zerzura map.
Same issue here, I posted here and on Twitter with no acknowledgement from anyone at Meta. A number of people have confirmed they have the same issue on my Twitter thread.
55.0.0.94.713.484388084 Runtime 55.0.0.94.713.484387702 OS SQ3A.220605.009.A1
Oculus PC also received PTC update to 55.0.0.91.272 (55.0.0.91.272)
My Quest 2 hasn't received any changes in terms of graphics, performance, user interface since the first v55 ptc release.
I have not noticed and am able to report whether this firmware includes the performance boost announced in the showcase.
I can only continue to confirm the device is smooth and well usable in all its basic functions compared to v54.
However I would suggest to @Ryanality that you share some release notes as you release updates so that beta testers can focus more on what to test.
Thanks, I also just got v55ptc updates on both my Q2 and QPro. So far I also don't see any differences or improvements. Minor complaints are that my QPro controllers still take too long to stabilize in the Quest home and the Q2 battery management issue is still not completely fixed (at least the headset now charges up to 97% but the green light still never goes on). Otherwise, everything is still playable.
Aside; I only see those occasional white sparkles if I enable mobile asw in ODT.
unsure if you are aware or if anyone has posted but games that are 3rd party games if you try to install the apk from on the headset it closes and wont install.
also i have tryed a few games where you need to setup the room to play unfortunately for some reason i cannot progress beyond any room setup it just tells me i need to setup the room after i have already completed it and cannot progress to play the games... The main game in question is Rube Goldberg Workshop.
As for you battery charging. I doubt it's the firmware. I had this happen to where it would not charge all the way and this will get worse and worse. Your battery is starting to fail. Mine got to the point it would only charge to about 70%. I ordered and replaced the battery myself. I did a video on how to replace the battery. It is not for the faint of heart if you are not mechanically inclined. Video: https://youtu.be/hu4-Ly3eFTw
@FinlessBob Pretty sure it’s a problem related to the newer Android 12 OS. When it first came out around v51 all of a sudden my headset battery would not go above 87%. With the very latest v55.ptc update it now goes up to 97%. Still short of 100% necessary to turn on the light green.
Maybe future updates will fix this. Anyway, time will tell I guess. In the meantime at least I’m still getting good runtimes. If the battery was actually damaged I’d expect this to drop significantly.
Actually not fully correct. Runs times may not go down at first. I took apart the old battery and there are sensors and pads that the oculus uses to determine safety of the battery. Like if it is swelling, etc. It will not fully charge it if it senses battery "life" is degrading.
And my story is the same as yours. When I got V47 (as I recall) just after is when I noticed my battery would not fully charge. In fact I contacted support and they were going to replace my 2+ year old Q2 for free for this problem. However they only had "so called" refurbished units. I did not want one of those and that is when I decided to replace the battery myself. After I did, it charged to 100% and is still charging to 100% now.
If this was a firmware issue, far more people would be complaining about this. And yes, the level it charges to can vary. I saw the same thing. Sometime 90%, sometimes more or less. It kept getting worse over time until at about 70% run time started going down and I knew there was a problem. I know you doubt what I am saying but my bet you will experience this get worse with time. When it started doing that for me, took about 2 months to get bad and charge only to about 70%.
@FinlessBob Not questioning your experience mate, you may be correct. Esp. given your new battery is charging to 100%, and I assume you get the green light.
However, my Q2 battery problem didn't start until v51 final when the OS changed to Android 12 and since the last update it seemed to be better. I'll monitor it for another month or two to see if this improves or not. If not, I'll contact Meta support and see if they can help. Thanks mate and cheers.
Same here, I've seen it start jumping and warping badly after a period of time. Even doing multiple factory resets I get the same results except once it looked like the color feed completely locked up but the black and white images were still updating so you could turn your head and see the stereo pass through in black and white with an old color image that was not updating. rebooting did turn the color updating back on but then after a few minutes it started jumping and warping badly again. (I did send a video of the issue when I reported the bug in the HMD).
Been having unplayable lag in Breachers since v54 and v55 PTC does not fix it even after multiple factory resets. Been going on for weeks. This applies to Airlink/Virtual Desktop/other games when I last tried too but I'm not going out of my way after the 10th+ factory headset to test extra apps/games at this point. Tried a 2nd headset I have with v47 on it but Breachers forces an update to v54/v55. These updates effectively ruined the internet on all my Meta devices and there is no way to rollback. Excellent work killing off a long term daily habitual user Meta developers, kudos.
What the heck happened? When I first got the the v55 PTC, the library was finally fixed and using my preferred filter and sorting as set in Settings -> Personalization.
Now, it is back to showing my full purchase history (All) and the filter button is gone.
No one in their right mind wants to see their full purchase history every time they open their library. What is the point of letting you set a preferred filer and sort if the library is not going to use it? This has been broken and fixed at lease 3 times in the last 6 months.
I'm on v55 and have also noticed this issue and mine is the same it gets to 87% then stops charging and this has only started happening since the Android 12 update, the strange thing is if I connect a battery (BoboVR strap) the headset will then continue to charge and the green light comes on at 98%, now like you I believe this is a software issue rather than a battery failure, because in Android there is a setting to limit charging to 80% or a little bit more depending on manufacturer but we can't get to the Android settings on meta devices, I would think they are doing this to increase battery life as they have had lots of returns due to battery failure ?! This figure of 87% is too coincidental for both of us!
I dont understand what is happening. I had serious stutter issue using airlink since v54. I switched on PTC to get V55 and the issue got worse. After multiple tests for days , and reading through the entire post on this topic, I gave up trying to find a fix and decided to wait for the next update. Today, I tried and had no more issue with airlink. Butter smooth , no lags . The fact is I didnt change anything on my Quest 2, and my internet connection hasnt changed. Same for the pc. The oculus pc app is still at the same firmware. No updates since yesterday (and I still use airlink to preview my game on unreal engine every day even with the stutters.) What the hell happened ??? I' m not complaining, but as a developper I d like to understand. Does the headset/pc app do silent updates ? Did this happened to anyone else?
Update: Well... After taking a 15 min lunch break, stutters are back. I didnt completely shut off my Quest. Just sleep mode. I tried rebooting it, but doesnt fix the issue. Stutters stutters and stutters. I really dont get it. Before Lunch I had not a single stutter. And I was on it for more than an hour... What the hell
Hope this would help anyone with the same situation as i had before:
Problem: updated to v54/v55 - stutter as xxxx - frequent disconnect - quest pro almost unusable
Solution: - (important) stopped using airlink - use VD (MUST use beta version) - wifi 6 either disable it altogether or fixed the bandwidth to either 80mhz/160mhz
Hope this gives some alternative to anyone who has been experiencing this BS and have been so fed up with the disconnecting and stuttering.
I really enjoy the new skybox (experimental feature) picture function. I use sidequest to save my Audio Trip maps offline and add others.
New oddity since the last update that I have been able to reproduce:
If I just connect the headset to the computer with a cable, all is fine. If I load import/export files and then go back into the headset the personalized picture is gone and the default home skybox is there. Or sometimes it is just black where the skybox should be. If I leave it as is and open a game and then exit the game to go back 'home', the personalized picture is back in action. There is some type of refresh for it that is triggering at odd times.
I prefer to have the attached view than the default one. 🙂
Those of you with flashing pixels, are you using AirLink and have Mobile ASW enabled ?
If yes, it's known that Mobile ASW makes a characteristic visual artifact when it reprojects due to network interference (it usually looks like static rainbow snow, but maybe it now shows as flashing pixels).
I use cable link, and asw turned off. I see flashing pixels since v53 on quest pro. Tried to switch all possible options in debug tool, nothing stopped these pixels
I'm not sure if there was an update to v55 late last week or not, I didn't initiate one myself, but my complaints about passthrough are resolved - it's quite solid for me now. I did increase the lighting in my room which may have also had an affect, so anyone with similar issues as I listed before may want to try that as well.
Good VD performance (HEVC 10-bit) for PCVR using the High resolution setting with SGSR and am really happy/downright surprised how good it looks (3080 10G). Standalone is running very smoothly as well including when having QGO enhancements enabled.
I am seeing the pixel artifacts still, they're intermittent and as other's have mentioned are more noticeable in dark sense(which makes sense since they're white...like how glare is easier to ignore in bright scenes).
Specifically with the new virtual environment the mirror causes bad performance, though others have reported it affects multiple. If I move away from the default location in Futura it seems to help but I assume that's only because it's lowering the mirror's render res. I don't have the same issue in Abstraction however.
I'm not on PTC, but also want to note that my battery also stopped charging to 100% as soon as the firmware jumped to Android 12L. It now gets to 96-97% and stops, I don't get a green light anymore. Way too coincidental for us all to have failing batteries at the same time, this has to be firmware related and battery calibration issues.
my battery does that, but other days it does get to 100%. the green lights are on, but yes often times i will check, 97%, controllers will get to 93% but other days i check it and all at 100%, its hit or miss mostly miss. My headset is around 2 months old.
Don't say all of us. In fact on the larger Facebook Q2 groups, no one is complaining of this yet. I do not have the problem as my battery is new (5 months old).
Yeah oddly enough my version numbers didn't change at all, I'm still on Runtime 55.0.0.93.x but the issue is clearly fixed and I didn't change anything. I'm finding it odd that nobody from Meta acknowledged the issue despite a number of people on here and on Twitter saying they had it also for the last week.
I'm just going to take the fact its sorted as a win and wait for the next thing to break.
Even better, just put my headset on for the first time today and am now on v55.0.0.111.713.x and wow! Meta have pulled something sweet out of the bag. Pro Controller detection is now almost instantaneous, I rebooted a couple of times & sure enough it's bang on!
I was out to dinner and came back to find I just got that same update! Now to do some tests to see if I still have the random white pixels sprinkling on the left side.
Nope, random pixel bands are still there in this release too. 😞
I also got the new v55ptc 55.0.0.111.713 earlier today on both my QPro and Q2. Everything is running very smoothly with standalone and wireless PCVR using Air Link. Prior to this update I would occasionally see some white sparkles in dark startup menus like the SteamVR Void and dark menus like with Air car or the standalone Tripp app. These seem to be fixed now, for me at least. I did do a few full power down/restarts and cleared my Guardian history after the update..
Not sure if this has improved my Q2 battery management issues. I have it charging right now so I guess I'll find out soon and report back. Cheers
Edit; Nope, Q2 battery management is still no-go-to 100% or Green Light, lol!
Controller tracking seems fine but on both headsets 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.
Tested out a few standalone, Oculus, Steam, and VivePort apps and these seem to work fine. Also msfs is working great.
