Forum Discussion
Issue with version 1.27 and SDK v1.26
Our systems auto-updated to version 1.27 last night. Calls to ovr_GetInputState() now produce values for m_inputState.IndexTrigger[0] that are always 0 no matter how the trigger is positioned. We're ...
I am running SDK V1.29 and that problem is still there.
My application has 2 VR modes, when I switch modes, I first get out of VR and get back in with a new ovr_Initialize and a new session (ovr_Create). To get the ovr_GetInputState to work again in the new session, just having the headset on is not enough. You then need to remove the headset and put it back on again! This make for awkward demos when I want to show both modes to a client...
The Oculus button work around does work, but after all, it is a work around... A real solution would be better.