How do I reduce the number of dropped frames?

For a complete guide on increasing capture performance, see the Verify Computer Performance page.

Why are there holes in my depth data?

Due to the way in which depth cameras sense depth, there are certain materials that cause errors in the depth data during capture. These are usually reflective or shiny materials that will cause holes and similar artifacts in your depth stream. Read more about material and garment constraints. To repair and reduce these artifacts, Depthkit's Refinement algorithm is designed to clean up and enhance your volumetric data.

Why is my project not launching correctly?

My takes are no longer visible in my Depthkit project.

  1. This is likely due to a file that may be missing from your project folder. Ensure that if you relocate your project to a new computer or drive, that you move all files and folders within the Depthkit project parent folders.
  1. Do not rename files within your Depthkit project. The dkproject.json is the source of truth of all of your project information. If your take folders are renamed, the dkproject.json file will no longer be able to read the takes when you launch the project in Depthkit. Instead, name the take from within Depthkit before your capture each take.

  2. Do not move take folders outside of your Depthkit project folder. If you relocate takes outside of the Depthkit parent folder, the new file path will not update automatically and Depthkit will not be able to read the takes when you launch the project.

  3. Do not delete the _calibration folder or dkproject.json file. Both files hold essential information about your project and should remain untouched within your Depthkit project folder.

When opening an existing project, my project does not open and takes a long time to load.

  1. Make sure you are selecting the parent project folder. Do not select and individual take within that folder.

  2. If you have relocated your project folder, make sure it is not opened from a exFat drive. If you need to move your project to an external hard drive, use the NTFS format.

When opening an existing project, I get an error message saying "Application has requested more GPU memory than is available"

When opening an existing project with many recorded takes, you may get an error that closes Depthkit. To work around this:

  1. Make a copy of your project folder (complete with all of the contents).

  2. Remove some of the take folders from the new copy.

  3. Open Depthkit and open this pared-down project folder instead of the original.

The clip names of the removed takes will still appear in the Edit context's Library panel, but show red alert icons indicating that the clips are offline. To restore those clips, simply add the take folder to the new project folder and restart Depthkit.

Common errors messages

Console error messages

Color frame dropped. 
Depth frame dropped.

Dropped frames will be reported in the Depthkit console, however, you should only watch for dropped frames in the diagnostics panel above the record button that becomes visible when recording. If this panel is reporting dropped frames, follow the steps to verify computer performance. This diagnostics panel will be your source of truth, so you don't need to worry about watching for performance issues in the console window.

Console warning messages

Failed to load legacy take: unable to determine asset version.

The error above may be present if you are importing a legacy project into Depthkit. It means that you likely have folders within your Depthkit project that are not take folders. This is fine and will not have a negative impact on your project. You can disregard this message.