Depthkit 0.7.0 Studio Export to Unity - Weird behavior

Hello everyone,

I might be in a very specific situation, hopefully some of you can provide me with some guidance.

I am using a 8 Kinect setup with Depthkit Studio 0.7.0 pre-release.
I calibrated the setup and got fair results, I know my Kinects are far away thus limiting the quality of both calibration and capture, but that’s a trade off we are ready to make in order to allow us for a larger capture space.

Here’s a screenshot of the calibration results.

We’ve been shooting all morning and in Depthkit everything’s great. Captures are what we expect and the fusion preview is fine. However, once exported in CPP Video and imported in Unity I get a lot of meshing issues. The problem is present on two different exports I tried on two different recordings. Watch this video for a comparative view of Depthkit and Unity results.

It feels like the exported version omits some parts of the camera even though it’s still inside the bounding box.

I also ran into and issue with the bounding box. I did set the values too high, trying to include more space to see if the export would do the same bug with the whole space. Now I’m unable to open this particular recording because it overloads GPU memory by trying to allocate 20gbs+ in VRAM. Is there a way to reset to the default bounding box?

Hi @GaneshBaron_Aloir

Thanks for your post, and congrats on being the first to find bugs in the 0.7.0 pre-release! :joy:

It does look like you’ve encountered a bug with the larger volume - its a scenario we have not yet tested as thoroughly. With your blessing, I will send you an email to start a process of gathering the project file from you so we can reproduce it on our side.

With regards to your project overloading your GPU, we will look to put a fix in for this. IN the meantime, you can reset your project settings in the json project file as a hack.

  • Close Depthkit
  • Go into your Depthkit project folder
  • make a back up of your dkproject.json
  • Open the dkroject.json in a text editor
  • Find the “fusedMeshConfig” entire for your capture.
  • Change the max/min bounds to be smaller
  • And/or change the Mesh Density to be lower
  • Reopen Depthkit and reload the Recording

Let us know how this goes as a quick fix!

2023-05-12 13_40_28-C__Users_Scatter_Documents_Depthkit_DepthkitStudioSampleCapture_dkproject.json -