Got my Quest on day 1. A marvellous piece of VR tech that, for the first time, truly feels like a natural extension of our body. Oculus Go was like a comfortable gaze into VR with a limited controller; Quest finally puts us in there with immersive wireless touch controllers. That sense of freedom and easy accessibility is by far the best. A little on the heavy side, but it doesn’t bother me much. Another step closer to the Oasis! or SAO!
With all the new changes in publishing and little information on how does it affect the actual dev pipeline, the first thing for me was to test it for development. I did hang out with Vader a bit before this. It looks like the documentation on their website was copied and pasted directly from those of Oculus Go. Everything seems working until the Quest failed to show up under ADB Devices and the nightmare started. My computer was set up for Oculus GO and Rift development before, this shouldn’t be a problem. Boy, I was wrong.
I plugged my Oculus Go in and it showed up under the ADB Devices. Besides updating the driver that everyone suggested online, the official online documentation also suggests that I should swap the provided cable with a USB 3.0 one. The journey to identifying one in my tech pile and in Bestbuy and eventually on Amazon was a nightmare of its own. The new cable arrived the next day, Quest was still no show. It’s a good cable tho.
After a series of trials and errors, I still couldn’t get the Debug window to pop up in the Quest. The documentation about updating the driver on Oculus’s website wasn’t helpful, my Oculus Go ADB Driver 2.0 won’t install. No matter what I did, the driver description stayed the same in the Device Manager. Based on all the sideloading tutorials I watched online, maybe a fresh install is easier than upgrading from Oculus GO ADB driver 1.0. Yep, Driver Version 12.0.0.0!? I was losing my mind.
I noticed that my Quest appeared in the Device Manager as an “Oculus Composite ADB Interface” so I googled it. According to this page, I would need to change it an MTP USB Device which is what Driver 2.0 is for. If I have successfully installed the 2.0 driver, I am able to change it. Finally, something makes sense. Valid If statements are the foundation of sanity.
I followed this instruction above. At step 6, I didn’t see an “MTP USB Device” on the list, but besides “Oculus Composite ADB Interface”, there was an extra option called “USB ADB Device”. I went for it and it fucking worked!!! The debug window popped up in my Quest right after I switched to “USB ADB Device”. It also shows up under the ADB devices. I am now able to Build and Run in Unity (2018.4.0f1) like usual.
Oh, I am so grateful, thank you, Bill Gates!
