Forum Discussion
Solved
Is the Interaction SDK enough for a VR App? would it be better to start from the All-In-One?
I still need to find my way through all the SDKs proposed by Meta. I'm a little bit confused about the one to pick... from what I can see the Interaction SDK is enough to create a VR experience, with...
Hi Bitwaker, thanks for tagging me!
- Core XR SDK is required for the All-in-One SDK. It's not required with the standalone Interaction SDK.
- I haven't used the Audio XR SDK or compared it to the default system, so I don't have an informed opinion here. My first thought would be to try using the default Unity system, then switch to the Audio XR SDK later on if there's something the default system lacks.
- Yes, Interaction SDK is all you need for your VR app if you just want hand tracking and controllers and interactions for them. I write all of the Interaction SDK documentation, so if the docs are missing info you're looking for or something is unclear, let me know.
I hope that helps--if you have any additional questions about Interaction SDK, please keep tagging me 🙂
Personally I'd say the Audio SDK is pretty much indispensable for its spatialization. You won't get that quality out of the box with Unity. After importing the package all you need to do is set it as the Spatialisation plug-in in Audio settings (https://developer.oculus.com/documentation/unity/meta-xr-audio-sdk-unity-req-setup/) then add the Meta XR Audio component to any component with an Audio Source (https://developer.oculus.com/documentation/unity/meta-xr-audio-sdk-unity-spatialize/)
Proper 3D audio makes a huge difference to any VR experience.
Thank you! this is a very great hint. I'm going to import the Audio SDK and the Interaction SDK to start my new project.
