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