Help: Cross-Eye Effect with HP Reverb G2 and New WMR Oasis Driver in DCS

[Hafer]

Thanks to the new Oasis driver for WMR, I pulled my Reverb G2 out of the basement again. Started DCS – and what did I see? A severe misalignment of both images (cross-eye effect). The tool for WMR that used to run via autoexec.cfg no longer exists. What can I do?

[mbucchia]

Did you check the troubleshooting guide that leads to this known issue, and a likely workaround:

https://github.com/mbucchia/Oasis-Driver-for-Windows-Mixed-Reality/wiki/Known-Issues#cross-eye-feeling-double-vision-poor-eye-relief-issue

[Hafer]

Strange, my reply has disappeared. Here it is again.

Thanks for the fix – I’m familiar with it and have already tried it without success. The distortion sliders only shift the image vertically (up and down), not horizontally. Unfortunately, it doesn’t help.

In all other VR applications (IL-2, VTOL, etc.) I have a perfect image with the Oasis drivers. It seems to be a DCS-related issue…

 

[Tom Kazansky]

6 minutes ago, Hafer said:

Strange, my reply has disappeared. Here it is again.

I remember reading your answer here in a BSB2 thread:

 

[Hafer]

Oops, thanks – I deleted my answer there.

[aceviper]

My DCS in vr crashes on startup.

Works fine in 2d.

Worked before fine with good performance.

Steamvr and a couple of other games work fine on new oasis driver...but not DCS.

sighs...tired of trying to fix it

 

[sleighzy]

6 hours ago, aceviper said:

My DCS in vr crashes on startup.

Works fine in 2d.

Worked before fine with good performance.

Steamvr and a couple of other games work fine on new oasis driver...but not DCS.

sighs...tired of trying to fix it

 

Sounds like an unrelated problem so raise your own post. Attach your DCS log file after replicating the crash, might be something simple.

[mbucchia]

14 hours ago, Hafer said:

Strange, my reply has disappeared. Here it is again.

Thanks for the fix – I’m familiar with it and have already tried it without success. The distortion sliders only shift the image vertically (up and down), not horizontally. Unfortunately, it doesn’t help.

In all other VR applications (IL-2, VTOL, etc.) I have a perfect image with the Oasis drivers. It seems to be a DCS-related issue…

 

Oh I see. Yeah if the issue is only in DCS then that's not the distortion offset issue I pointed you too. 

Recommend you disable all OpenXR add-ons. I also don't know if DCS single-threaded still supports OpenVR? It might be a good test to try OpenVR instead of OpenXR. 

[sleighzy]

2 hours ago, mbucchia said:

I also don't know if DCS single-threaded still supports OpenVR? It might be a good test to try OpenVR instead of OpenXR. 

Single-threaded no longer exists anymore. Both the executables in bin and bin-mt are multithreaded and bin-mt will be removed in the future. It's all OpenXR these days.

[Hafer]

3 hours ago, mbucchia said:

Oh I see. Yeah if the issue is only in DCS then that's not the distortion offset issue I pointed you too. 

Recommend you disable all OpenXR add-ons. I also don't know if DCS single-threaded still supports OpenVR? It might be a good test to try OpenVR instead of OpenXR. 

Unfortunately, that didn't help. The farther away the objects are, the more I see them doubled.

[Hafer]

I found the fix! As a test, I disabled the autoexec.cfg - It contained the following values:

no_device_hotplug = true,
force_cross_eye_recovery_tool = true,
options.graphics.stereo_mode_use_shared_parser = true.

And now it works. Phew...

[sleighzy]

2 hours ago, Hafer said:

I found the fix! As a test, I disabled the autoexec.cfg - It contained the following values:

no_device_hotplug = true,
force_cross_eye_recovery_tool = true,
options.graphics.stereo_mode_use_shared_parser = true.

And now it works. Phew...

Just for curiosity sake in case this comes up for others, why did you have the "force_cross_eye_recovery_tool" entry in there in the first place? What does this do?

Edited October 7 by sleighzy

[Hafer]

On 10/7/2025 at 11:26 AM, sleighzy said:

Just for curiosity sake in case this comes up for others, why did you have the "force_cross_eye_recovery_tool" entry in there in the first place? What does this do?

That was probably a leftover from an old DCS version. I think back then you needed that entry to launch DCS’s own WMR VR alignment tool.