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 using version 1.26 for the SDK (I haven't seen a newer version). Has anyone else seen this problem?Thanks,Bruce

Hi Bruce, the same problem here. I can't read the buttons anymore. The only thing that still works is "inputState.Touches". It shows what button is touched, but is super sensitive to touch.

Luckily, we had a computer that had not auto-upgraded. We copied the Oculus program files folders from that machine (1.26) to a machine that had auto-upgraded to 1.27 and the latter machine worked again. We had a critical demo to pull off and that was our work-around.

Please post if it does resolve the problem. I'm not well-versed in Oculus development and I'd appreciate knowing if this problem's been solved. Thanks.

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

Hello everyone,Our engineers are aware of the problem and are currently looking into a solution.In the meantime, a workround is to press the Oculus button to enter the Universal Menu, then press it again to return to the game. The buttons should work then.

Issue with version 1.27 and SDK v1.26 | Meta Community Forums

21 Replies

Dietrick89
Honored Guest
6 years ago
Docker provides an API for interacting with the Docker daemon (called the Docker Engine API), as well as SDKs for Go and Python. The SDKs allow you to build and scale Docker apps and solutions quickly and easily. If Go or Python don’t work for you, you can use the Docker Engine API directly.
STFSTF
Explorer
7 years ago
Hi, I just found this thread https://forums.oculusvr.com/developer/discussion/33329/has-oculus-removed-the-ability-to-run-c-console-exes

There is a comment to initialize the ovr with the "Invisible" flag which I just tried:
ovrInitParams initParams = { ovrInit_RequestVersion + ovrInit_Invisible, OVR_MINOR_VERSION, NULL, 0, 0 };
ovrResult result = ovr_Initialize(&initParams);

With this intitialization, the InputState structure (which contains all the buttons and trigger states) gets updated without any rendering. Maybe this helps you too.

Stefan
STFSTF
Explorer
7 years ago
Since I had used the controllers for emulating joysticks via FreePIE and vJoy before, I would like to have this functionality back to get the inputstate without rendering anything.
Anonymous
7 years ago
@imperativity
Could you tell me when the issue will be fixed? We have to reply to our customer. They wait for long time.
Anonymous
7 years ago
@imperativity
We have a important customer bothered by this. They don't believe Oculus makes this kind of serious mistake and can't fix it for long time. We have to fix it ASAP. If Unity works well in this version, I believe there are some workarounds we can use to avoid this issue. Could you provide it?
zakk102
Honored Guest
7 years ago
@imperativity

Thank you!! looking forward to it.
zakk102
Honored Guest
7 years ago
@imperativity

Can you provide any work around? The Unity version SDK works, so there must be a way to get the right value. Maybe it's not that clean code. Can you provide to us?
Cloudhopper
Honored Guest
7 years ago
@imperativity
@NinjaGaijin

The t.Controllers sample stops updating the trigger unless the function "API.ovr_CommitTextureSwapChain.Ptr" in file OVR_CAPIShim.c is called. In our application, the VR display is rendered in a separate application, so we need to read the state of the buttons and triggers without a graphics window associated with the application. This worked fine up until 1.27.
Cloudhopper
Honored Guest
7 years ago
@imperativity
@NinjaGaijin

The t.Controllers sample stops updating the trigger unless the function "API.ovr_CommitTextureSwapChain.Ptr" in file OVR_CAPIShim.c is called. In our application, the VR display is rendered in a separate application, so we need to read the state of the buttons and triggers without a graphics window associated with the application. This worked fine up until 1.27.
Cloudhopper
Honored Guest
7 years ago
@imperativity
@NinjaGaijin

The Sample software provided with the SDK "t.Controllers" illustrates reading buttons from the touch. I have modified this code to read the IndexTrigger, and it works. There are many examples (all of them) of applications that are able to utilize the trigger., yet this issue, if fundamental, would be a blocker for all applications utilizing the Touch controllers. The workaround of pressing the menu button twice does nothing to correct the errant behavior in our application. Why is this not shown as a know bug in the current SDK release? Is it really just a handful of folks that use the SDK interface to access the hardware? How does Unity or UE4 get the correct value?