Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

XRInteractionToolkit - InputHelper's Button definitions wrong/misleading. Bug?

Discussion in 'VR' started by snw, Mar 23, 2020.

  1. snw


    Mar 13, 2014

    I'm currently developing for Oculus Quest and almost lost my mind because I couldn't get XRController's "select" functionality to work.

    I just figured out that if I use "TriggerPressed" for the "Select Usage", the InputFeatureUsage-check in the InputHelpers class always returns false. If you look at the XRInputMappings (, there is no "TriggerPressed" definition. I assumed, that "TriggerPressed" would somehow map to CommonUsage.triggerButton, but it doesn't!

    Why does InputHelper introduce additional, hard-coded Button/ButtonInfo defintions instead of utilizing the definitions in the CommonUsage class? Isn't this very error prone?

    Last edited: Mar 23, 2020