OpenXR Meta Quest2 Controller Profile Missing

When using the OpenXR Interface in ParaView using OpenVR with the Meta Quest 2 headset, my controllers are rendered with an actual Quest 2 controller model and they are able to perform the supported range of motions such as those mentioned here.

However, when using OpenXR with the Meta Quest 2 headset, the controllers are rendered as green wedges and they are not able to perform most of the supported range of motions. They are only able to move the camera around, move the data, and open the context menu (by pressing the B button on the right controller).

My understanding is that the binding of these controls is affected by code inside VTK and not ParaView itself. I looked at the VTK GitHub repository and found that the module for OpenVR contains a JSON file called vtk_openvr_binding_oculus_touch.json. However, I found no similar file in the module for OpenXR.

To confirm that this is, in fact, causing the issues, I tried to compile VTK from the source, however, I ran into issues here. Therefore, I would like to request someone else to take a look at this.

Indeed, this is correct!

We would be happy to see this fixed though, I will try to help you with compiling VTK, but you may also want to compile ParaView as well.

@LucasGandel and @Thomas_Galland may have more to say about the right way to add the bindings.