Depthkit Core asset disappears
You may find that some Depthkit assets disappear when you move the camera too close to them, or aim the camera at your Depthkit asset from a particular perspective.
This is an issue with Depthkit Core’s Mesh Bounds not being positioned correctly in relationship to the clip’s actual rendering geometry, which then causes it to get frustum-culled inappropriately and disappear. You can see the Mesh Bounds position when you enable Gizmos and observe the green bounding box associated with the clips’ Collider component.
By default, this bounding box will surround the asset origin - which is the same as the sensor position - rather than the subject of your capture.
You can work around this by moving the origin to the subject in relationship to the bounds. This can be accomplished this two ways:
Edit volume bounds in metadata file
In the metadata, change the boundsCenter.z value to the distance in meters that you want the origin be offset. For example, the sample Depthkit Autumn clip should have a value of ~2.1 by default, as that is the approximate distance from the sensor to the subject.
Apply offset with parent Unity object
Parent the Depthkit object to an empty object, and use the Transform component of the Depthkit object to dial in the offset. Then apply any position/rotation changes to the parent.
Updated about 2 months ago