| name | cloning-prims |
| description | Cloning USD subtrees to create copies at new paths. Use when user asks to clone, duplicate, copy a prim, or create instances of existing geometry.
|
| license | LicenseRef-NvidiaProprietary |
| version | 0.3.0 |
| author | NVIDIA ovrtx |
| tags | ["ovrtx","usd","prims"] |
| tools | ["Read","Grep"] |
Cloning Prims
When to Use
Use this skill when the user asks to clone, duplicate, copy a prim, or create instances of existing geometry.
Inputs
Resolve inputs in this order: existing repository files and referenced snippets, explicit user request, then broader agent context.
- Target API surface: Python, C/C++, or both.
- Source prim path to clone and one or more destination prim paths to create.
- Desired execution mode: Python ovstage sync, Python ovstage async, or C ovstage clone (which is inherently async at the C layer — the enqueue returns an op id you wait on).
- Whether the request is actually a clone, USD reference, instance, or new-geometry authoring workflow.
- Repository source snippets referenced below. Treat these snippets as the API source of truth.
Prerequisites
- Use an ovrtx checkout that contains the referenced examples and docs tests.
- Read the relevant
> **Source:** snippet before writing or explaining API usage.
- Confirm the source prim already exists on the runtime stage and destination paths do not conflict with existing prims unless replacement is intended.
Instructions
- Identify the source prim path and every destination path the caller wants to create.
- Confirm whether the workflow needs a synchronous Python ovstage clone, Python async ovstage clone, or C ovstage clone.
- Read the matching snippet and preserve its source-path, destination-list, wait, and error-checking pattern.
- Do not use cloning when the caller actually needs USD instancing, references, or authoring new geometry from scratch; route to the loading or writing skills instead.
- When changing code, run the stage-mutation docs test that owns the clone snippet whenever practical.
Output Format
- For explanations, cite the relevant API names, source snippets, and caveats.
- For code changes, summarize the files changed, snippets affected, and validation run.
Scripts
This skill has no scripts.
Limitations
- The referenced snippets remain the source of truth; update or add tested snippets before documenting new API usage.
Overview
stage.clone creates copies of an existing prim subtree at one or more new target paths and publishes the change at an ordinal. This is useful for duplicating geometry, creating arrays of objects, or spawning instances from a template.
Python
Clone to a single target
Source: tests/docs/python/test_stage_mutation.py snippet doc-clone-usd
Clone to multiple targets
Source: tests/docs/python/test_stage_mutation.py snippet doc-clone-usd
Async clone
Source: tests/docs/python/test_stage_mutation.py snippet doc-clone-usd-async
C
Clone to multiple targets
Source: tests/docs/c/test_stage_mutation.cpp snippet doc-clone-usd-c
Wait for completion
Source: tests/docs/c/test_stage_mutation.cpp snippet doc-clone-usd-c
Async clone
Source: tests/docs/c/test_stage_mutation.cpp snippet doc-clone-usd-async-c
At the C layer ovstage_clone is inherently async — the enqueue returns an
ovstage_enqueue_result_t with an op_index you wait on. There is no distinct
synchronous variant, so the "async" snippet shows the same call as the base
clone snippet; the two are kept for parity with the Python clone /
clone_async split.
Key Types / Functions
| Python | C |
|---|
stage.clone(source, targets, ordinal=...) | ovstage_clone(stage, source, targets, count, ordinal) |
stage.clone_async(source, targets, ordinal=...) | ovstage_clone(...) (C is always async — wait on the returned op_index) |
Troubleshooting
- The source path must exist in the stage.
- The target paths must not already exist in the stage.
- Cloning copies the entire subtree under the source path, including all children.
- Relationship targets, path values, and USD attribute connections under the source
subtree are rebased to the corresponding clone. Paths outside the subtree stay unchanged.
- In Python, advance the ovstage write floor after the clone completes and before rendering its ordinal.
- In C,
ovstage_clone returns an ovstage_enqueue_result_t; wait on the returned op_index with ovstage_wait_op() before advancing the write floor or using the cloned prims (e.g., writing attributes or stepping).
Deprecated Standalone APIs
ovrtx_clone_usd (C) and Renderer.clone_usd* (Python) are deprecated in 0.4
and retained for standalone compatibility. New code should clone through
ovstage at an application-owned ordinal, wait for the clone, and advance the
write floor before rendering it.
See docs/core/ovstage_integration.rst, skills/update-0_3-0_4-c/SKILL.md and skills/update-0_3-0_4-python/SKILL.md.
References
- Use the
> **Source:** directives in this skill to locate tested snippets before reusing API patterns.
- Keep related skills, docs, and snippets synchronized when changing the workflow.
