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 🙂
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 🙂
Thank you for providing such a clear answer. The only concern I have with the documentation today is the lack of clarity regarding the full set of SDK. This led to my previous confusion. I understand that this may not fall under your responsibility as a member of the Interaction SDK team, but I believe it's important to enhance the introduction to clearly explain the purpose of each SDK and how they can be utilized together.
Also the fact that the "All-in-One" is at version 60.0 and the interaction SDK reached 62.0 was quite confusing while trying to understand where to start 🙂 does it mean that the All-In-One is still using interaction SDK 60? or just they move with a different version number... (this is a topic for another question... 🙂 )
I completely agree with you that the documentation set should explain how the SDKs work together. That's been a sticking point before for me as well as other people trying to use multiple Meta SDKs. I'll pass your feedback to the team that handles the docs for the entire set of SDKs 🙂
The All-In-One is now using Interaction SDK v62, but originally the All-In-One release was delayed, so it was stuck with v60 of Interaction SDK for a few days. That should be fixed now!
Also, in my original answer I incorrectly said that Interaction SDK requires the XR Core SDK and includes it. That was incorrect, so I've updated that part of my answer.
