Parks artists edit playground meshes in a DCC then return content to USD. What structural property should the round-trip preserve?
Select an answer to reveal the explanation.
Short Explanation
Stable prim paths are street addresses for your playground parts. If the round-trip renames every address, the rest of the twin gets lost looking for home.
Full Explanation
When parks artists edit playground meshes in a DCC and return content to USD, stable prim paths are the structural property the round-trip must preserve. Downstream references, payload arcs, variant selections, and layer overrides key off those paths; renaming them orphans the rest of the playground twin and breaks city composition roots.
Brand-new random prim paths on every export intentionally break references and force manual repair after every art pass. Removing all kind metadata because “kinds cannot round-trip” is an unnecessary loss—kinds should be preserved or explicitly remapped, not discarded as blanket policy. Flattening the entire playground into one anonymous Mesh destroys hierarchy, addressing, and selective override workflows municipal twins rely on for phased updates.
Exam caveat: If a DCC namespace forces path changes, maintain an explicit path-map artifact and rewrite references in the same pipeline step; silence is not a migration strategy for parks asset libraries.
Operational check: Diff prim identifiers before and after round-trip, resolve a known set of references and overrides onto playground assets, and fail the pipeline if path stability or reference resolution regresses relative to the previous good package.