Quest Link Performance Issue

No improvement with the PTC v85 version, same stuttering and freezing with Msfs 2024. 

Using link cable, which before last week, worked perfectly.

I've been using link for years without any real issues until the recent issue preventing us from going to desktop.  Now they fixed that issues but introduced this horrendous performance bug.  The two combined pushed me to switch to a wired Virtual Desktop setup and it's working so much better than it did on Link.  Still amazed it's been over a week since this bug was reported and there is no update but on the bright side I'm on Virtual Desktop now and I'm done forever with Link.

Have we any official updates from Meta on this and an ETA for a fix?  This blog is 8 days old now.  I know I'm sounding like a broken record asking for updates on an almost daily basis, but some customer service would be appreciated.  

till nothing? No updates, no communication... Meta shines as always with its inactivity!

Hello, Community Manager, are you asleep? It's been several months since your Link software stopped working properly. You've managed to butcher John Carmack's work; you're gods. I bought the Quest 3 on its release day in France, and everything worked perfectly. With each new update, it's been a disaster. A small example of your genius: we can still hear the Oculus Link home music that you removed on PC. The moral of the story: excellent hardware and catastrophic software. Hire Guy Godin, and for me, that's it for Meta headsets. You take us for fools, just look at the Link video you made. Goodbye.

I would like to know if there are any meta staff actually bothering to read this ? Why is there no apparent dedicated community staff who provide an interface to your paying customers ? why is it there are no updates when you announce known issues ? why total silence.  Also is manny.prerelease68​ still working for meta as they have stopped replying. I have a simple ask. when will the usb3 being reported as usb2 be fixed as reported by me at end of Oct in v81. Why is it you have released v83 and in process of releasing v85 when you have not fixed a huge issue in v81. Why aren't fundemental bugs being prioritised ?? I am told the issue i raised has been repeated internally by manny.prerelease68​. So how come 3 months later and heading rapidly into month 4 this is not resolved. I see others have the same issue. I am at the point of buying a Pimax Crystal cos i am so fed up with the constant bugs in software breaking pc link. How do i get a refund on the brick which is my quest3 ?

Do you guys realise how many people are using pc link ? How can it be after the last major outage a year ago that the testing and release process has not been tightened up to ensure no breaking changes. I know there is a myriad of PC hardware out there but getting a usb3 (connect via usb c, therefore it has to be usb3 ) to report as usb 2 is on a different level of inferior release testing.  

So can i get an update on my issue and when it will be fixed please. Can i even get an acknowledgement from someone in Meta they have even read this ? (I won't hold my breath). The community engagement for such a large enterprise company is shockingly bad. Or do we take it VR in meta is dead given the huge loss re Meta Horizon and infact there is no one left ?? 

In a business you would not get away with providing this lack of support, and clarity on progress after this long of notifying of an issue (I would expect daily updates from my IT dept).  I don't know how as paying customers we are less important somehow.  It's getting beyond ridiculous at this stage, almost 2 weeks later.  Can we have an update please?

UPDATE: We’re continuing to actively investigate the Quest Link performance issue and it remains a top priority. We're working diligently to identify a fix and will continue to keep the community updated on a resolution.

Just tested the encoding issue again and its still an issue as of Meta Horizon Link Version 85.0.0.223.552. Hopefully we will see a fix in the near future. 

Hello, you also investigated the programming of the AV1 codec, three years since the headset came out for your information, not a single byte of coding for this codec, well done once again.