Unity InputSystem differences between Oculus GOs
We own about 10 Oculus Go and develop an Application with Unity. We discovered that some are firing on different buttons and axis in Unity's InputSystem than others. This forced us to map everything to both configurations. How is this even possible? Go 1: Trigger: Axis 3: -1 (pressed state) Touchpad Axis 1 Axis 2 (inverted) Touchpad touch JoystickButton16 Touchpad press JoystickButton8 Go 2: Trigger: Axis 3: 1 (pressed state) Touchpad Axis 4 Axis 5 (inverted) Touchpad touch JoystickButton17 Touchpad press JoystickButton9
UI buttons only work after the first click
Is any one else experiencing this? My buttons do not work the first time you click them but once past the first click they work 100%. I'm building using the new updates for both Unity 2019.3.5f1 and Oculus 14.0 Any ideas as to what is causing this are welcome. ThanksOVRInput.Get problem with Button One always returning false (Unity 2019.3, OVRPlugin 1.44.0)
Hello, I'm using ALVR to connect Quest to my PC. I have a problem when developing anything with my Oculus Quest in Unity. I found that button One on each controller doesn't seem to work when playing in Unity. When I write: Debug.Log(OVRInput.Get(OVRInput.Button.Any)); it only prints true when pressing anything except button A and X on controllers. Do you guys have any fix that? Thanks