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 v56 is starting to roll out for Meta Quest Pro and Meta Quest 2 soon.
We're going to try out something new this time around! Instead of a single megathread, we'd like to gather feedback for specific issues in their own separate threads.
For example, if you've installed PTC and there's a sticker of a pink elephant unexpectedly following you around the room, jump on over to our Get Help board and search for "pink elephant PTC" or something like that, if you don't see any existing threads, make a new thread in there, put PTC v56 in the title and something like "Haunted by Pink Elephant", and post it. If you add the Label and Tag PTC it'll help everyone search for just PTC issues too. If anyone else is seeing the same thing, they can find your thread and jump into it to share.
Moderators will also help merge topics that are the same together so keep things consolidated.
It's best if you can post each bug you spot in it's own thread, that way we can all keep track of individual issues separately, and can notify everyone seeing the problem when there's news, or we need to collect details.
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!
@BOLNICHKA39 Normally I've found that the PTC's and final releases eventually match each other over time. Same goes with the oculus desktop pc app public beta as well.
Hello. My Quest 2 is in PTC v56.0.0.115 and now I can´t use Quest Link with Air-Link. Cable Link is ok, but Air-Link don´t work. Also if I use Oculus Casting and you use full screen mode, the casting is frozen. How can I go back to v55?. Thank you
While transitioning from the audio trip editor tunnel back to the main game menu the passthrough activated. Double tapped and the black with purple guardian lines environment was present that I can only get rid of by restarting or shutting down. After shutting down the version must have changed because the guardian floor was really off and a few functions like the guardian/boundary, etc. are different in the settings section. I am supposed to be 162cm on this calibration tool and now am 26cm taller without any other changes to my play space or lighting.
I would hold on any roll out of these builds until you get one that is solid vs adding features every month that also include oddities.
When did multi window become available in touch mode ??? (running v56 PTC) never had it on previous builds and nothing about it on the release notes, don't get me wrong it's a step in the right direction, just need to make the outta windows slightly angled inwards.
I'm having a different Airlink issue now. before I was getting white pixels in the right lens. Now while playing in 120hz mode (And honestly I need it at this point) The lower half of the screen gets very pixelated then it get's stuck. Almost like no vsync but the tears stay and then gets all pixelated, while the top half doesn't change. This only happens in 120hz mode. 90hz works fine but I can't take not having the extra smoothness. The smoothness doesn't break even when the compression artifact (Lower layer only) come in. It's extremely smooth. It's driving me insane and honestly am very upset at this point. Just allow us to choose which driver I can use. V51 worked the best for me.
New oddity that just started happening this past week.
When I am in Audio Trip, I press the oculus button to bring up the resume/quit game menu options. Sometimes it doesn't bring up that resume/quit menu option. Instead it takes me back to the home environment without fully closing the game. The game window isn't visible, but if I click again on the Audio Trip game icon that is on the Q2 taskbar I go right back into it without the game loading.
It's happened several times now and just happened again today. I haven't figured out why it sometimes does that action and not others.
Fixed my screen tearing issue that I mentioned earlier. User codec h.264 instead of 265. Make sure to restart the service and leaving code slicing on. This took care of my issue.
everytime trying to use the quest pro after the update. it keeps on popping up the notification saying your controller cannot be track and the notification keeps popping up like an annoying pop up ad on a website.
The quest pro controller stops working with Real vr fishing as well. no matter how far you try to throw the fishing line out, the controller only register it as a small movement and you see the fishing line just dropping in front of your face.
The quest pro controllers don't seem to want to stay connected to the headset at all in this latest update. Which is extremely annoying.
Actually- they ARE connected to the headset, but the lights flash and it stops tracking completely. And sometimes all lights shut off. But i know the controller is still on and getting button input. It just doesnt want to track anymore. Its making quite literally every vr experience unplayable.
@armax23 That doesn't make.... any sense. Im using airlink when this occurs. Pretty sure disabling my wifi would kick me off of being linked. I kinda need the wifi.
@Cassbunny that guy has to be wrong about why he thinks he fixed his controller tracking. now i have jumped to a different SSID which helped my tracking in the past. In fact I think if you only have one SSID and you forget the network which will kick you off, my controllers stay good, but ticking the box to disable wifi makes your controllers just funky.
But yes of course if you are using airlink you need the wifi.
I didn't fix it, better call it a "workaround". Because I agree it's impossible to play with Airlink this way. So I play via Link with cable. It's just a workaround until they fix the problem in the firmware. My problem is that controllers were losing the tracking each minute, they just kept disconnecting and then connecting again until the next minute.
But then I read somewhere in this forum, that turning off Wi-Fi helped one guy to fix the problem with tracking, and it helped me too. With WiFi turned off, controllers work as they should. The problem was introduced only in v56 for me.
Does anyone know how big is the size of this update? My headset, being charged and connected to internet, had been stuck in the "Updates in progress" screen for 2 hours without finishing updating. Eventually I just canceled the update.
When Oculus link is wired, there is a kind of transparent ghosting that moves with my head as I turn, it is very obvious and distracting, video drivers are updated, new link cable from Kiwi , reset the headset, I went online and others were having the same issue in fact one user posted a registry fix stating it is a bug, I applied it , it worked a little but the issue still exists, when I use airlink with the dlink wireless adapter there are no issues, only when the cable is used, that tells me it is not a computer or a usb issue as the adapter is connected to the usb port.
I have made so many support tickets and been on the forums for basically months, left on military orders, came back, and this thing still doesn't work properly. It worked for - one day - and it's back on the BS.
Being out of the PTC I had no choice but to take official v56 update. The Quest Pro controllers tracking is not acceptable in this version. Controllers lose and reestablish tracking so often that it makes the whole experience very frustrating. I never had this behavior in v55. Meta, pls fix this a.s.a.p.!!!
With this version, controllers randomly jump to different positions or lose tracking completely for a couple of seconds.Also, finger tracking when holding controllers is buggy and often doesn't register the proper index finger position.
Before the v56 controllers worked almost perfectly
My headset took the newest update of version v56 yesterday. So the v56 version ends with ...93 and runtime with ...14. After two longer sessions with the USB link and also airlink, I never experienced the tracking issues again!
That's great to hear, @Kozakblaha! I am glad to hear that the headset update was able to resolve the Air Link issue and that you are able to get back to enjoying PCVR. If any new problems come up, please share them with the rest of us, and we can pass that information on to our engineers.
To the guy that said are they QA this??? the answer is simple meta doesn't QA jack sh!t They release useless features, breaks the compression, Create the famous sparkles compression artifacts. Add more useless feature doesn't fix any of the compression, mem leaks they have for the past 3 patches. Still there. Every game.
How can pc link chew up 11.3 Gb of vram at the game menu?
Virtual desktop idle around 6Gb same and in game 9Gb but pc link over 12Gb- poor optimization and mostly mem leaks all over the place.
