![faceshift kinect v2 faceshift kinect v2](https://media.springernature.com/lw685/springer-static/image/art%3A10.1007%2Fs11042-016-3374-6/MediaObjects/11042_2016_3374_Fig1_HTML.gif)
Delete all the characters written inside the Value Data textbox (mine contained “AiChargerPlus”) Double click on the “Lower Filters” item.The path and the value that you are going to modify (Click to zoom in a new tab, as all the images of this guide) Once you’re here, you should see on the right panel some strange stuff with 3 columns: Name, Type, and Data.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\
![faceshift kinect v2 faceshift kinect v2](https://ars.els-cdn.com/content/image/1-s2.0-S0966636216300479-gr2.jpg)
At this point, you should come out with a window of the registry.Say Yes to the UAC popup that warns you that you are going to modify system stuff.Open the Windows Registry (press Win+R, type “regedit” and then press ENTER).
#Faceshift kinect v2 how to
The solution is simple if you know how to use Windows Registry: And the Windows Device Manager said me that my PC already run all the most recent driver versions. Rebooting and changing ports had no effect. But my PC is ok with Kinect since I used it a lot of times to showcase our full body VR solution, so the problem should be with the Windows 10 Creators Update that has broken something in my Kinect support. I tried the device on my Windows 8.1 laptop, and it worked like a charm, so it was obvious that the problem was with my PC. Of course, no one of these solutions worked for me.
#Faceshift kinect v2 drivers
It all started when I wanted to shoot my latest Youtube video (on Amazon Sumerian) using Kinect as a webcam, something that on Windows 10 is now possible thanks to the new drivers by Microsoft.