Forum Discussion
OVRInputModule primary index trigger is unreliable.
Hi. I am having an issue wher the OVRInputModule is not working with me properly when I try to use the Primary Index Trigger. I have UI elements in my game including toggles and sliders. If I use the A button, I am able to interact with these widgets successfully. However, when I use the primary index trigger, it is hit or miss whether or not my input is registered.
For the "Joy Pad Click Button", I have "One" and "Primary Index Trigger" selected.
I did put some breakpoints in the function
virtual protected PointerEventData.FramePressState GetGazeButtonState()
and it does seem like the pressed and released variable are toggled on and off properly when I use the A button or the trigger on the right controller.
Any ideas?
Thanks,
John Lawrie
2 Replies
Replies have been turned off for this discussion
Here are some videos showing the behavior when it works and does not work as well as the settings.
Video showing when the trigger does not work but the A button does.
Video showing when the trigger works just the like A button works.
OVRInputModuleOVRInputModuleCollapsed
I'm having this exact issue a year later, specifically with the UI. It's borderline game breaking. I would greatly appreciate any suggestions on tackling this issue.
I've noticed the OVRInputModule is translating the OVR inputs into traditional Unity inputs, I'm not sure if this is standard anywhere else but I'm curious if that could be part of what's causing the problem. I'm not sure if this is an OVR API issue as much as it is an issue with that specific script, but I'd love a solution.
