How to "separate" Oculus GO button.one from primaryIndexTrigger — Oculus
Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.

How to "separate" Oculus GO button.one from primaryIndexTrigger

BreadlineBreadline Posts: 1
NerveGear
Hi!

In my Oculus GO app I'm creating a menu that pops up whenever button.one is pressed. The primaryIndexTrigger triggers events when I push in-game objects with it. I am able to open the menu with button.one easy, but the problem is that both of the buttons trigger events of game objects when pressed while pointing towards them. I would like to disable this from the button.one. I've been trying to study the OVRInput script but found nothing (I'm pretty new to this).

Comments

  • didiertidodidiertido Posts: 1
    NerveGear
    edited August 13
    Hey, sorry for necro-ing this but I'm having a similiar issue where the trigger on the Go controller is triggering OVRInput.RawButton.A too. Were you able to solve it? This may give me some clues on what to try. I also checked everything on OVRInput and OVRInputModule. (I know GO doesn't have A button. It's for Rift and Quest cross development)
Sign In or Register to comment.