Solved
Oculus Integration asset necessary?
Hi there :)
I've developed VR applications professionally for B2B in Unity for a couple of years now - Gear VR, Vive, and Rift. It's my first time developing for the Oculus Quest, amazing device. I've easily and successfully been able to build directly to the device, and already made a working custom interaction framework in no time using Unity's XR Input system without the Oculus Integration asset in the project whatsoever.
I was wondering if using the Unity Integration asset is actually obligatory? I'm quite confident that I can make all the interaction needed on my own, but what if I hope to release something on the store one day?
If so, what are in fact the required parts of the asset package?
I've developed VR applications professionally for B2B in Unity for a couple of years now - Gear VR, Vive, and Rift. It's my first time developing for the Oculus Quest, amazing device. I've easily and successfully been able to build directly to the device, and already made a working custom interaction framework in no time using Unity's XR Input system without the Oculus Integration asset in the project whatsoever.
I was wondering if using the Unity Integration asset is actually obligatory? I'm quite confident that I can make all the interaction needed on my own, but what if I hope to release something on the store one day?
If so, what are in fact the required parts of the asset package?