WillDaBeast509

With the latest update, 2.9.10.4160, the VR controllers no longer disappear as soon as you click on the VR tab in the settings, but they still don't do anything. My controller appears correctly with the hand, and makes the point and click animations, but the pointer does not appear and it cannot click or interact with anything. To be clear, this is what I experience before the VR tab fix anyway; even if I never clicked on VR tab my controller would never get the pointer to click anything. Using Vive controller with Index headset.

Exact same issue myself, but with a vive tracker puck. In fact, the hand appears when first launching the game (although can't interact with anything), but if I go to the VR settings tab, it disappears for the rest of the session. They claimed it was fixed specifically for Pimax controllers in this thread, but there's others still experiencing it. https://forum.dcs.world/topic/353257-handcontroller-not-working-in-version-296-quest-3/?do=getNewComment

I had the exact same issue as your original post, until I disabled the OpenXR Toolkit. The developer is no longer supporting it, and it looks like something from the last few months (be it steamvr, DCS, or otherwise) broke it. I gathered there's others that can still use it fine, but unfortunately I'm not sure it's an option for Index users anymore. There is a tool called quad-views-fovated by the same developer, which provides an even better version of the fovated rendering, but it broke the Steam motion smoothing. For now I've just resigned to not having the fovated rendering and CAS sharpening.

@BIGNEWY Just chiming in that I also still experience this issue, with a Valve Index headset and Vive controller. The hand initially renders and does the point/grip animation when clicking buttons on the controller, but cannot interact with anything, whether in the menus or in a cockpit. If I open the VR tab on the settings menu, the hand disappears until relaunching the game.

Previously DCS was recognized as a 'seated' app, so the room boundaries would not appear in VR. When running the MT version, this is not the case, and the boundaries will be displayed. As the MT version is a different executable I'm guessing it is not 'tagged' as a seated game like the standard ST version is.