For a client we developed a Kinect application which was shown at the Dutch Floriade festival. More details about this project in a next post.
The problem with the old Kinect SDK was the inability to use the Kinect within a virtual machine. Because of this I had to create a bootcamp partition and install Windows on it just for the sole purpose of Kinect development. The 1.6 SDK solves this!
Below are the results of my tests with the Kinect within VMWare. I used the following system configuration to test on:
- MacBook pro 2011 with 2Ghz core i7 and 8GB RAM..
- OSX Mountain Lion.
- VMWare Fusion 5 running Windows 7.
- Visual Studio Express 2012.
- Kinect 1.6 SDK.
First I tested the above setup with the Xbox Kinect. This did not work which I more or less expected since Mircosoft wants to push the Kinect for Windows for Kinect development.
Next I tested was the Kinect for Windows. After I connected the device I started the Shape Game sample application. The device was found and worked immediately! I also tested the Kinect with our own application and this also worked as expected.
Ont thing I noticed was that both applications did not run as smooth as when I ran the application under bootcamp. After examing my virtual machine settings I noticed I had given it only 1 cpu core (out of the available 8). This could be the problem. When I changed the maximum number of cpu cores the virtual machine may use to 4, things ran much smoother. There was no noticeable difference when running within a virtual machine or bootcamp.
For more information about the 1.6 SDK see: http://msdn.microsoft.com/en-us/library/jj663803.aspx#SDK_1pt6_M2.
Conclusion
The new Kinect 1.6 SDK does work within a virtual machine if the Kinect for Windows is used.
Conclusion
The new Kinect 1.6 SDK does work within a virtual machine if the Kinect for Windows is used.