Public-works assets include underground utility vaults that do not fit stock model kinds cleanly. When is a custom model kind appropriate?
Select an answer to reveal the explanation.
Short Explanation
Sometimes the city has a special drawer labeled utility-vault because the stock filing cabinet drawers do not fit. Register a custom model kind when core kinds are not enough.
Full Explanation
Public-works underground utility vaults that do not fit stock model kinds cleanly warrant a custom model kind when core kinds are insufficient and a registered custom kind clarifies civic model hierarchy. Kinds help tools classify model structure (component/assembly/group-style organization). If vaults are first-class municipal assemblies that core kinds misfile, registering a custom kind—properly derived/registered in the kind registry—improves traversal, filtering, and packaging rules for utility twins.
Creating a custom kind whenever a mesh has more than four materials couples kind to material count, which is not what kinds mean. Deleting KindRegistry so no kinds remain destroys classification rather than clarifying it. Never using kinds and relying only on camera prims for categorization abandons model hierarchy and is not viable for municipal twin organization.
Exam caveat: custom kinds are appropriate sparingly—when core kinds cannot express the civic hierarchy—not as decoration for every mesh oddity. Registration and inheritance rules matter; an unregistered string is not a real kind.
Operational check: register the custom vault kind, tag vault models correctly, confirm model-hierarchy tools recognize the kind, ensure core kinds still work for ordinary components, and document when authors should choose the custom kind versus stock kinds.