zildac

Do you have Open XR Toolkit enabled? If so, it will not work with native OXR in DCS..ED issue. I had the same thing 2D mirror is fine, HMD is blank. Disable OXRTK and it will work albeit with double cursor as in my previous post.

In my testing, if you are using the native OXR now supported by DCS with a Varjo AERO you will have the double cursor/offset issue, and you can't use OXRTK. ED are enumerating the AERO incorrectly as having four screens, which breaks the cursor and OXRTK.

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.

The issue I and @mbucchiaare talking about is specifically related to Varjo headsets and the way in which the "new" OpenXR DCS enumerates them. But yes, there are likely issues affecting other headsets too, albeit for different reasons.

This is NOT just about XRNecksafer. As stated, the issue is the way DCS is enumerating the capabilities in relation to OpenXR for the given HMD. For the Varjo this results in OXRTK no longer working when attempting to use native DCS OXR. @BIGNEWY please do report @mbucchia findings to the team. Thankyou.

Unless you have an Aero and still wish to use OXRTK.

What headset?

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

No dice with a Varjo Aero. DCS native OXR launches fine but no HMD display unless OXRTK is disabled.

You don't "need" OXRTK, it just allows you to tweak some additional settings. It is very very useful, but there seems to be some mixed success running it with the newly introduced native OXR support in DCS (depending on Headset in use).

Hi, just to confirm, so there is no longer a need to swap the DLLs out? The app is using OpenXR natively out of the box with no modification? If so, that also means Reshade will no longer work, not an issue for me personally.

You may want to take a look at this mod, which generally improves the readability and optimises some of the textures in the Tomcat in VR. It may allow you to "up" the resolution without affecting your performance negatively. https://www.digitalcombatsimulator.com/en/files/3313661/

Yeah, it's easier than it first appears, and very satisfying

Legend!! Thankyou!

I recall seeing this listed as a known issue recently , but can't recall where exactly.

For whom?

Yup...looks like a simple to implement change. Shame. @BIGNEWY Can you nag the devs re this again please?

Only required in the Tomcat

Thanks for adding the kneeboards!!

Agreed. And hopefully the shimmering will also get fixed / significantly reduced as a result.

Welcome to our cult. Prepare for blood, sweat , tears and joy [emoji4]

Uncaged, Sensor select forward for mav not ins mode , then TDC depress?

As stated, this theory does the rounds every few months. These settimgs have zero impact on the VR experience. Any perceived improvement is placebo.

Care to share the details?

Yeah, they do appear to have taken a mogodon or two now. Since a few patches back.