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 v57 is starting to roll out for Meta Quest Pro and Meta Quest 2 soon.
Our new process from v56 worked great to create specific threads for each issue that's happening so let's do that again!
If you're seeing an issue or bug after updating to PTC v57 jump on over to ourGet Helpboard and search for any existing thread, if you don't find one, make a new thread. Please add the tag PTC v57 to the thread and in the title. This way everyone can look for just PTC v57 issuestoo.
It's best if you can post each bug you spot in its own thread, to keep track of individual issues separately.
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!
This is important as the thread is linked to in about a half dozen outside forums (virtual desktop, reddit etc) who use it to keep updated about the progress on this issue and potential fixes - the thread is still used daily with about 8000 current views.
I have checked and this thread does now appear in the search link provided by @Ryanality above. I hope the thread issue can continue in this manner.
@Ryanality Thanks mate, I look forward to trying out PTC v57 soon on both my Q2 and QPro (main one I use now). While I'm not a big fan of this new Blog format I do see your point about posting issues in the Get Help section.
Just an idea but I think it may be better for you to create a separate PTC v57 Mega thread in the Get Help section to collect and discuss any issues. I would suggest that users only respond to the Announcements Blog thread when noting PTC updates, including version numbers, so we can keep track of rollouts. Also, maybe a brief report on how well the PTC is working.
Once v57 goes final I think you should close postings to both PTC v57 threads. Then the same, open a v57 Final Blog Thread in Announcements (as per normal) and also open a v57 Final Mega thread in Get Help section for general discussions. I think that this will provide users a more direct way to discuss these updates while also keeping the more user friendly non-blog format.
Anyway, I hope you find some of my suggestions useful and will consider trying some or all of these out. Thanks mate and cheers.
Edit; @Dave200S I like your idea of tagging ongoing issues that carry on from previous versions. Thanks mate.
@EveryDay10 When Ryan says that a PTC is rolling out soon (as opposed to rolling out now) I normally see it about 3-6 days later. I always check this thread to see if any have got it yet. I usually find that once some get PTC it gets rolled out to others on PTC pretty quickly. Anyway, when I get ptcv57 I'll post that here. Cheers mate.
This is a joke, we have the same problems since v53 where you practically ruined everyones Quest 2 devices for them to ultimately upgrade to the newer device releasing next month.
All the while playing "passive aggressive" with each coming update by completely ignoring all open issue and requesting people to open new threads over the same problem on every new release.
Awesome way to minimize the actual damage you are doing to the FW\Device since this way, you will never have to actually deal with open bugs, as you completely scrub the list on each new update.
NONE! of the issues reported since v53 were fixed. Absolutely 0! yet, you keep pushing more updates to already broken build.
I still want to go back to v52. and the fact that we are already in v57 only comes to show how rushed each update is. as if there is a commitment to push updates every 3-4 weeks, and it doesnt matter if the QA is garbage.
All the while playing "passive aggressive" with each coming update by completely ignoring all open issue and requesting people to open new threads over the same problem on every new release.
@pikpukpak Seems to me you are the one being a little passively aggressive mate, lol! I've been on PTC with both my Q2 and QPro since about v51 and haven't had any major problems. The only major issue I've had is with my Q2 battery management (not wanting to charge to 100% or ever get a green full charge light). This still might just be caused by the 2.5yo battery age and nothing using an external battery doesn't solve. Other minor issues (I always do bug reports on these) seem to slowly get resolved, for me anyway.
If you are an experienced user than you know by now that you cannot simply rollback to versions older than the current non-ptc. Continuing to complain about this isn't very useful imho.
Really up to you whether or not you want to participate in the Quest PTC program. In your case I think it might be a good idea for you to avoid this and just stick to non-ptc. Again, your choice.
I too have hade the white specs while using airlink sinc v53. A few weeks back, I did however notice they went away while casting at the same time to a chromecast. I stop casting, spots come back, cast again to chromecast, no spots. This is repeatable for me as of right now. Can anyone else verify the aswell, if so, we may be able to point them in the right direction to the solution.
Is there any chance at all that developers will bring back the "Lying Down Mode" that was present in v53 and later removed, within this decade? It's virtually impossible to enjoy 3D VR YouTube content while reclining on a couch, especially when your head is resting on a pillow. This is due to the completely baffling absence of an option to adjust / shift the image center along the vertical axis. It's frustrating that there's no way to comfortably watch VR content while lying down. When will this bug be fixed??!
OK, I got v57ptc earlier today on my Quest Pro and oculus desktop app public beta. I haven't updated my Q2 yet but I'll do this later. Anyway, the version #'s are:
Headset; 57.0.0.191.669
PC app; 57.0.0.192.153
The update included firmware and controller updates.
First BIG news is in the Quest home we now have Legs! This looks pretty cool and when you shift around a bit they kinda move with you. I'm not sure they get tracked with the QPro using eye, face, and hand tracking, but I'll try this later. Pretty cool feature though imho. The new menu's are nice and you can directly use hand tracking to position and use them. So, no more direct touch in experimental. Probably not something I'm going to use much because I mainly am using PCVR wirelessly with Air Link. Shifting back and forth from standalone to the Rift home void/dashboard menu seems a little more solid.
I tried a few standalone Quest store, Rift store, Steam store games/sims and everything seems to work fine. The only problems I found so far is my hands do not show up with the Rift store Toybox app and this makes it impossible to play. Fortunately it's not something I play very often and just use it to test controller tracking. I have filed a bug report for that.
Anyway, all I got so far. Once I get a chance to update my Q2 I'll post those results. Overall, seems like a nice update.
Edit; Tried with my Q2 and same good results, except the hands not showing up with Toybox. Also, the washed out colors in Natures Trek Rift store version seems ok now on both headsets.
I know you omitted it because of health concerns of your users (it would be abused) but I've been recently diagnosed with back pain and doctors ordered me to lie down and rest for 15 days with minimal physical activity.
I can't watch movies in Skybox theatre because when I use a pillow it gives me back pain.
@cael.thunderwing Ya, with Air Link running Toolbox there are no hands. Pressing the oculus button brings back hands and the dashboard but as soon as I go back into the game they disappear again. Hopefully @Ryanality will pass this onto his team and get this fixed soon.
@TomCgcmfcsame, i rely on Virtual Desktop as somethings up w/ my Motherboard's USB3 chipset and it cant sustain the usb bandwidth to keep a consistent FPS over Oculus Link. (i find while an overall Lower FPS total w/ virtual Desktop, its more consistent than i had w/ AirLink & Oculus Link.)
@cael.thunderwing or @TomCgcmfc , would either of you be able to start a thread for that issue with hands? I'll send it over to the engineering team to look into! The separate threads make it easier to keep track of the discussion for just one issue at a time, and it's easier on engineers who want to see the word for word feedback on what you're experiencing without having to sort through all the other comments in a thread.
@AzeezAncelo, I'll let the team know folks are still interested! That feature was tested out during the PTC for v53 and it was deemed not quite ready yet. I believe it's still on the list for the future once it's ready to go.
@RyanalityIf the "Lying Down Mode" isn't ready yet, it's possible to return it to the "Experimental" section, as it was in V53, and based on feedback, this worked fine.
From the moment of purchasing Oculus Go up until today with Quest 2, this significant option was only available in the v53 update and then removed...
It seems that after PTC v57 the Companion Device Manager is no longer working correctly. The Companion Device Manager window appears but it keeps loading and the device allowing-window never appears. This was still functioning correctly in V56.
We now have legs in the mirror and can teleport to a larger area of the home space vs being limited to the dots on the floor.
I don’t think the panel view option was there before. It is very large and in charge and doesn’t show more content. You can only resize it inward to a tall cell phone shape instead of down and in for a more reasonable size.
The menu appears a controller span away from the top of my legs – way too close to be practical. So once again moving it up and out every time. Pic is with my head bent completely down to see it. Needs to be in a more usable location.
Menu item selection sound seems louder and there is sometimes an echo effect. Really wish there was a way to turn it off completely like I can for other systems. If there is, please let me know.
Full body estimation doesn't seem to work. When crouching, you avatar doesn't crouch, and when doing any type of kick movement, no leg movement happens. Also, my avatar has boobs now?!?!
For the second time, a Meta update broke my VZfit biking experience. With 56, every time the animated birds that were working perfectly fine with 55 popped up on screen, it crashed the app. Thankfully the great support people at VZfit managed to fix that.
I just got 57 overnight and now my stationary bike, which normally automatically connects to VZfit and worked just fine yesterday, refuses to connect. So I went into the headset settings, found the bluetooth area, told it to connect to the bike, the bike beeped and connected. And then immediately beeped again and DISconnected.
So now, unless something gets fixed fairly fast, for the second time in a row, I won't be able to finish a VZfit challenge due to a Meta update breaking something. At least before all I had to do was turn off the animated birds and I could still ride, this time I can't ride at ALL because it's broken in the headset itself, not in the app.
@AiroKunOmega Maybe just select the right bra size, lol!
@karen.cusimano Send in a bug report and let your fitness developer know. Sounds like there may be some BT related issues with v57ptc. Hopefully these will get resolved soon with further beta updates.
@AiroKunOmega I don't think there is leg tracking in the headset, so kicking isn't possible. What you see may be estimated movement based on head movement like LIV has or so I believe....maybe not even that much. I think small trackers may be coming out on the market this year from other companies that would make that possible for you & others. The last part of your comment had me chuckling, but then again they are appropriate for my avatar. 😆
DL PTC V57. & now my left pro controller wont connect to headset. the mobile app saids its connected by its not tracking in headset. i have also removed it from the headset to reSync it. That does not work either. The only way it works is if I disable WiFi & Restart my Quest Pro. but once it reconnects to internet the left controller is gone again. Anyone here can help me out. thx.
RoadToVR mentions that someone found in the PTC v57 settings a few things that aren't currently exposed. There's an option to turn off the mirror, an airplane mode (not to block wifi like on phones, but to fix tracking while on a moving vehicle) and an extended battery mode (drops image quality).
I'm guessing the airplane mode will disable IMU tracking and rely on cameras only, since plane movement will mess with the IMU's accelerometers. Although that makes tracking laggier (cameras are 60Hz, made of interleaved 30Hz controllers and 30Hz head, while IMUs are 500Hz).
I am currently on PTC v57. I seem to be having issues with getting Airlink to work after I updated. I even Updated the Oculus App on my PC to v57 and I got it to work for a play session then I was unable to get back on Airlink after I put down my Quest Pro for a little bit and came back. Is anyone else having this issue? In addition, Im still having issues with my Logitech M650 L Bluetooth mouse with causing my view to Stutter whenever I move the mouse and head. This has been a problem since v54. Will this ever get fixed? Thank you.
@Rayne23 I'm finding that I have to completely end the 3 oculus tasks in task manager or restart my computer if the issue is on the PC side or I have to restart my headset if it is on that side, more often. I keep my headset on/sleeping most of the time and when it wakes PC or it doesn't always find the connection. Once established it is fine.
Side note: There is no longer a way to pin apps/games to the universal menu. The option is there if you click the 3 dots next to a game, but it is greyed out.
@Okuda.IOI I didn’t lose eye and face tracking with v57ptc. Both show up and working fine when viewing my avatar in a Quest Home mirror. Maybe go into your settings and try enabling this again.
Tired that several times and still nothing, also i'm not the only person effected by it ?! had another update today, but still the same, have no idea what the update tired to fix ? Also anyone able to use just one controller and hand tracking together ? or is that another USA feature only like voice control ?
@Okuda.IOI I tried the one hand/one controller in the Quest home with my QPro and it seemed to work ok. I haven't tried it with any apps yet but I think it may be something that developers need to add anyway.
You're the 1st person I've heard about your eye/face tracking issue. Maybe contact meta support and see if they have any suggestions for you. Good luck mate and cheers.
I did contact support and so did someone else (in the get help section) you must have a different version of v57 than me, as I haven't got the one hand, one controller function either, I know they roll out features to different regions, but as far as I can see this version has given us legs that move like thunderbirds puppets and only work in the home environment! (a bit pointless really!) So in my opinion this update has promised a lot and given nothing but janky legs and broke a bunch of stuff..!
@Okuda.IOI OK I just got another ptc v57 update today on my QPro (v57.0.0.201.669) and my face/eye tracking also stopped working. I can't see these work when in the Quest Home looking at my avatar in the mirror. I've filed e a bug report on this.
Also, got an update on the oculus desktop app public beta (v57.0.0.210.153). Seems to work ok with Air Link but the controllers are still invisible with the Rift store app Toybox. Fine with other apps I've tried so far. Again I've filed a bug report.
Hopefully these will get fixed soon. @Okuda.IOI I think it would be useful if you'd include your ptc v57 version numbers as I have so we can make sure we're singing off the same song sheet, Thanks mate and best cheers.
Hey @TomCgcmfc, @Okuda.IOI, and anyone else noticing trouble with Face/Eye tracking, The team is currently looking into this now after reports that were shared by the mod from the main thread on the issue. We'll update that thread when there's more to share or if the team needs any more information. Thanks for jumping in and sharing!
I got update 57.0.0.201 on quest2, now my hand tracking has become buggy. Firstly, the hands of the avatar in the area of the hands have a clear break in the model, and secondly, when I release my hands to the waist, the helmet loses its hands and instead of putting the virtual hands into their standard position (to the waist), they begin to flicker right in front of the face, twitch, take strange poses, after a couple of seconds they disappear and after a second they reappear, and so constantly
It's been nearly a week since this PTC build was released and all the bugs reported when will we see the next release to fix a few of these issues ??????
@cael.thunderwing Actually the beta bugs reported so far effect standalone more than PCVR imho. Because I don’t use any face, eye, or hand tracking those bugs don’t effect my wireless PCVR using Air Link. In any case I’d guess we’ll see further beta updates over the next week or two. I’m pretty sure that Meta will want to have nice clean builds in place prior to Meta Connect later this month. It would be a little embarrassing otherwise, lol!
Once again my headset, phone app and PC app have all updated to v57 even though I do not have PTC enabled.
What am I supposed to report bugs are PTC 57 or just v57?
Changes seem to be mainly cosmetic. I haven't noticed anything new in the settings screens, maybe some stuff removed.
Still no filter options on the App Library screen. These disappeared and reappeared in v55 for me. Then disappeared after updating to v56 although another Meta person said it should be fixed in v56. Certainly not there in v57.
How do you distinguish the PTC versions from the release versions?
OK, I just got the new PTC v57 update on my Quest Pro; version 57.0.0.236.669. Still on same oculus desktop app public beta 57.0.0.192.153
All standalone tracking (face, eye, and hand) now seems to all work fine. You still need to select search on the app panel to get it to display like you want it to. No big deal, just takes a few seconds to do.
Tested out with a few standalone apps and PCVR/Air Link with Rift, Steam, and VivePort games/sims, including msfs flight sim, and all seems to be working very well.
I'll update my Q2 later today (really don't use this much anymore tbh) and let you all know if I find any bugs.
Of course, now we just need to wait for others to report how this update has bricked their headsets, lol! Just kidding, I hope all goes well with everyone. Cheers.
Edit; just a couple of minor bugs; my pro controllers and avatar body/arms still seem to take about 30 seconds to display properly when I first startup. Also, in PCVR/Air Link, the controllers still do not show up on the Rift store app Toybox. Neither are the end of the world for me but I have filed bug reports on both of these.
Edit#2; I just found another interesting PTC v57 option to turn on/off the mirror with any Quest home environment with a mirror. Go to quick settings/settings/personalization/objects. There's and enable/disable switch there. Seems to work ok. Cheers.
Edit#3; Ok, took the time to update my Q2 today to the same ptc v57 update, mentioned above. All’s working well, same as with my QPro. Poor old Toybox still has invisible controllers though, lol!
Also worth mentioning, I have yet to see any of those pixel sparkles that I very occasionally saw in previous updates. Actually, everything seems to be working very well now. Could be a bit of placebo effect but even my Q2 home and standalone apps seem a little snappier and a bit better clarity. Going in and out to Air Link seems is a little better as well. Overall, looking like a very nice update imho. Cheers
Why on earth would you do that to the experimental features section? i found all of those to be useful. Why do i update sometimes only to get feature reductions? I've had key game items just simply involuntarily removed. What else can i say, i like the border.
@vr_energy_rv Most Experimental options eventually make it to regular options settings imho. You just need to hunt and peck a little to find these, lol!
I just got a public beta update for the oculus desktop pc app today. This version (settings/general tab/scroll to bottom) is now 57.0.0.238.153
This update also gave me a startup note to update oculus drivers, which I selected it to do and these were installed. Everything seems to be working very well. I can't say I've noticed any changes but if I do I'll let you all know.
The controllers are still invisible with poor old Toybox, lol! Funny because it's the only app I've had any problems with so far. Not a big deal because I only use that app to test out tracking and gripping/grip releasing. This has always been better with Link and Air Link compared to Virtual Desktop btw, for me anyway.
I see that there now is a v57 final thread with some release notes (which don't seem complete imho). Once more users get this I'll probably shift my PTC v57 comments to that thread, with my latest version #'s (headset and PC) so Final and PCT users can compare notes. Cheers.
