Honored Contributor

PTC v55 Release Megathread

282 replies
75740 views

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!

Show previous replies

P

PainTitan

Participant

I think the laying down mode issue is still there. When I recenter, my VR perspective can tilt. Laying down mode toggle missing since before may. Very disorientating for locomotion or moving in games when standing up.

T

tanubon

Inspiring

Link Sharpening of Quest Link gets "Disabled", "Normal" & "Quality" now ("Disabled" & "Enabled" before). But Quality is just worse than Normal... only clear boundaries are sharpened, and most of the parts are the same as when disabled (very blurry). Is it mistake? or is it really Quality mode?

What Quest Link needs is improvements such as foveated encoding. Link is clearly lower pixel density than Virtual Desktop. Even Link uses much more VRAM, lower performance.

Strange super high latency problem on H265 is still there. When do you fix???

AS1C

Participant

Got the update V55, the issue with graphical artifacts/white sparkles/pixel glitches was not fixed(

T

Takumori

Participant

yep... seems so. This getting incredibly frustrating to put up with

JeffNik

Honored Contributor

Just got V55 about 20 minutes ago and rebooted. It happened while I was working on a VR QuestPro project in Unity. After the update, I can no longer run my App in the Unity editor. It crashes the editor. It worked correctly until the update. Can any other Unity developers who have the update see if it works for them? The project uses the Oculus Integration package, core standard render pipeline, The project is, of course set to Android. If I upload the APK directly to the headset, the app runs fine, but if I try to run it in the editor - the headset view freezes up and the editor crashes.

** edit **

It should also be noted that I updated the integration package to the brand new V54 that was just released as well.

M

mrbumpy409

Participant

Okay, so many are reporting on the Virtual Desktop Discord that the white sparkles issue, while improved, has not fully been fixed. As for the network lag spikes, some are saying its fixed and others are saying it's not. 🤷‍

D

dMs

Participant

Wi-Fi issues that EVERYBODY been posting for the v53 and v54 versions are still there.

S

Stugabaranda

Up and Coming

I joined the ptc and received the update of which I report the versions:

System version:

50577570021100150

Version

55.0.0.71.713.482426767

Runtime version

55.0.0.71.713.482406052

OS version

SQ3Q.220605.009.A1

Quest 2 device

I have not done any factory reset.

I played a bit both via airlink and VD for about 30 each and first impressions are that the stutters, artifacts and pixels on the right side of the viewpoint are gone.

I turned around myself several times to check if the blocks that occurred before recur and for now everything is fine, it seems to have returned fluid and without interruptions that compromise playability.

In the experimental functions it is possible to activate the new wifi interface

The prone mode is no longer present (actually I didn't have it anymore even in v53 and v54 official versions)

The controllers seem to pair more quickly when held, and the hand/controller transition seems to be more responsive as well

The guardian has not yet been improved in the sense that only one environment can be configured yet.

The room setup in the experimental functions has remained unchanged except that, among the furniture that can be added, the desk is no longer there while now you can add beautiful wall objects that are not seen in the home like all the rest of the furniture .

In the physical space menu, there is still the absence of the mixed reality menu that allowed you to add a desk and sofa regardless of the room setup in experimental functions,

and there is only the objects and furniture item that only asks you if you want to "see" the ones you add via room setup and reminds you; to see we mean the vertices and not physically see the object in the home.

Dashboard magnifier removed (which didn't work in v54 anyway)

The panel in direct touch mode can now only move again with the white bar under it while in v54 you could also grab it from the side and it was nicer (IMO).

Returning to the most important thing, ie the network peaks and graphic problems in VD and Airlink, as I said before, they seem to have disappeared but I reserve the right not to claim victory and to create illusory expectations because I read that the problem has reappeared for other users despite the v55 update.

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

E

Exius86

Participant

Just got the update. Brilliant, Meta, just f... brilliant! Now my AirLink doesn't connect no matter what I do! I tried connecting both through my router W-Fi and through the laptop mobile hot spot - none is working. Air Link detects my PC, the network meets all the requirements, I try to connect, it shows black screen and loading and then I return to the Oculus environment. "Connected to [PC_name]" prompt is shown on the bottom of the screen. Sometimes it shows "AirLink Connection lost" error, but very rarely. Usually it doesn't show any error at all, the Air Link just doesn't connect and that's all. I used Air Link to do some VR workouts and now I can't do that...

Do you have any QA at all? Or are you intentionally killing PC VR? And by the way that controllers disappearing bug under Wi-Fi 5 in standalone is still in v55 and it seemes even worse - happened several times in a minute while in v54 it happened once in several minutes. These updates are worse and worse...

Does anybody knows what is the latest public release? I want to leave all this PTC sh*t and turn off the updates at all. Untill they stop adding all these useless "new features" and prioritize on fixing BASIC functionality it's better not to update and stay on the latest stable version.

S

Stugabaranda

Up and Coming

HI.
if it was possible to go back to v51 I would not hesitate to advise you to quit the ptc, but since this is not the case because the latest "stable" release is v54 with its problems, I feel more conscientious in advising you to continue dancing on v55, because it seems that they are working on some solution that makes the base software more stable.
What you report is undoubtedly serious, but I'm right to suggest that you try to restart your device a couple of times and let the update "settle". also try to check if the oculus software for pc has updated to v54 (stable and not ptc).
Your total inability to connect via airlink seems to be a rare case at the moment because the problems usually reported concern network spikes, artifacts and stuttering, not the inability to start airlink. I know you're exasperated, it's sacrosanct so I don't blame your heat, but I advise you to be patient. the lack of technical support is well known so make the wisest use of the community (for me): vent to lower the pressure and not destroy the Quest against the wall, help and get help.

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

E

Exius86

Participant

I tried restarting the headset, restarting the PC and the router - nothing helped. Then I went to the Oculus debug tool. I had H265 there as a video codec. I changed that to H264 - and Air Link connected! Now it connects even if I set it to H265 again. Very strange bug!

Network spikes and stuttering is still there with Air Link. So, I haven't notice any improvemepnts so far. On the contrary I even noticed that the controllers tracking became worse (Meta Quest Pro). In v54 when I turned the headset on - the controllers almost immediately were in the correct positions, now they start in some weird positions and it takes them longer to get the right position. And moreover they tend to position incorrectly even after that (I hold both my hands together and one of the controllers positions itself lower or higher than the other). And this tracking issue affects the performance in such games as Pistol Whip or Gun Club VR pretty badly.

I agree that v51 was the best so far, but now even v54 seems great compared to this nonsense... If v54 is public - I guess I will quit PTC and forget this nightmare. These kind of thing should be tested with regular QA, not in public beta, this is basic functionality.

T

TomCgcmfc

Honored Contributor

I got v55ptc on both my Q2 and QPro earlier today. I spent about 1 hour with my Q2 and 1.5 hours with my QPro using a mixture of standalone and PCVR with Air Link.

Standalone after a couple of restarts was very stable and I think the graphics and passthrough look a little clearer. I did not see anymore edge sparkles even in darkish games or when watching movies on my Prime Video app.

Wireless PCVR with Air Link was very good using the oculus desktop app Public Beta v55. Like most major updates I did need to pair the headsets again. After that going back and forth between standalone and PCVR was a lot less cranky than it had been with v53/54. The new 3x link sharpening options (off, normal, quality) is nice. Probably personal preference but I really like the quality sharpening because it softens things a bit without being blurry like having it off is. Also, local dimming with my QPro seems to have a little less bloom and I never saw any edge sparkles.

Air Link was very smooth using 200mbps Dynamic bitrate and latency seemed to be around 55ms and did not have any significant spikes. Using 200mbps Fixed still adds about 5-10ms of latency without any significant difference in clarity, to my eyes anyway. All my Oculus, Steam, and VivePort games are working well and so are my flight sims (msfs and xp11/12). Also, all seem to work a little better after a couple of restarts.

Overall, I'm very happy with v55ptc so far.

My only major complaint is that the battery management of my Q2 with the Elite battery strap is still broken. I still need to disconnect the Elite battery before shutting down, then charge the headset and Elite battery separately. The Elite strap battery always charges to 100% but my Q2 headset battery never goes above around 88% and the green light never goes on. I startup my Q2 without the Elite battery connected and connect it afterwards. Again, I disconnect the Elite battery before shutting down.

This Q2 battery management problem started when my Q2 OS went from android 10 to 12 (~v51 final?). Hopefully this will get fixed sometime before v60, lol! No real big deal since as long as I follow my current procedure it works fine and I still get lots of runtime.

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers

Moriarti4

Up and Coming

Just going to throw this one out there to all the people having PCVR link issues, for month's I had all sorts of issues with both air link and VD and new routers etc nothing worked, so I went a bit insane and done a fresh install of windows 11 ! BANG all network issues gone and none have come back since before the V49 update! Now all I can assume is that a windows file somewhere had got corrupted by a bad meta update in the past and had stayed like that until it was over written during the windows reinstall ! I know it's a crap thing to have to do but if like me a long time ago I have windows and files on separate drives for this very reason, we all know how bad windows update can be sometimes !!!!!

LunchAndJosh

Inspiring

Glad that your fix was to reformat your whole pc, but for most of us the problem is with Meta v54, which they need to fix. Reformatting a whole PC is not a real fix.

Moriarti4

Up and Coming

My point was that no amount of meta updates is going to fix the corrupted windows file ! They broke it ages ago but can't fix it with an update as the file is a windows system file that they broke (and god forbid they admit they did that!)

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO