reported Meta Oculus Link v68 (PTC) bug with DCS

[YoYo]

It heppend to me Today!  

 

[YoYo]

I see that is topic about this issue already:

 

1 minute ago, mbucchia said:

There are many threads about this. Meta introduced a blatant bug in their update that breaks many of the OpenXR API layers out there (OpenXR Toolkit, QVFR, HTCC, OXRMC...). Then after I reported the issue to them, they ignored me.

Time to move to Virtual Desktop, where the developers care and properly look after their software.

Thanks for the clarification, damn that sucks since it Im using OpenXR Toolkit for literally everything related to VR :(.

[YoYo]

Btw. from Reddit:

Quote

EDIT: If someone really want to waste their time on this, you can remove the CHECK_XRCMD() wrapping that function call in dispatch.cpp. This effectively ignores the bogus return value from Meta's runtime and allows everything else to proceed (confirmed myself).

Where I can try it? Should I do it in OXRToolkit some file?

[diamond26]

On 7/24/2024 at 10:45 PM, slughead said:

I am in the process of switching to VD too for the very same reason.

I’ve tested again VD in preparation of the v68 bug and I have to say that visuals are up to the same level I have with Link. Using QuadViews ( I do use a WiFi 6 router dedicated to VD). If only SSW was in par to ASW and we had more options for image correction with VD as we have in OpenXR toolkit.

Edited July 30, 2024 by diamond26

[YoYo]

2 minutes ago, diamond26 said:

I’ve tested again VD in preparation of the v68 bug and I have to say that visuals are up to the same level I have with Link. Using QuadViews ( I do use a WiFi 6 router dedicated to VD). If only SSW was in par to ASW and we had more options for image correction with VD as we have in OpenXR toolkit.

 

So DCS and OXR Toolkit works with VD without any issue?

[BIGNEWY]

With the latest Meta update v68 a crash is happening when users have openXR toolkit enabled. 

Disable the tool and you should be ok. 

Not sure about the VD claim yet. 

thank you 

[mbucchia]

14 minutes ago, YoYo said:

So DCS and OXR Toolkit works with VD without any issue?

Yes, Virtual Desktop works fine with the OpenXR API layers. Virtual Desktop is made BY gamers FOR gamers.

[YoYo]

23 minutes ago, mbucchia said:

Yes, Virtual Desktop works fine with the OpenXR API layers. Virtual Desktop is made BY gamers FOR gamers.

Ok, thanks for the confirmation. VD has its drawbacks too. I tested it at a friend's and the texture compression was worse than on the Link cable, where I have the encode bitrate set to 960 but of course it also has many advantages too. 

Personally, for me, OXR Toolkit is not only a cool tool with many graphic options, but I also used the Turbo=on option, which works quite well for me, as well as taking screenshots directly from the goggles in native resolution and many more. For me "sharpness" was also a good option as well.

RiP OXR Toolkit :(.

I've checked now @BIGNEWY, disabling OXR Toolkit in the menu causes DCS to start in VR mode without a problem.

 

I haven't checked, but I suspect that other games stopped working along with OXR Toolkit too.

[YoYo]

Supposedly Reshade currently works with OXR, but I've only used OXR Toolkit, which was a lot nicer and better for me (when I was using Reshade some time ago it only worked on OpenVR).

 

Edited July 30, 2024 by YoYo

[Qcumber]

2 hours ago, YoYo said:

Btw. from Reddit:

Where I can try it? Should I do it in OXRToolkit some file?

I've given up on meta and am now using VD all the time. Quality and performance are very good. 

[BIGNEWY]

threads merged

[hannibal]

On 7/16/2024 at 5:39 AM, USSR_Rik said:

Do you use OpenXR environment?

Ah, I see in log --force_OpenXR

Guys, please attach your options.lua (I can't reproduce now on Q3, drivers 68.0.0.325.361 (68.0.0.325.361))

Did you sent automatically generated crash-reports into our base?

And finally: do you use OpenXR Toolkit when launched DCS?

i have uninstalled OpenXR toolkit and rebooted PC and it was still crashing for me

 

3 hours ago, YoYo said:

I've checked now @BIGNEWY, disabling OXR Toolkit in the menu causes DCS to start in VR mode without a problem.

this did not work for me either..

uninstalling openXR toolkit did not work.

dcs crashing no matter what on the v68 meta link software (and i am not on PTC beta channel)

Edited July 30, 2024 by hannibal

[hannibal]

4 hours ago, mbucchia said:

There are many threads about this. Meta introduced a blatant bug in their update that breaks many of the OpenXR API layers out there (OpenXR Toolkit, QVFR, HTCC, OXRMC...). Then after I reported the issue to them, they ignored me.

Time to move to Virtual Desktop, where the developers care and properly look after their software.

 

 

cant thank @mbucchia enough..

i dont want to call him marvel jesus.. but perhaps VR jesus!

[slughead]

1 hour ago, hannibal said:

uninstalling openXR toolkit did not work.

If you use any other OpenXR layers, such as QVFR or HTCC, they are also affected and likely to be causing the crash.

4 hours ago, YoYo said:

Personally, for me, OXR Toolkit is not only a cool tool with many graphic options, but I also used the Turbo=on option, which works quite well for me, as well as taking screenshots directly from the goggles in native resolution and many more. For me "sharpness" was also a good option as well.

You can use the OpenXR Toolkit and all the other OpenXR tools generated by mbucchia and Fred (HTCC, Openkneeboard) with VD.

[hannibal]

4 minutes ago, slughead said:

If you use any other OpenXR layers, such as QVFR or HTCC, they are also affected and likely to be causing the crash.

You can use the OpenXR Toolkit and all the other OpenXR tools generated by mbucchia and Fred (HTCC, Openkneeboard) with VD.

As quest pro user,  out of date on using VD and quadviews... until now I was fine with meta link software and openxr tool kit... I also have eye tracking turned off because I found it just drains battery quicker..

What do I have to do to get quest pro on quad view and VD up and running? I already have a wifi 7 router...

@slughead

[slughead]

Just now, hannibal said:

As quest pro user,  out of date on using VD and quadviews... until now I was fine with meta link software and openxr tool kit... I also have eye tracking turned off because I found it just drains battery quicker..

What do I have to do to get quest pro on quad view and VD up and running? I already have a wifi 7 router...

@slughead

Not a lot really. Just follow the instructions here:

• Discord | #start-here | Virtual Desktop

and here: 

Home · mbucchia/Quad-Views-Foveated Wiki · GitHub

 

However, I stopped using QVFR a while ago as I found it more of a CPU hog over cities and caused more ASW. I did try it again with VD, but I found it caused the clouds to become pixelated, so I turned it off once again.

[Qcumber]

5 hours ago, YoYo said:

, thanks for the confirmation. VD has its drawbacks too. I tested it at a friend's and the texture compression was worse than on the Link cable, where I have the encode bitrate set to 960 but of course it also has many advantages too. 

If VD is optimised the differences to link cable are very subtle in terms of quality and performance. It really depends on how good your wifi connection is and that your latencies are well controlled. 

[slughead]

There is a fixation on the bit rate. Yet, unless you compare with the same codec, the bit rate is somewhat meaningless as the newer codecs that VD can support, which Meta Link doesn't require a far lower bit rate to achieve the same compression. So far, I'm happy with the visuals and performance I get with VD. Each to their own though, but do consider codec when discussing bitrate. It is very much apples and pears otherwise.

[YoYo]

21 minutes ago, slughead said:

There is a fixation on the bit rate. Yet, unless you compare with the same codec, the bit rate is somewhat meaningless as the newer codecs that VD can support, which Meta Link doesn't require a far lower bit rate to achieve the same compression. So far, I'm happy with the visuals and performance I get with VD. Each to their own though, but do consider codec when discussing bitrate. It is very much apples and pears otherwise.

Did you buy new wifi router on this occasion? If yes, which one? Btw. I can be on the same time on cable but for charging?

Edited July 30, 2024 by YoYo

[slughead]

Just now, YoYo said:

Did you buy new wifi router on this occasion? If yes, which one?

 

Yes, as my current home's Wi-Fi is a mesh network. So, I purchased a dedicated router. It's a TP-Link BE9300. Overkill, overpriced. You can get much cheaper routers that will do the job well, I am told. The list provided by VD is here: • Discord | #general-support | Virtual Desktop

I also use these battery packs to keep my headset charged. I put them in a shirt or jeans pocket. Running without a cable is freedom.

INIU Power Bank, 20000mAh Fast Charging Portable Charger, 22.5W Powerbank with USB C Input & Output, Battery Pack PD3.0 QC4.0 for iPhone 15 14 13 12 11 Pro Max Mini Plus Samsung S22 S21 S20 iPad etc : Amazon.co.uk: Electronics & Photo

 

[gonvise]

Ok, we are clear that meta are the devil (not sarcasm) and that they don't give a sh*t about PCVR. On the other hand, we have VD that seems to listen, but no cable link, only wifi and, then, it must to stream the video from PC to googles. I have already posted in several posts the configuration that I have in cable link that gives me the quality and fluidity that I would like to achieve with VD. Taking into account that QVFR and toolkit work in VD, that supersampling can be done via PD in DCS or even with QVFR, I still have the problem that, no matter how many codecs I change in VD, in all of them I get that blurry scene that I don't get in cable link at 960. As @slughead says, ok, it's not a question of bitrate values, but of the combination of that bitrate and the corresponding codec, so...

Can someone tell me which code I should choose to get the least compression possible and get it close to what I see with cable link? It's just that no matter how much I want to use VD, and I do, I can't get rid of that blurry halo due to video compression.

Edited July 30, 2024 by gonvise

[slughead]

1 minute ago, gonvise said:

Ok, we are clear that meta are the devil (not sarcasm) and that they don't give a <profanity> about PCVR. On the other hand, we have VD that seems to listen, but no cable link, only wifi and, then, it must to stream the video from PC to googles. I have already posted in several posts the configuration that I have in cable link that gives me the quality and fluidity that I would like to achieve with VD. Taking into account that QVFR and toolkit work in VD, that supersampling can be done via PD in DCS or even with QVFR, I still have the problem that, no matter how many codecs I change in VD, in all of them I get that blurry scene that I don't get in cable link at 960. As @slughead says, ok, it's not a question of bitrate values, but of the combination of that bitrate and the corresponding codec, so...

Can someone tell me which code I should choose to get the least compression possible and get it close to what I see with cable link? It's just that no matter how much I want to use VD, and I do, I can't get rid of that blurry halo due to video compression.

I think you’d be best to ask this on the VD discord which is their support forum. Then you’ll get answers from the VD team.

[Werewolf_fs]

V68 official launch...

*EDIT nothing works  but A particular solution, intall folders v67, oculus_vclient, oculus_diagnostics and oculus-runtime, about installing v68. I will be able to link to the files as soon as the drive allows me to.

Edited July 30, 2024 by Werewolf_fs

[Qcumber]

35 minutes ago, gonvise said:

Taking into account that QVFR and toolkit work in VD, that supersampling can be done via PD in DCS or even with QVFR, I still have the problem that, no matter how many codecs I change in VD, in all of them I get that blurry scene that I don't get in cable link at 960.

I'm not sure why you are getting a blurry scene. What are your VD settings? Can you post a screenshot of your in game overlay so we can see your latencies etc? 

[hannibal]

2 hours ago, slughead said:

Yes, as my current home's Wi-Fi is a mesh network. So, I purchased a dedicated router. It's a TP-Link BE9300. Overkill, overpriced. You can get much cheaper routers that will do the job well, I am told. The list provided by VD is here: • Discord | #general-support | Virtual Desktop

I also use these battery packs to keep my headset charged. I put them in a shirt or jeans pocket. Running without a cable is freedom.

INIU Power Bank, 20000mAh Fast Charging Portable Charger, 22.5W Powerbank with USB C Input & Output, Battery Pack PD3.0 QC4.0 for iPhone 15 14 13 12 11 Pro Max Mini Plus Samsung S22 S21 S20 iPad etc : Amazon.co.uk: Electronics & Photo

 

The BE9300 is awesome. I use it with my quest 3 setup. But I use link cable for my quest pro