mbucchia QV bypassed with new DCS patch

[AhSoul]

Figured it might be worth me posting this here as well as the patch discussion thread where it might get lost.

I'm on the new patch with QV added to DCS settings, but it's not checked. However my mbucchia QV is being bypassed:

Quote

2024-09-30 21:12:53 +0100: XR_APILAYER_MBUCCHIA_quad_views_foveated layer (v1.1.3) is active
2024-09-30 21:12:53 +0100: Using layer: XR_APILAYER_MBUCCHIA_quad_views_foveated
2024-09-30 21:12:53 +0100: Using layer: XR_APILAYER_MBUCCHIA_toolkit
2024-09-30 21:12:53 +0100: Using layer: XR_APILAYER_FREDEMMOTT_OpenKneeboard
2024-09-30 21:12:53 +0100: Using layer: XR_APILAYER_VIRTUALDESKTOP_oculus_compatibility
2024-09-30 21:12:53 +0100: Requested extension: XR_KHR_D3D11_enable
2024-09-30 21:12:53 +0100: Requested extension: XR_KHR_visibility_mask
2024-09-30 21:12:53 +0100: Requested extension: XR_OCULUS_audio_device_guid
2024-09-30 21:12:53 +0100: Requested extension: XR_EXT_hand_tracking
2024-09-30 21:12:53 +0100: Requested extension: XR_HTCX_vive_tracker_interaction
2024-09-30 21:12:53 +0100: Requesting extension: XR_EXT_eye_gaze_interaction
2024-09-30 21:12:53 +0100: Requesting extension: XR_FB_eye_tracking_social
2024-09-30 21:12:53 +0100: Application: DCS (DCS.exe)
2024-09-30 21:12:53 +0100: XR_APILAYER_MBUCCHIA_quad_views_foveated layer will be bypassed

Do I need to do something to get it to not be bypassed?

Or do I need to tick the DCS option, which then uses mbucchia QV?

Edited Tuesday at 12:58 PM by AhSoul

[AhSoul]

Ahh ok so looks like you have to tick the option in DCS, and then it uses mbucchia QV. I'd thought it was a separate implementation and should leave the DCS one off.

Edited Monday at 08:44 PM by AhSoul

[Rosly]

Same here on Varjo 3.10.3.25 + mbucchia QV mod

@AhSoul Which HS and SW/FW version you use?

[sleighzy]

1 hour ago, Rosly said:

Same here on Varjo 3.10.3.25 + mbucchia QV mod

@AhSoul Which HS and SW/FW version you use?

Have you ticked the Quad Views box in DCS under the VR tab?

[PawlaczGMD]

completely unnecessary and undocumented change, wasted an hour of my time trying to find out why QV isn't working.

[Rufuz64]

I also wonder what the purpose of the button is. Having several on/off buttons for one and the same thing makes no sense to me.

[PawlaczGMD]

yeah, this is already turned off by disabling eye tracking in VR software, or disabling it in PimaxXr (for pimax). Now there is also a box in game options, all 3 have to be ticked for QV to work. 

[sleighzy]

17 minutes ago, Rufuz64 said:

I also wonder what the purpose of the button is. Having several on/off buttons for one and the same thing makes no sense to me.

It only does one thing. The button turns on or off Quad-Views if you currently have it installed, i.e. the Quad-Views-Foveated API layer that a number of us have had installed for a while now. More convenient than using Fred's OpenXR Layer GUI tool (for people not familiar with all the tooling available) as Quad-Views-Foveated itself does not have any ui for turning it on or off.

6 minutes ago, PawlaczGMD said:

or disabling it in PimaxXr (for pimax)

Quad-Views can be used by numerous headsets, not just Pimax, and those don't have a UI for turning it on or off.

Note that the PimaxXR option would have likely disabled the entire Quad-Views api layer on your system...the DCS setting doesn't, it just disables it in game.

Edited Tuesday at 07:47 AM by sleighzy

[Rufuz64]

vor 1 Minute schrieb sleighzy:

It only does one thing. The button turns on or off Quad-Views if you currently have it installed, i.e. the Quad-Views-Foveated API layer that a number of us have had installed for a while now. More convenient than using Fred's OpenXR Layer GUI tool (for people not familiar with all the tooling available) as Quad-Views-Foveated itself does not have any ui for turning it on or off.

Thank you for the clarification.

Strangely enough, the (undocumented) ‘Track the eye position’ button behaves differently. If I switch it off, the eye tracking on my Pimax still works...

[gonvise]

Are you telling me that if someone wants to enable mbucchia's QVFR, in addition to following the installation instructions on github, they will have to enable this option in DCS or it will not work? Or the first time the layer is installed this option will appear checked?

[Rufuz64]

You have to enable "Use Quad View", otherwise it will not work. Default is OFF

[Rosly]

11 hours ago, gonvise said:

Are you telling me that if someone wants to enable mbucchia's QVFR, in addition to following the installation instructions on github, they will have to enable this option in DCS or it will not work? Or the first time the layer is installed this option will appear checked?

Yes because QV has API where system is offering this capability and game confirm that it will use it.

[zildac]

12 hours ago, gonvise said:

Are you telling me that if someone wants to enable mbucchia's QVFR, in addition to following the installation instructions on github, they will have to enable this option in DCS or it will not work? Or the first time the layer is installed this option will appear checked?

Enable it in DCS, DCS presents it as supported...all good

[Doggo]

If I enable it, DCS crashes for me. It's warning me that I'm using OpenXR and OpenXR motion compensation.

 

It's quite confusing now.

[sleighzy]

1 hour ago, Doggo said:

If I enable it, DCS crashes for me. It's warning me that I'm using OpenXR and OpenXR motion compensation.

 

It's quite confusing now.

Do you mean OpenXR Toolkit and not "OpenXR"? Disable the OpenXR Toolkit and try again.

You can install this tool to see all the API layers and untick the boxes for OpenXR Toolkit and OpenXR Motion Compensation (just leave quad_views) and see if that resolves the issue.

https://github.com/fredemmott/OpenXR-API-Layers-GUI

Edited Tuesday at 11:47 PM by sleighzy

[Doggo]

2 hours ago, sleighzy said:

Do you mean OpenXR Toolkit and not "OpenXR"? Disable the OpenXR Toolkit and try again.

You can install this tool to see all the API layers and untick the boxes for OpenXR Toolkit and OpenXR Motion Compensation (just leave quad_views) and see if that resolves the issue.

https://github.com/fredemmott/OpenXR-API-Layers-GUI

 

Thanks! That tool is very useful.

I reinstalled quadviews and its working. I need the openxr support for my accessories.

 

See the screenshot message, anybody else have warnings like that?

Edited Wednesday at 02:05 AM by Doggo

[sleighzy]

@Doggo, yup that's normal, it's just listing your current API layers, you can ignore it. Probably only helpful for us if things don't work...but we'd need to see a DCS log file anyway. So yeah, if it's working then all good, enjoy.

[edudix]

So summarizing, we have to enable this to use the QUAD FOVEATED script? It does not mean that they have include it in their code?

[sleighzy]

20 minutes ago, edudix said:

So summarizing, we have to enable this to use the QUAD FOVEATED script? It does not mean that they have include it in their code?

Correct.

[edudix]

18 minutes ago, sleighzy said:

Correct.

Thanks man!

[Gunfreak]

I get far worse performance now then before the patch with my Pimax crystal. I have Quadview and eye tracking on in DCS, yet i still have like 10-15FPS less then before that patch, and this patch was supposed to include various performance improvements.  Looking at the VR capture I did in OBS, it seems my quad view settings from quad view companions aren't working. 

[gonvise]

52 minutes ago, Gunfreak said:

I get far worse performance now then before the patch with my Pimax crystal. I have Quadview and eye tracking on in DCS, yet i still have like 10-15FPS less then before that patch, and this patch was supposed to include various performance improvements.  Looking at the VR capture I did in OBS, it seems my quad view settings from quad view companions aren't working. 

1. Try disabling turbo mode in QV. The same thing happened to me and by deactivating it it worked again.

or

2. Try VRS Foveated Rendering (OpenXR Toolkit). It still works better for me than QVFR and it doesn't matter whether you activate the options within DCS or not. 

null

[Gideon312]

Interesting post on Reddit by mbucchia:

 

His suggestion is to uninstall OpenXR toolkit, a piece of software which isn’t maintained in the last two years.

Edited Friday at 04:06 AM by Gideon312

[PaulXKRS]

On 10/1/2024 at 8:47 AM, Rufuz64 said:

Thank you for the clarification.

Strangely enough, the (undocumented) ‘Track the eye position’ button behaves differently. If I switch it off, the eye tracking on my Pimax still works...

I recommend leaving the eye tracking in DCS off. Use the Pimax eye tracking. I found that enabling the eye tracking in DCS reduces image sharpness. 

5 hours ago, Gideon312 said:

Interesting post on Reddit by mbucchia:

 

His suggestion is to uninstall OpenXR toolkit, a piece of software which isn’t maintained in the last two years.

 

Yes, definitely. This was news to me as well, although if you used quad views before then I think you had to zero OXRTK  settings as part of the set up process. Every day is a school day in VR...

[PaulXKRS]

On 10/2/2024 at 2:51 AM, Doggo said:

Thanks! That tool is very useful.

I reinstalled quadviews and its working. I need the openxr support for my accessories.

 

See the screenshot message, anybody else have warnings like that?

 

Disable or uninstall OXRTK if you are using quad views and uncheck Track the eyes position in DCS if you have eye tracking enabling in your headset ( I use a Pimax Crystal).