Below is a list of known issues and fixes / work arounds for the SDK. Check if your problem is in the list below, and if not, contact us at support@threegear.com.
Here are a few tips to improve the tracking quality:
Camera Height: The camera has a sweet spot for tracking the hand. If your hands get too close, the quality degrades. If you're using a single Primesense Carmine 1.09 from the dev kit, the ideal height for the camera is 28". Try to maximize the length of the snake arm in the dev kit.
If you're using a single Kinect or Asus Xtion Pro, the ideal height for the camera is 33".
If you adjust the camera height, don't forget to run camerasetup again!
Calibration: The quality of the hand tracking is dependent on an accurate estimate of the size of your hands. If you do not know your hand scale, be sure to run the nimble_server in calibration mode (Win64 / OS X):
nimble_server.bat -c (or nimble_server.sh -c on Mac).
Alternatively, you can try personalizing your hand calibration.
It is likely that you have the wrong CameraType set in your config.yml and your hands are getting mirrored.
If you're using an Xbox Kinect camera:
CameraType: OpenNI
If you're using a Kinect for Windows camera:
CameraType: KinectForWindows
If you're using a PrimeSense or Asus camera:
CameraType: OpenNI2
This issue can occur if you're using the legacy two-camera setup. If you intended to use a single camera (which is recommended), you must set in your config.yml file: NumCameras: 1
Make sure you've plugged in the two cameras on separate USB 2.0 controllers. Most desktops and laptops have several USB ports on different controllers. Try selecting two ports that are physically far apart.
In Windows, you should be able to see that both Kinect cameras are working properly by typing "Device Manager" in the Start Menu and opening the "PrimeSense" folder.
Make sure that you are either using OpenNI with two Kinect Xbox 360 sensors or the Microsoft Kinect SDK with two Kinect for Windows sensors.
This issue and resolution applies only to the legacy two-camera solution using the Xbox Kinect or Kinect for Windows.
Check that both Kinect cameras are working normally under the PrimeSense device group in the Device Manager. If the PrimeSense devices are not present or not working normally, you'll probably need to install / reinstall either the OpenNI / NITE / SensorKinect drivers or the Microsoft Kinect for Windows runtime. You can find both sets of drivers linked from our legacy camera installation page (Win64 / OS X).
Make sure you are using Xbox 360 sensors (rather than Kinect for Windows sensors).
From the Device Manager, double-click on the Kinect Camera icon to open up Kinect Camera Properties and check that the driver is provided by PrimeSense. If the drivers are provided by Microsoft, then Windows Update may have updated the Kinect Driver behind your back. Disable Windows Update's driver auto-update. Then use USBDeview x64 to disable and uninstall the old Kinect drivers. Finally, reinstall the PrimeSense drivers from our legacy installation page (Win64 / OS X).
Run NiViewer64 that comes with OpenNI (from the Startup menu) to check that OpenNI is working properly on your computer.
Make sure you are using Kinect for Windows sensors (rather than Xbox 360 Kinects).
Make sure you are using the Kinect for Windows setting in the configuration file (which defaults to OpenNI). Check that CameraType: KinectForWindows is set in the config.yml file.
Make sure that you installed the Kinect for Windows run-time linked from our legacy camera installation page (Win64 / OS X)
You can contact us at support@threegear.com.