Did Meta Link Update Break DCS again?

[Recluse]

So there was a LINK update today (probably PTC as I hadn't turned that off).

Oddly the version numbering system is totally changed: Current version is:  201.0.0.73.547 (201.0.0.73.547)  while the Previous PTC version that "fixed" the problem was 85.0.0.223.552 (85.0.0.223.552).

WIth this new update, DCS crashes on startup again with this log entry:

Quote

2026-02-11 02:57:41.820 INFO    SOUNDER (26328): Loaded 7 sounders.
2026-02-11 02:58:06.099 INFO    VISUALIZER (Main): [21:58:06.591][Info   ] OpenXR: Environment Access Check timeout is: 25034 milliseconds
2026-02-11 02:58:06.099 ERROR   VISUALIZER (Main): OpenXR failure runtime is not available
    Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:433
2026-02-11 02:58:06.100 ERROR   VISUALIZER (Main): OpenXR exception: runtime is not available
    Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:433

I have been using Virtual Desktop, but I did make sure to switch the OPENXR Runtime to the LINK application for testing purposes.

Now it LOOKS like my Headset (QUEST 2) is also downloading an Update now, so maybe there was a mismatch between the new LINK version and the Headset OS. There was an odd lag time when the LINK connected, but it seemed to connect OK and gave me the Desktop view.

Maybe a false alarm which will be resolved if there is a headset software mismatch, but I wondered if anyone else was seeing this.

Virtual Desktop continues to work great, and I only tested the new LINK software to see if they improved anything with the Wired Connection (since the previous few updates gave me really bad performance). 

Sometimes I got a crash with error message, other times, DCS just timed out and shut itself down with no error. When I got an actual crash, I  looked at the Crash Log and that old error seems to be back as well:

Quote

DCS/2.9.24.19998 (x86_64; MT; Windows NT 10.0.19045)
C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRTImpl64_1.dll
# C0000005 ACCESS_VIOLATION at 00007ffa5821766c 02:0004766C

EDIT: No headset  update. 

Edited February 11 by Recluse

[sleighzy]

Correct. Everybody on the PTC should not update. Turn off auto-updates. Same (similar) issue as last time.

Runtime Version: Instance RuntimeName=Oculus RuntimeVersion=1.201.0 Same trace as before:

2026-02-11 02:06:44.905 INFO EDCORE (24632): C:\Program Files\Meta Horizon\Support\oculus-runtime\LibOVRRTImpl64_1.dll
2026-02-11 02:06:44.905 INFO EDCORE (24632): # C0000005 ACCESS_VIOLATION at 00007ffef398766c02:0004766C
2026-02-11 02:06:44.905 INFO EDCORE (24632): SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'redacted'
2026-02-11 02:06:44.905 INFO EDCORE (24632): OS-Version: 10.0.26200 () 0x300-0x1
2026-02-11 02:06:44.906 INFO EDCORE (24632): 0x000000000004766c (LibOVRRTImpl64_1): ovr_ReleaseHapticsClip + 0x2E43C

 

See previous v85 PTC issue I posted. Looks like back again.

 

Edited February 11 by sleighzy

[Steel Jaw]

I'm f-ing done with meta and its constant unnecessary updates breaking things...now using virtual desktop...best move ever.

[Cgjunk2]

1 hour ago, Steel Jaw said:

I'm f-ing done with meta and its constant unnecessary updates breaking things...now using virtual desktop...best move ever.

I’d love to be done with Zuck and his meta.   At this point, all his updates for link seem to be some sort of passive aggressive move to abandon PC-VR support.   With him firing a bunch of his VR staff, seems the writing is on the wall, he’s lost interest.

I’ll be seriously considering the Steam Frame when it comes out.   In the meantime I’d love to move over to Virtual Desktop, but don’t wanna mess with buying and setting up another router to work with it.   Does anyone know if VD can run via the USB cable instead of wirelessly?   

[sleighzy]

12 minutes ago, Cgjunk2 said:

I’d love to be done with Zuck and his meta.   At this point, all his updates for link seem to be some sort of passive aggressive move to abandon PC-VR support.   With him firing a bunch of his VR staff, seems the writing is on the wall, he’s lost interest.

I’ll be seriously considering the Steam Frame when it comes out.   In the meantime I’d love to move over to Virtual Desktop, but don’t wanna mess with buying and setting up another router to work with it.   Does anyone know if VD can run via the USB cable instead of wirelessly?   

Couple of options. One widely used is a USB-C to Ethernet adapter, not officially supported by VD but they have a section on their Discord server for it. The other is pure USB-C however may not be as good (listed as one of the cool tools for VD https://github.com/Kuijen/RT-RP). 

[Recluse]

Was going to give RT-RP a try. For Windows, is the Java version (Gnirehtet) preferred? The Gnirehtet readme says:

 

Quote

Use the Rust implementation. The native binary consumes less CPU and memory, and does not require a Java runtime environment.

But RT-RP seems to prefer JAVA though both implementations are present.

 

I got back to the working version of LINK, but, as before, event though DCS runs, it is a stuttery low frame rate mess.  VD is working very well, but trying to make use of the cable for a bit better bandwidth.  When LINK was working well, the performance was still not as good as VD, but the visual clarity WAS a bit better. Trying to get the best of both worlds!

 

EDIT: I just tried the RUST version. Seemed to work well!!  VD reported a higher connection bandwidth and I could crank up the bitrate a bit. More experimentation needed, but a good start.

Edited February 13 by Recluse

[Cgjunk2]

9 hours ago, sleighzy said:

Couple of options. One widely used is a USB-C to Ethernet adapter, not officially supported by VD but they have a section on their Discord server for it. The other is pure USB-C however may not be as good (listed as one of the cool tools for VD https://github.com/Kuijen/RT-RP). 

Does the RT-RP tool require any new/different hardware, or does it just run over the same USB3 cable connected from headset to computer?

 

2 hours ago, Recluse said:

Was going to give RT-RP a try. For Windows, is the Java version (Gnirehtet) preferred? The Gnirehtet readme says:

 

But RT-RP seems to prefer JAVA though both implementations are present.

 

I got back to the working version of LINK, but, as before, event though DCS runs, it is a stuttery low frame rate mess.  VD is working very well, but trying to make use of the cable for a bit better bandwidth.  When LINK was working well, the performance was still not as good as VD, but the visual clarity WAS a bit better. Trying to get the best of both worlds!

 

EDIT: I just tried the RUST version. Seemed to work well!!  VD reported a higher connection bandwidth and I could crank up the bitrate a bit. More experimentation needed, but a good start.

I’d love to hear updates on how it performs for you as you experiment. 

[Recluse]

3 hours ago, Cgjunk2 said:

Does the RT-RP tool require any new/different hardware, or does it just run over the same USB3 cable connected from headset to computer?

 

I’d love to hear updates on how it performs for you as you experiment. 

No other hardware! Same cable.  I originally thought you had to download Gnirehet as well but it is included in the RT-RP.

 

- I installed the RT-RP RUST.

- I connected my headset with the LINK USB3 cable (I knew it connected OK because the Meta LINK PC was shown as ready, but I did not launch it.

- I ran the RT-RP start CMD file and got the message that RT started successfully and also the VD Streamer started.

- I eventually saw a Gnirehtet prompt in the headset and accepted the connection.

- Then I remembered to turn off WiFI on the Headset.

- I started VD in the Headset, and despite an error that said it was on a different network, it connected up and showed me the desktop.

- Started DCS and was in VR.

- VD with WiFi usually shows 5 GHz 866 Mbps connection.  With the cable, it showed 5 GHz 1200 Mbps, but I don't know if that is accurate as VD expects WIFi.

- VD was set to automatically set bitrate, and I thought it was a little low, (as usual with WiFi, it sets itself to ~68, so I exited, bumped it up to 84, and restarted DCS.)  Definitely saw some visual improvements!! and no loss of frames or additional lag.

- Maintained a steady 80 fps (which I also see with WiFi, but sometimes it fluctuates, especially in MP. I only did a quick check in a few Instant Action Free Flights.  I will say that whenever I fly the Apache it drops frame rate. With the Cable/RT-RP, though it only dropped to ~70 FPS, whereas it would drop down to 50-60 on WiFi.  N of 1 so not really scientific at this point!

 

Tonight is our usual MP session, so that will be a big test. Typically, though VD gets me steady 80 FPS SP over WiFi, it usually drops quite a bit during a MP session especially when Changing Slots or going to the F10 map.

 

EDIT:  I see a lot of errors, but my connection and VR session was never interrupted.

 

Probably these are game server connections, not Headset/PC connection.

null

Edited February 13 by Recluse

[Recluse]

So I got a notification that there is a LINK Update (Stable not PTC) but I am loath to do the update in case in it the same PTC version that caused issues.  LOL, not that I am using Meta Link any more for DCS, but I would still rather not have a broken version.

 

Anyone do the update and can post the version number?

The broken PTC version was 201.0.0.73.547 (201.0.0.73.547)

[Tea-Pig]

For anyone fed up with Meta updates breaking things, you can run the Meta link app isolated from the web as described here:

https://forums.x-plane.org/forums/topic/342175-how-i-fixed-version-83-meta-horizon-bug-that-prevented-connecting-to-headset/

You can tell if it's working by the home screen which will just be blank grey.

If you keep the wifi off on the headset then it won't update either.

[Rocky49]

My Quest 3 is useless in DCS again.  I can start DCS but in about 20 minutes the headset freezes and I can't do anything.  My monitor shows my head movements but have to shut down the Quest and restart.  If I start DCS without my Quest it starts and runs perfectly.  Also if I use my Quest in other games, no issue.

[fab.13]

Hello,

I suggest to block automatic update when your meta link work well
very easy to block
 

 

[carbolicus]

I need a new VR headset and was going to get a Meta Quest 3, but this thread seems to highlight regular problems with Meta software which stops it working.

Can you use the Quest 3 without Meta?  I get the impression that Virtual Desktop means you can avoid Meta, and it works well - is this what most people use?

I’m aware that the Quest 3 is a very popular headset for DCS users, so does that mean that most people use VD and not Meta?

I’m assuming that those DCS users who go with Meta are doing so because they also want to use Meta stand-alone games - not a problem for me who would only use it for flight sims.

[Phantom711]

@carbolicus

I would argue, that the reported problems are kinda exaggerated. I‘ve used a QuestPro for the past two years and the only issue there was with Meta Link was about two years ago. It took Meta about 2 weeks to solve the problems. If you want to avoid problems, don‘t opt into PTC, which is Metas beta test program.

yes, Virtual Desktop is a valid alternativ, but requires a dedicated router.

Steam Link is another alternative.

vor einer Stunde schrieb carbolicus:

I’m assuming that those DCS users who go with Meta are doing so because they also want to use Meta stand-alone games - not a problem for me who would only use it for flight sims.

If someone wants to play standalone games then he/she won‘t need Meta Link since it is meant specifically for PCVR.

Also, it‘s not like you have to make a choice and then you‘re stuck with it…you can switch between the different options relatively quickly.

I would suggest to start of with Meta Link and then work your way from there.

Edited February 26 by Phantom711

[Recluse]

24 minutes ago, Phantom711 said:

@carbolicus

I would argue, that the reported problems are kinda exaggerated. I‘ve used a QuestPro for the past two years and the only issue there was with Meta Link was about two years ago. It took Meta about 2 weeks to solve the problems. If you want to avoid problems, don‘t opt into PTC, which is Metas beta test program.

yes, Virtual Desktop is a valid alternativ, but requires a dedicated router.

Steam Link is another alternative.

If someone wants to play standalone games then he/she won‘t need Meta Link since it is meant specifically for PCVR.

Also, it‘s not like you have to make a choice and then you‘re stuck with it…you can switch between the different options relatively quickly.

I would suggest to start of with Meta Link and then work your way from there.

@Phantom711

OMG I spent YEARS ignoring all the Virtual Desktop fanbois and slugging it out with Meta LINK until the last few updates made it impossible.  One of the reasons I avoided VD was because I DO NOT HAVE A DEDICATED ROUTER and with AIRLINK, it always complained that the connection wasn't good enough (but it worked pretty well...until it didn't). I got a DLINK AIRBRIDGE (when they were supported and the WIRED LINK was problematic) and it worked GREAT....then they stopped supporting it, and, for a time Wired LINK was stable and working well. Then it wasn't.  I bought VD, and it worked great OUT OF THE GATE.  Dedicated ROUTER: MYTH.   LINK saying my 5G connection wasn't good enough: LIES.

Everyone's setup is a little different, but I have to say that FOR ME (and others who have chimed in on the various threads) the problems with the  last several LINK updates were anything but exaggerated, especially for DCS.

Now I use VD with and without the RT-RP reverse tethering so I can still use the LINK CABLE for slightly better bandwidth. Also use STEAM LINK for some games and I am very very happy to NEVER have to use The META QUEST LINK since every update seems to break something or other. 

 

- My machine is hard wired into the dual band Router (which serves the entire household) via house Ethernet cable and a switch

- My headset (QUEST2)  is connected to the WiFi via the 5G band

- LINK Cable connected from Headset to a Powered USB 3.0 HUB for both power and data if using RT-RP

Edited February 26 by Recluse

[Phantom711]

@Recluse 
I need to add: When I was referring to Meta Link, I was talking about cabled link.

[Recluse]

4 hours ago, Phantom711 said:

@Recluse 
I need to add: When I was referring to Meta Link, I was talking about cabled link.

@Phantom711

Thanks for that!!  I went through a long period where my LINK cable just would not work, or would frequently disconnect. I tried several cables to no avail, until Auto-magically, an update fixed it, and I sweated making any further updates lest it BREAK again.

 

To add to the mix, I noticed my Quest headset software was recently updated to 2.1.1034 Build 5210688.3680.150

I never updated my LINK software, so I am still running 85.0.0.223.552 (85.0.0.223.552) (the last "good-ish" version before the DCS breaking one which also had a name change like the Quest software.)  Now it seems like it is working relatively well with DCS. Not as well as VD, though, but nice to have another backup plan.

Can somebody report on what the CURRENT Stable LINK version is and if it is working in DCS with the current QUEST version? LINK stopped asking me to update, so wondering if there is still a new one out there.

Edited February 27 by Recluse

[Steel Jaw]

On 2/13/2026 at 12:23 PM, Recluse said:

No other hardware! Same cable.  I originally thought you had to download Gnirehet as well but it is included in the RT-RP.

 

- I installed the RT-RP RUST.

- I connected my headset with the LINK USB3 cable (I knew it connected OK because the Meta LINK PC was shown as ready, but I did not launch it.

- I ran the RT-RP start CMD file and got the message that RT started successfully and also the VD Streamer started.

- I eventually saw a Gnirehtet prompt in the headset and accepted the connection.

- Then I remembered to turn off WiFI on the Headset.

- I started VD in the Headset, and despite an error that said it was on a different network, it connected up and showed me the desktop.

- Started DCS and was in VR.

- VD with WiFi usually shows 5 GHz 866 Mbps connection.  With the cable, it showed 5 GHz 1200 Mbps, but I don't know if that is accurate as VD expects WIFi.

- VD was set to automatically set bitrate, and I thought it was a little low, (as usual with WiFi, it sets itself to ~68, so I exited, bumped it up to 84, and restarted DCS.)  Definitely saw some visual improvements!! and no loss of frames or additional lag.

- Maintained a steady 80 fps (which I also see with WiFi, but sometimes it fluctuates, especially in MP. I only did a quick check in a few Instant Action Free Flights.  I will say that whenever I fly the Apache it drops frame rate. With the Cable/RT-RP, though it only dropped to ~70 FPS, whereas it would drop down to 50-60 on WiFi.  N of 1 so not really scientific at this point!

 

Tonight is our usual MP session, so that will be a big test. Typically, though VD gets me steady 80 FPS SP over WiFi, it usually drops quite a bit during a MP session especially when Changing Slots or going to the F10 map.

 

EDIT:  I see a lot of errors, but my connection and VR session was never interrupted.

 

Probably these are game server connections, not Headset/PC connection.

null

You connected the headset via usb3 link to what?  Your pc or your router?

[Recluse]

1 hour ago, Steel Jaw said:

You connected the headset via usb3 link to what?  Your pc or your router?

Sorry, USB3 cable is connected from headset to PC (via a powered USB HUB). HUB is not necessary, I just find it gives me better charging (though SLIGHTLY less bandwidth) than connected directly to USB3 on the motherboard.

Edited February 27 by Recluse

[Smokin1469]

@carbolicusFWIW, I have a quest 3 and I use the Link cable connected to my machine.  Granted, I've only been on DCS for about 3 years, but only once did a Link update break DCS.  That was a couple months ago and Meta sent out an update fixing the issue in about 2 days.  I've been very happy thus far with my Q3 and Meta Link.  

[Tea-Pig]

On 2/26/2026 at 8:42 PM, carbolicus said:

I need a new VR headset and was going to get a Meta Quest 3, but this thread seems to highlight regular problems with Meta software which stops it working.

Can you use the Quest 3 without Meta?  I get the impression that Virtual Desktop means you can avoid Meta, and it works well - is this what most people use?

I’m aware that the Quest 3 is a very popular headset for DCS users, so does that mean that most people use VD and not Meta?

I’m assuming that those DCS users who go with Meta are doing so because they also want to use Meta stand-alone games - not a problem for me who would only use it for flight sims.

I've had a Quest Pro for a couple of years and it's been pretty reliable. As @Smokin1469 says, there was one Meta update that broke DCS a while back, but there was a workaround and Meta released a patch within a couple of weeks. Other than that I've had no real problems although it is a shame that these headsets are so loaded with Meta bloat and spyware. I keep mine isolated from the internet.

Most people seem to say that Virtual Desktop is the best PCVR solution, but it's never worked well for me so I use the Meta link cable and it seems fine, except I can't get eye tracking through it. So no DFR for me, but my system seems beefy enough to cope without it.

With that said, if were in the market for a new headset I would go for a proper PCVR one with a Displayport connector. My old Reverb was so easy to set up and no link issues.

[Phantom711]

vor 12 Stunden schrieb Tea-Pig:

except I can't get eye tracking through it.

That should definitely work though. I used cabled link with DFR via QuadViews. You will still benefit from it, even with a 4090. 

I mean at the end, eye-tracking is the edge that the QP has over the Q3.

In order to not derail the thread, PM me, if you want to give it a try.

[Qcumber]

On 2/27/2026 at 9:26 PM, Tea-Pig said:

Most people seem to say that Virtual Desktop is the best PCVR solution, but it's never worked well for me so I use the Meta link cable and it seems fine, except I can't get eye tracking through it. So no DFR for me, but my system seems beefy enough to cope without it.

Steam VR is the best option I have found recently. The latest version (last couple of months) gives me better quality and performance over Meta and VD.

In terms of eye tracking make sure you follow all the setup instructions as per https://github.com/mbucchia/Quad-Views-Foveated/wiki

[Cgjunk2]

On 2/17/2026 at 2:05 PM, Tea-Pig said:

For anyone fed up with Meta updates breaking things, you can run the Meta link app isolated from the web as described here:

https://forums.x-plane.org/forums/topic/342175-how-i-fixed-version-83-meta-horizon-bug-that-prevented-connecting-to-headset/

You can tell if it's working by the home screen which will just be blank grey.

If you keep the wifi off on the headset then it won't update either.

I tried this to avoid the trauma of any more updates, but it didn’t work.   Meta Link is asking to be updates today.  Has anyone else gotten this to work?

[Recluse]

11 hours ago, Cgjunk2 said:

I tried this to avoid the trauma of any more updates, but it didn’t work.   Meta Link is asking to be updates today.  Has anyone else gotten this to work?

LOL I have been trying to get someone to tell me what the latest STABLE update is and if if fixes anything....I have been snoozing the update for days.  The old LINK version 85.0.0.223.552 (85.0.0.223.552) paired with the latest Headset version 2.1.1034 Build 5210688.3680.150 seems to work as well as LINK ever worked.