On some Azure Kinects, we have noticed a slight misalignment between the sensor depth and color, especially when more than 3 feet from the sensor. We are currently investigating this issue.
For more details on how to establish if your sensors are affected by this inaccuracy, read our guide:
Azure Kinect alignment verification →
There could be a connectivity or power issue with your sensor.
- Verify that your depth sensor is plugged in and well powered. You can check this via the power indicator LED on the back of the device.
- Restart your computer and relaunch Depthkit once you have checked that your sensor is properly powered.
Ensure that your sensor is securely plugged in and powered on.
If it is a power issue, you may want to try plugging it directly into the power outlet in case an extension cable is causing insufficient power.
Ensure that you have installed the Kinect SDK.
If you have not done so, Depthkit will launch, but you will not be able to see depth or color streams.
Check the performance of your sensor with the Kinect Configuration Verifier Tool.
This will give you insight on the state of your sensor connection. Ideally, all categories will be checked and green.
Make sure you have your sensor connected to your computer via a USB-3.1 / USB-C (gen 2) port. Gen 2 ports have a much higher data transfer rate and will promote a more stable connection and data stream from your depth sensor. If you computer does not have a USB 3.1 (gen 2) port, try a USB to USB-C adapter. Learn more about USB ports and how to find which one you are currently using.
You cannot run the Kinect Configuration Verifier while you are running Depthkit
You will find that the depth/color streams may not show up in Depthkit when both apps are active. With this in mind, once your Kinect performance is confirmed, close the verifier before you open Depthkit.
If your Kinect is repeatedly disconnecting from the computer, update your WDF Kinect Sensor Interface driver. You can find this in the Device Manager, under Kinect sensor devices. In the drop down, right-click on WDF KinectSensor Interface and select update driver.
If this does not solve the issue, take a loot at the Performance testing page.
To solve for under-performance, follow the instructions in Performance testing.
If there is not enough light in your scene, the Kinect fps may drop to 15 fps. To avoid this, make sure your capture area is well lit. You will know when this happens if the Depthkit console reports the warning "low light activated". This low light mode will be deactivated when lighting is increased.
Depthkit detects a body or bodies based on body indexbody index - The detection of one or multiple bodies in the depth data. When generating your assets, this acts as a body mask, allowing you to simply hide the background for clean exports of your subjects. This eliminates the need to shoot on a green screen. data. If your subject is not detected during capture when capturing with the Kinect for Windows v2:
Make sure the full body is in the frame. The body indexbody index - The detection of one or multiple bodies in the depth data. When generating your assets, this acts as a body mask, allowing you to simply hide the background for clean exports of your subjects. This eliminates the need to shoot on a green screen. cannot detect a partial body or a subject that is being obstructed by an object.
Make sure the subject is not too close to the sensor. The Kinect will not detect a body if too close to the sensor.
- Ensure that your Kinect is level and not rotated. You may be tempted to capture vertically as you would with a DSLR. However, the sensor cannot detect bodies if rotated or in a vertical position.
To solve this issue, update the firmware on your RealSense to the latest version. Find information on firmware releases and how to update here.
Updated 3 months ago