Broken - Varjo Aero & Open XR Toolkit (using latest OB w/native OXR)

[zildac]

For those of us who use OXRTK with DCS and use a Varjo Aero, this setup will no longer work with the current (native OpenXR) 2.8 OB. This is due to the way ED have implemented OXR support for the Varjo. You can find more detailed info on the Varjo and OXRTK discord. At present, you can still use the "old" OpenComposite DLL swap route to maintain OXRTK compatibility with the latest OB. Not sure if this has been done for a specific reason or if it is just an oversight on EDs part.

The culprit is here:

[OXRTK] 2023-01-25 22:16:13 +0000: Runtime supports extension: XR_VARJO_quad_views

Edited January 26, 2023 by zildac

[dburne]

Interesting I was looking forward to giving it a try today, sounds like I should stay with Steam VR at least for now.

[zildac]

29 minutes ago, dburne said:

Interesting I was looking forward to giving it a try today, sounds like I should stay with Steam VR at least for now.

Aside from the OXRTK issue, the native "new" OpenXR support also has the silly double cursor thing back again, so personally I would avoid. You can still use the OpenComposite OpenXR route, but I know you weren't a fan of that approach. As an aside, the native OXR support is significantly less performant than using the OpenComposiote approach...who knows.

Edited January 26, 2023 by zildac

[dburne]

12 minutes ago, zildac said:

Aside from the OXRTK issue, the native "new" OpenXR support also has the silly double cursor thing back again, so personally I would avoid. You can still use the OpenComposite OpenXR route, but I know you weren't a fan of that approach. As an aside, the native OXR support is significantly less performant than using the OpenComposiote approach...who knows.

 

 

Ok thanks for the feedback!

[Gordy]

agreed - I get double cursors with the native openxr support, and performance around 71+ fps.

The same configuration with the drop-in .dll replacement that I've been using for the last year has me at 84-90 fps, no double cursor.   So I'd stick with the drop-in .dll and openxr for now.

[zildac]

Just to update here, the performance drop using native DCS OXR (all other issues aside) versus using the "old" OpenComposite method appears to be the fact that DCS is still recognising the Aero as having four displays, it's rendering all four but displaying only two, therefore more work=less performance.

Edited January 26, 2023 by zildac

[ORboarder]

Just a heads up, turbo mode (which was awesome) is also currently crashing the sim when enabled.  
please fix this ED.  Please learn to make correct patch notes.  I spent hours trying to find out why my game was crashing.  So embarrassing and disrespectful to your users