Honored Contributor

PTC v54 Release Megathread

206 replies
47190 views

The Public Test Channel (PTC) for Quest v54 is starting to roll out for Meta Quest Pro and Meta Quest 2. Thanks everyone for all your feedback!

Let's use this thread for collecting feedback on v54. 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.

Thanks again to everyone testing out PTC and sharing your feedback! We appreciate your help testing out the core functionality of software as we develop!

ptc

Show previous replies

J

jay4405

Participant

What the point of a public test channel if one doesn't listen to the community. Us Guiney pigs opt in, tell you issues and you release the build anyways. Everyone agrees V51 is awesome. So why can't we have a roll back option like everything else. Roll back options are key when it comes to PC VR market (Too many variables to not have a roll back option.) Then you release the updates slowly which sounds like a damage control, however then users complain about the experiences, in my case Airlink is useless which makes the headset useless to me. Seriously please consider listening to the community when problem arrive and delay or stop the newest builds. Now I'm on v53 which is awful for airlink (Worse in every way) and hearing the same with V54. You get free beta testers which valuable data that's obviously being ignored. Right now you guys are king but do have some stiff competition around the corner. If down the line I found an good headset that allows me to roll back drivers (Valve deckard) maybe then I might changed ships. I love you software hardware when it works and praise about it. Please start listening to the community. Hell just re- release V51 as V54 and I'll be happy. Last ditch effort, please add a roll back option, it's pretty absurd there isn't one. Your not just a console, you connect to a PC with many variables as I'm sure your aware of. Please Roll back option, Roll back Option, Roll Back Option. It unfair that we have to suffer for months before playing again.

C

ChristinaPM

New Participant

I could not agree more!! v51/v52 worked PERFECTLY for me, and v53/v54 broke Airlink which I am DEPENDANT on for work, so I now have to pay 400 quid out of pocket for a Pico 4 as a backup because the Oculus software is so broken and unpredictable. PLEASE BRING BACK THE ROLL BACK OPTION, META!!

I am even considering stopping support for Quest headsets in the future (was planning on getting Q3 this winter), but due to the horrible software and no rollback, I don't think I'll be coming back tbh.

J

jay4405

Participant

Yes, Driver roll back options need to happen. We need to be able to install manually and roll back manually. Now I'm probably not going to be able to play for months now. Maybe if everyone screams Roll back option they might get the common sense on that. At least make PC VR OCulus desktop with a Driver roll back option and allow me to choose which driver.

Moriarti4

Up and Coming

Meta has no interest in PCVR at all ! everyone is going stand alone, look at the forth coming Apple headset rumours! The problem with PCVR is so many various combinations of hardware and software to code for! Look at those poor AMD GPU owners stuck on max 100mb due to a bug in the AMD drivers, Yes I agree you should be able to roll back the drivers, the only way to currently totally remove the oculus software from your PC is to use a 3rd part uninstaller (kills all reg etc) There is very little money in the hardware side, it's all about the apps and games for that ring fenced system! again look at the App Store for example and the amount that makes per year! So when you think meta isn't listening to you ? YOUR RIGHT ! it's not worth there time! We are in the early days of VR/AR up take and I look forward to the day we can dump the PC totally much like what tablets have done with bulky laptops. Before I get flamed for this, I too am a PCVR user with a Quest Pro and have had issues with wifi etc I want the best graphics and game play, but like living through the years of zx spectrum, C64, Amiga 1200 then 486 PC's i've had to wait for someone to build it cheaply.

P

pitchBLAK

Participant

I've been getting high AirLink latency on my Quest Pro ever since upgrading from v51 (happens on both v53 and v54). I do not experience this on my Quest 2 at all.

I've tried:

- Different channels on my router (both DFS and non-DFS)

- Forcing my router to 160mhz and 80mhz

- Using both h.265 and h.264 (w/ and without sliced encoding)

- Turning off Local Dimming

- Turning off mobile ASW

- Rebooting the headset and controllers countless times

My router is directly connected to my PC via CAT6 (1m cable), have also tried each port on the router, including the 2.5 multi-gig port. I've updated the router firmware too.

My PC specs are:

CPU: 5800x3d

RAM: 32Gb

GPU: 4080

Router: ASUS AX86U

I've been testing sitting about 1 meter from my router and it is instantly reproduceable in any game or even the Oculus home menu. No other device is connected to the wifi6 SSID than the QPro.

Hopefully my image is attached, but anything over around 130mb fixed (regardless of h.265 or h.264) starts getting above the 20-30ms in transfer latency (both encode and decode are fine). Soon as I put it to 150mb, it gets into the 100ms, then at 200mb it's an utter freeze fest at 200-350ms.

If I set it to dynamic, then it doesn't want to get any higher than around 80mb.

On the direct contrary, my Quest 2 does not exhibit any of this... even at 200mb, transfer latency is around 15-20ms.

This is not an issue on cabled link. Both QPro and Q2 are around 5ms transfer latency even at 500mb h.264.

Oh also, this is my second QPro, first one had a dead pixel and it lagged on v53+ too. Very much like this fixed as it dampens the PCVR experience quality for sure!

T

tanubon

Inspiring

I have terrible latency, too (since v53) on H265 Air Link. I was able to use 200Mbps (even higher) smoothly before, but currently super high latency.

A

Ausimui

Participant

just a reminder for everyone, when you swtich off your PTC, beaware that it might for some reason restore you back to v53 (which erases everything and you have to do everything setup again). EVEN if you do not download the update, sometimes it just automatically "f" u in the "a". So beaware. by the way, both v53/v54 screw everything up and I have to go back to my quest 2 just so that i can stick with v51.

S

Sakigun

Participant

How to roll back v51, bro. Thank you

A

Ausimui

Participant

Once you are on v53, you are done. no more rolling back to v51. Some have tried sideloading the v50 but still stuck with v51. v53 is your closest.

S

Sakigun

Participant

Does anyone know how to roll back to v51, v53 uses too much battery, and lots of bugs. PS: i went to v54 but no better either. Sorry my English is not good. Thank you

J

jdawg461976

Participant

you guys mentioning these ASUS settings, i also had an ASUS router i just returned because of all the problems I was having with my quest pro. I got a netgear nighthawk and all my problems are gone. Reading all of this it sounds like the ASUS just needed some special config and possibly the nighthawk just didnt have the capability(which is luck for me).

Edit: I did find the setting you point to on the nighthawk(you show the ASUS). I enabled that already and maybe that is why I have no issues with the nighthawk.

Moriarti4

Up and Coming

When I had really bad issues with airlink across multiple quest pro updates, i bought and returned about 4 different brands of router and the results where always the same, the reason for sticking with Asus as I find it straight forward to alter the pro settings compared to other brands as it turned out it was windows that was causing the issue! (Fresh install of windows 11 fix it!) All this said you shouldn't have to alter the settings to get it to work, you don't do that for any other wireless tech you have ? I guess that's why they tired to release the Meta Air Bridge (which didn't sell well due to over priced!)

A

ArcAngel115

Participant

heres the thing. v51 WAS 100 percent stable for me. And to not provide me the option to maintain that stability is wrong. Does Nvidia or AMD restrict what drivers we chose to use? No, we can maintain a funtional configuration even after driver updates come out. We are ALL having a degraded experence , just most people dont realize it or dont care. Its those of us here who are vocal about it because we have some technical knowlage and its out duty to gripe so the silent masses are properly served.

Meta needs to realize that the reason that the quest 2 sold so well was one simple thing. PCVR WORKED! As a stand alone unit, the quest 2 is just meh. Again, yes, standalone was drove masses to the quest 2. Then it drove many of those masses to invest in a quality multi-thousand dollar gaming PC after realizing how crap stand alone was. Stand alone got them in the door, both the end user and Meta, but PCVR gives the quest 2 its legs and longevity.

S

sibirlupus

Participant

For you, yes. For others it may not have been stable. The real points here are that this is an effort from multiple parties to have continuous updates be a thing for our Quest headsets. So to sit on an update and refuse to move from it helps no one and leaves the device open to possible future issues. Also, this is about how you respond and address things. You are yelling at "Meta" to fix things, but your are really yelling at actual people that make and support this hardware/software. The phrase "You get more flies with honey than with vinegar" really holds true.

Asus G20CB (I7 6700, 32GB RAM, 870 EVO SSD x2, GTX 1080 Ti) Linksys EA9300 Router, Quest 2 and Quest Pro with Air Link/Virtual Desktop

A

ArcAngel115

Participant

we tried honey in the v53 ptc thread, we got no flies. and how i'm responding is appropriate because i spent money period. just ask budlight if that's important. updates are good, choice is better and the right thing to do. using smalls words so you'll understand -.-

A

ArcAngel115

Participant

BTW, some people here have talked about sideloading v50 and it not working. That makes sense. BUT, in theory v51 should work because its android 12. I want to try it but I cant for the life of me find a v51 zip to give it a shot. I want v51 and dont care about new features, my PC can handle features with virtual desktop or ALXR/ALVR just give us the dam firmware that worked! We will do the rest