PTC v55 Release Megathread

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.

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.

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   

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.

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.

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.)

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?

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.

barabba9174 

I had this same problem recently. I think i removed my devices and also did a factory reset, i think it took me doing some of that twice. it would not pair or put the link code up, finally it did work though but it was not just easy.

Ryanality So after a factory reset on the firmware 55.0.0.130.713. The problem with graphical artifacts or white sparkles or pixel glitches is still there. I don't know anymore, maybe it's a problem with the GPU in the helmet. Or I'd like to go back to v48-v51 to find out for sure.