Skip to main content
New Participant
May 14, 2018

Multiple OVRInput Requests Broken

There seems to be a serious input issue where a call to something like OVRInput.Get (OVRInput.Button.PrimaryIndexTrigger) in one script (anywhere in the script, doesn't have to be Update, LateUpdate, or whatever) makes it so that all calls for the exact same request anywhere else in the project fail. 

My test for reproducing is the GearVRControllerTest scene that comes with the Oculus SDK. I have an additional canvas set up so that OVRInput.Get (OVRInput.Button.PrimaryIndexTrigger) is being called from my own script on my own canvas and OVRInput.Get (OVRInput.Button.PrimaryIndexTrigger) is also being called by OVRGearVRControllerTest.cs. Only the input request in OVRGearVRControllerTest prints a result of "True". I'm testing with an Oculus Go and using Unity 2017.4, but I've seen this on and off for several months wondering why nothing has been done about it.
    This topic has been closed for replies.

    1 reply

    Meta Employee
    May 19, 2018
    Hi @Thickney,

    I have not been able to repro this on a Go with 2017.4.1f1 and the 1.25 Utils / OVRPlugin. I've created multiple canvases and 3d objects in the scene that react to OVRInput.Get(OVRInput.Button.PrimaryIndexTrigger) across multiple C# scripts and they all process the input as expected.

    Can you provide a minimal project.zip that demonstrates this? That would really help in getting to the bottom of this one.

    If there is an issue here we definitely want to fix it.

    Thanks!
    James