koobas.hobune.stream
Oculus Controller Input only partially working?
Hi gang! I've been having a bit of a strange problem for a while. Developing for the Quest on Unity 2018.2. I've tried updating to 2018.3 to see if the version was to blame but that didn't appear to work.
As I create OVR Inputs, I'm noticing strange behavior that happens across all dev team's machines, both in Editor testing and on Quest devices: OVR Input works for some buttons but not all.
Analog sticks on both Oculus controllers work, as do Button Two and Button Four. However, Button 1 and Button 3 do not work. For example, if I have the code:
if (OVRInput.GetDown(OVRInput.Button.One))
Debug.Log("One hit.");
if (OVRInput.GetDown(OVRInput.Button.Two))
Debug.Log("Two hit.");
if (OVRInput.GetDown(OVRInput.Button.Three))
Debug.Log("Three hit.");
if (OVRInput.GetDown(OVRInput.Button.Four))
Debug.Log("Four hit.");
... then I'll only see "Two Hit." and "Four Hit".
I would assume this has something to do with OVR thinking I'm using different controllers, like the GearVR controller, even though I'm using the normal Oculus one.
I've read some bizarre posts online saying that they resolved it by pressing the home button on the Oculus controller, or by editing the Android Manifest. Neither of these solutions seemed to do the trick for me.
I should note that if I use the normal Input system...
Input.Get$$anonymous$$eyDown("joystick button 0")
It works. So, what could be going on with my OVR Inputs? I'd prefer to use that system over the Input stuff.
I have the same issue. Have you been able to solve it? @justinpatterson
I have the same issue. Have you been able to solve it? @justinpatterson
Yes - I had to update my Oculus plugin and add a bit of code if running in editor.
