none
Does Kinect SDK beta 2 support Virtual Machines RRS feed

  • Question

  • Hello.

    I would like to know, if Kinect SDK beta 2 can be run in virtual environments ?

     

    Thanks,

    Vahagn


    Vahagn Nahapetyan Blogs : http://vh4u.blogspot.com/ http://3dkinect.blogspot.com/
    Friday, November 25, 2011 7:46 PM

Answers

  • V1 update as of 1.6 supported virtual machines, given the guidelines outlined here:

    http://msdn.microsoft.com/en-us/library/jj663795.aspx

    v2 will not support virtual machines. The virtual machine would have to emulate/virtualize all the necessary DX11/Shader Model 5 requirements for compute without added latency to ensure all frames arrive on time. There is very limited threshold when sending frames to the compute shader.


    Carmine Sirignano - MSFT

    Thursday, August 28, 2014 6:52 PM

All replies

  • No. Here's a snip from the readme;

    Virtual machines: You must run applications built with the Kinect for Windows SDK Beta in a native Windows environment. Kinect for Windows applications cannot run in a virtual machine, because the Microsoft Kinect drivers and this SDK Beta must be installed on the computer where the application is running.

    Friday, November 25, 2011 9:05 PM
  • Thanks Greg for your quick response.


    I noticed this in beta 1 version too and thought Microsoft will support virtual machines in beta 2.  
    What about, if I will install SDK and drivers in the same virtual machine ?
    How I know in VMware you can have multiple drivers for the same hardware(one for real OS, one for virtual machine). So if you will install Kinect SDK just in the virtual machine, then all will work normal. What you think about this ?

     

    Vahagn 


    Vahagn Nahapetyan Blogs : http://vh4u.blogspot.com/ http://3dkinect.blogspot.com/
    Saturday, November 26, 2011 9:21 AM
  • Hello Vahag 

     

    Thats not working here.   If you find away than please share

    kind regards

    Bill  

    Thursday, December 8, 2011 9:52 AM
  • Hi Bill.

    I have done another thing. What I need was to install OpenNI and Microsoft SDK in the same machine. One in a real machine and the second in a virtual.

    I installed Microsoft SDK in my real machine and OpenNI in the virtual one. Virtual machine recognized 3 removable devices- Kinect Camera, voice, Motor.

    I intalled standard Microsoft camera driever  for Kinect Camera (can be found in System32) and it started to work fine. 

     

    Vahagn


    Vahagn Nahapetyan Blogs : http://vh4u.blogspot.com/ http://3dkinect.blogspot.com/
    Thursday, December 8, 2011 9:58 AM
  • Hello Vahagn

    That sounds great!!

    Hope to try it later this week thanks for sharing !!!

     

    Bill

    Thursday, December 8, 2011 10:35 AM
  • Yeah i found out where kinect installs the drivers for the sdk to.

    If you go to: C:\Program Files\Microsoft SDKs\Kinect\v1.0 Beta2\Drivers

    it has the drivers but you cant distribute them because i wouldnt have a clue as to how to correctly install them but you can play with installing the driver bythemselves on a test machine or virtual machine so when microsoft comes out with the installer to install drivers for themselves network administrators/IT can make images of a computer with the drivers installed.

    But as the readme says the beta version "does have distribution rights" (okay not word for word but i was paraphrasing a little)  but the commerical version will.

    Thought this might be of help so you can better use it in a virtual machine.

     


    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda
    • Edited by The Thinker Thursday, December 8, 2011 2:25 PM
    Thursday, December 8, 2011 2:25 PM
  • Hi,

    Just to add my voice to this. I have just purchased the Kinect For Windows sensor v2 specifically for some Psychology experiments based on body movements. It has a lot of cool features over and above Kinect v1. Unfortunately, my Uni environment only supports Windows 7 on our workstations so I've set up a Windows 8 VM for the Kinect v2 set-up using VMware player. Of course, this set-up does not work and now I know why. The sensor is recognised as "Xbox NUI Sensor" but will not work with any of the demos, Kinect Studio v2.0 or the Gesture Builder.

    If this could be made to work in future releases, it would really help. At the moment, my only recourse is to re-install my workstation with an OS unsupported by my central IT team to give a native OS platform for Kinect v2


    Martyn Atkins (Senior Technician / Programmer) Plymouth University School of Psychology LinkedIn: http://lnkd.in/V3dRi7 Twitter: @Martyn_JA

    Thursday, August 28, 2014 8:45 AM
  • V1 update as of 1.6 supported virtual machines, given the guidelines outlined here:

    http://msdn.microsoft.com/en-us/library/jj663795.aspx

    v2 will not support virtual machines. The virtual machine would have to emulate/virtualize all the necessary DX11/Shader Model 5 requirements for compute without added latency to ensure all frames arrive on time. There is very limited threshold when sending frames to the compute shader.


    Carmine Sirignano - MSFT

    Thursday, August 28, 2014 6:52 PM