Search Unity

Resolved Primary trigger of Oculus Go/Quest mapped to button One

Discussion in 'VR' started by jeppe79, Apr 1, 2021.

  1. jeppe79

    jeppe79

    Joined:
    Sep 17, 2019
    Posts:
    76
    Hi,

    I am converting a project from Oculus Go to Quest 2.
    In the Go the primary trigger (Index finger) is used for navigating menus.
    After updating from Unity 2018 to 2020.3.2f1, Oculus integration, XR and so on... and I load the project in Oculus Quest 2.
    Then the primary trigger does nothing, but I can navigate with button A instead.

    How can I correct this?
     
    jeppe79, Apr 1, 2021
    #1

  2. jeppe79

    jeppe79

    Joined:
    Sep 17, 2019
    Posts:
    76
    For future reference, I solved this by going into OVRInputModule of the Eventsystem gameobject in the UIHelper prefab from Oculus.
    There you can select which button you interact with.
    The option is currently named: Joy pad Click Button.
    I also noticed the primary index trigger is on the left controller and secondary index trigger is on the right controller.

    Hope it helps someone.
     
    jeppe79, Apr 3, 2021
    #2