Forum Discussion
OVR seems to think my Quest is a Go since today. I don't understand why, or how to fix/revert this.
Game Engine: Unity 2019.1.2f1
Oculus Utilities v1.36.0
OVRPlugin v1.36.0
SDK v1.1.22.00
I've been working on a Quest experience for a while now, and when I arrived at the office this morning to test a new (completely unrelated) feature, my dev build loaded with only a single controller using the Oculus Go controller model, which I found weird. I added a debug.log statement and asked it what product the device was (using OVRPlugin.productName), and it prints "Oculus Go". I have full positional tracking, and if I press a button on the other controller, the system shifts which hand is active and deactivates the other. So, it somehow realizes it's a Quest, but it tells my system it's a Go anyways. ADB recognizes the device as a Quest, so it's something software related. I have tried restarting my Quest to see if that'll help, but it did not
Oculus Utilities v1.36.0
OVRPlugin v1.36.0
SDK v1.1.22.00
I've been working on a Quest experience for a while now, and when I arrived at the office this morning to test a new (completely unrelated) feature, my dev build loaded with only a single controller using the Oculus Go controller model, which I found weird. I added a debug.log statement and asked it what product the device was (using OVRPlugin.productName), and it prints "Oculus Go". I have full positional tracking, and if I press a button on the other controller, the system shifts which hand is active and deactivates the other. So, it somehow realizes it's a Quest, but it tells my system it's a Go anyways. ADB recognizes the device as a Quest, so it's something software related. I have tried restarting my Quest to see if that'll help, but it did not
12 Replies
- Hi did you sort this out, I have just come across the same issue
- I thought this had to do with the manifest xml document. Oculus > delete manifest then Oculus> create new manifest. This is all in the oculus drop down menu.
ZahCraft said:
I can confirm that this has solved the issue for us -
https://www.reddit.com/r/OculusQuest/comments/chjpu5/fix_for_sideloadedhomebrew_apps_and_games_with/?utm_source=share&utm_medium=ios_app
Same issue since today morning with my Unity builds!.. This fixed it!- I can confirm that this has solved the issue for us -
https://www.reddit.com/r/OculusQuest/comments/chjpu5/fix_for_sideloadedhomebrew_apps_and_games_with/?utm_source=share&utm_medium=ios_app - Quest:
Version 7.0.0.32.358.163419639
Runtime Version: 7.0.0.32.358.163419951
OS Version: user-333700.2680.0 - Exactly the same behavior here Alexander
- We have noticed a similar issue starting this morning: only one controller is being tracked and the other has it's model stuck on the floor (our 0,0,0 position in scene) until you press any button on it, then it switches states making the other tracked and the other stuck on the floor.
This is affecting all of our builds, newly built and those that was working before today.
Unity 2018.3.2f1
VRTK 3.3.1
Oculus Integration 1.36
Oculus Headset Runtime version 7.0.0.32.358.163419951
Oculus Headset version 7.0.0.32.358.163419639 (on Quest)
Oculus Headset version 333700.2680.0 (on connected phone) - I've reverted to an earlier build from GitHub that I know worked correctly a couple days ago, built it as a completely new project in Unity reconfigured the names and version numbers to make it a completely separate build for both my developer machine and the Quest, and it still shows up with a Go controller. I have no clue what to do about this
- This morning. Came to the office and all of our builds show the controllers as Oculus Go's ones.
They were working perfectly yesterday,
