Bug: incorrect depth data submitted via Oculus SDK

[actually_fred]

DCS submits an ovrLayerType_EyeFovDepth layer via ovr_SubmitFrame2 (this might be ovr_SubmitFrame or ovr_EndFrame in the source); the depth data in this layer appears to be incorrect.

The most visible impact of this is that the performance HUD options in the oculus debug tool do not work with DCS.

As I understand it, this will also have an impact on perceived performance and 'smoothness': accurate depth data is required for positional timewarp and for ASW 2.0; missing depth data should disable these techniques entirely, but it's not clear what incorrect depth data will do - at least, it seems unlikely they will work as intended.

Both OpenKneeboard and VRKneeboard work around this by removing the depth data; in OpenKneeboard's case, this is done by copying into an ovrLayerType_EyeFov.

Edited April 5, 2022 by actually_fred
clearer explanation of dropping the depth data

[edmuss]

Could this be linked to some of the reprojection issues with OC_ACC?  Jabbah had mentioned the artifacting on the menus was due to a missing depth buffer?