Using Leap Motion to Develop for Nimble VR
Very excited to hear about the Nimble VR deal. We now have a more concrete idea of what the input device will be... your hands! As Rift developers who are supporting Leap Motion in their development efforts does it make sense to consider using Leap Motion as a proxy for Nimble VR? The upside is that some things will not change... meaning you will use hands in both the Leap Motion and Nimble VR as the UI/Input device inside your title. What will change is the SDK which means you will have to rewrite the code that communicates to the API for the hand tracking.
I am imagining Oculus will make a Nimble VR kit for our DK2s available soon... Soon being a relative term as they need to do more engineering and manufacturing before this is ready for the devs... Meanwhile precious development time is marching on as we get closer to a CV1 release.
So does it make sense to use Leap Motion as a proxy while waiting for the release of Nimble VR for the Rift?
I am imagining Oculus will make a Nimble VR kit for our DK2s available soon... Soon being a relative term as they need to do more engineering and manufacturing before this is ready for the devs... Meanwhile precious development time is marching on as we get closer to a CV1 release.
So does it make sense to use Leap Motion as a proxy while waiting for the release of Nimble VR for the Rift?
