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 ...
Florayne45 said:
Others who have been developing for Oculus devices- has this been a common occurrence in the past? Automated updates breaking your production environment? Definitely makes me hesitant to continue supporting this platform if it isn't going to be reliable.
Big time, we've had several important demo's derailed because of a last minute update forced on us.
When things work it's great but the uncertainty of when an update hits and what it might break is a big problem