Skip to main content
New Participant
August 10, 2019

Oculus Integration 1.39 Only one controller active at a time

Since the update, my biggest problem is that while I could manipulate the 2 controllers simultaneously back then, now, only one of them is tracked at a time, the tracking switch between each controller when I press any button and the other is reset at Vector3.zero local position & Quaternion.identity. I get the controller position values from
OVRInput.GetLocalControllerPosition(OVRInput.Controller.LTouch)
and
OVRInput.GetLocalControllerPosition(OVRInput.Controller.RTouch)
Of course these two lines returned the right position value back then but now only one of them return a tracked value at a time while the other one seems "disabled".
This topic has been closed for replies.

3 replies

Participant
August 12, 2019
Was having this exact same issue on Oculus Quest, Unity 2018.4 LTS, but following this seemed to help: https://forums.oculusvr.com/developer/discussion/79152/project-issues-with-latest-firmware-integration-update#latest

Also, make sure on your OVRManager Script your target device is set to Quest instead of Go.

However, now my app doesn't auto start on the Quest once it's built anymore. I fixed that with this solution: https://forums.oculusvr.com/developer/discussion/48645/oculussampleframeworkproject-1-5-1-wont-launch
Participant
August 12, 2019
Was having this exact same issue on Oculus Quest, Unity 2018.4 LTS, but following this seemed to help: https://forums.oculusvr.com/developer/discussion/79152/project-issues-with-latest-firmware-integration-update#latest

However, now my app doesn't auto start on the Quest once it's built, but if that happens you should be able to get on the oculus and start it through the Unknown Sources. Hopefully that he
Participant
August 12, 2019
Was having this exact same issue on Oculus Quest, Unity 2018.4 LTS, but following this seemed to help: https://forums.oculusvr.com/developer/discussion/79152/project-issues-with-latest-firmware-integration-update#latest

However, now my app doesn't auto start on the Quest once it's built, but if that happens you should be able to get on the oculus and start it through the Unknown Sources. Hopefully that helps.