cloning-prims

Cloning USD prims duplicates existing prim subtrees to specified destination paths, safely copying geometry and scene structures without manual recreation. This process requires correct source validation and destination conflict checks before applying tested cloning APIs for reliable duplication.

Cloning USD prims creates fully independent duplicate subtrees at new paths, whereas instancing shares geometry data for memory efficiency and referencing links external layers. Workflow guidance helps choose the right approach based on whether you need scene mutation or instance preparation.

OpenUSD supports runtime stage mutation through tested cloning APIs for both Python and C implementations. These patterns include validation, async handling, and error checks to ensure reliable geometry duplication during scene construction and OVRTX workflows.

Cloning USD prims fails at occupied destination paths because the operation requires destination conflict checks to prevent overwriting existing scene elements. Validating the target stage path ensures the cloning API can safely copy the source prim subtree without structural collisions.

The best way to prepare USD prim clones for instance scenarios is using tested cloning APIs that apply source validation and destination conflict checks. This ensures reliable subtree duplication across multiple destination paths during runtime stage mutation for OpenUSD and OVRTX workflows.

Source validation is required before cloning USD prims to ensure the prim subtree exists and contains the expected geometry data. Correct validation combined with destination conflict checks enables tested cloning APIs to reliably duplicate scene elements at new paths.