[RESOLVED] Issue Viewing Exported Depthkit Clip In Unity 2020.3

Hello,

I was able to create a Unity 2020.3.33 project with the HDRP pipeline and see the sample autumn data work correctly.

However when I export my clip into Unity, nothing appears. An interesting note is that if I use the autumn meta data, I can see my clip and it does play though it doesn’t play in full

Is there something I should check for in my export settings?

Thanks!

@CameronDonley, sorry to hear you’re having trouble. Here are some questions to help narrow down the issue:

• Are is your asset a Depthkit Core (single-sensor) or Depthkit Studio (multi-sensor)?
• When you swap your asset for the Autumn sample, are you swapping only the video, poster, and metadata files linked to the Depthkit object, but keeping all other components and settings in the object the same?
• Are you using the Shader Graph look, the VFX Graph look, or both?
• Are you getting any errors in the console?

Screen recordings of what you’re seeing, or even screenshots of your Depthkit object’s Inspector panel may also be helpful in identifying the issue of you are able to share. Let us know, and we’ll see if we can help figure this out.

Hey Cory,

• I recorded the asset using depthkit 0.6.0 app with 1 Azure Kinect DX Camera
• I’m using the same prefab Depthkit Clip + Studio Shader Graph Look for both. Here’s me with my meta data

image1920×545 46.8 KB

Forum won’t let me have two screenshots in the same post so I’ll make another post with the vs screenshot

• There are no errors in the console

vs me using her metadata

meta3836×1039 262 KB

@CameronDonley Can you share your metadata file? We can have a look and see if there’s an issue with its contents.

Won’t let me upload .txt files but I’ll dump the text

{
    "_versionMajor": 0,
    "_versionMinor": 3,
    "boundsCenter": {
        "x": 0,
        "y": 0,
        "z": 0.6662974953651428
    },
    "boundsSize": {
        "x": 1.6137933731079102,
        "y": 1.272017240524292,
        "z": 0.8325949907302856
    },
    "format": "perpixel",
    "numAngles": 1,
    "perspectives": [
        {
            "clipEpsilon": 0.006005320698022842,
            "crop": {
                "w": 1.0,
                "x": 0.0,
                "y": 0.0,
                "z": 1.0
            },
            "depthFocalLength": {
                "x": 504.4706726074219,
                "y": 504.6934814453125
            },
            "depthImageSize": {
                "x": 752.0,
                "y": 593.0
            },
            "depthPrincipalPoint": {
                "x": 383.9451904296875,
                "y": 366.900634765625
            },
            "extrinsics": {
                "e00": 1.0,
                "e01": 0.0,
                "e02": 0.0,
                "e03": 0.0,
                "e10": 0.0,
                "e11": 1.0,
                "e12": 0.0,
                "e13": 0.0,
                "e20": 0.0,
                "e21": 0.0,
                "e22": 1.0,
                "e23": 0.0,
                "e30": 0.0,
                "e31": 0.0,
                "e32": 0.0,
                "e33": 1.0
            },
            "farClip": 1.0825949907302856,
            "nearClip": 0.25
        }
    ],
    "textureHeight": 1188,
    "textureWidth": 752
}

@CameronDonley I took a look at the metadata you provided, and it appears to be working.

image1920×1045 99 KB

One thing our team noticed is that in your screenshot, you have a Depthkit Studio mesh source and look applied to your Depthkit Core clip, and although it may render your asset, artifacts may appear and performance may drop. Be sure to switch out the components with their Depthkit Core counterparts to avoid these issues.

So I was able to get this working in a new project that was using Core instead of HDRP. Is there a reason why it wouldn’t work with HDRP?

@CameronDonley, to clarify a couple of things:

• Depthkit Core refers to workflows using single-sensor assets.
• Depthkit Studio refers to workflows using multi-sensor assets

Unity’s render pipelines (Built-in, URP, and HDRP) can render both types of assets, as long as the proper Depthkit Expansion Package plugins are used.

• For single-sensor assets in the Built-in pipeline, install the Depthkit Core package, and use the Depthkit Core Built-in Look component in your Depthkit object.
• For single-sensor assets in URP or HDRP, install Depthkit Core & Depthkit Shadergraph packages, and use the Depthkit Core Shadergraph Look component in your Depthkit object.

Let me know if you have any other questions, and if the above combinations are still not working.

Ok that all works, thanks for the explanation