I see now that the release notes state that “VTK’s OpenVR’s input model has been updated to be action-based and supports binding customization within the OpenVR user interface.” - which sounds like its related to my problem. Not sure what I need to do about this, though…