// 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.
| 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"] |
Use this skill when the user asks to clone, duplicate, copy a prim, or create instances of existing geometry.
Resolve inputs in this order: existing repository files and referenced snippets, explicit user request, then broader agent context.
> **Source:** snippet before writing or explaining API usage.This skill has no scripts.
clone_usd creates copies of an existing prim subtree at one or more new target paths in the runtime stage. This is useful for duplicating geometry, creating arrays of objects, or spawning instances from a template.
Source:
tests/docs/python/test_stage_mutation.pysnippetdoc-clone-usd
Source:
tests/docs/python/test_stage_mutation.pysnippetdoc-clone-usd
Source:
tests/docs/python/test_stage_mutation.pysnippetdoc-clone-usd-async
Source:
tests/docs/c/test_stage_mutation.cppsnippetdoc-clone-usd-c
Source:
tests/docs/c/test_stage_mutation.cppsnippetdoc-clone-usd-c
| Python | C |
|---|---|
renderer.clone_usd(source, targets) | ovrtx_clone_usd(renderer, source, targets, count) |
renderer.clone_usd_async(source, targets) | ovrtx_clone_usd() (always async in C) |
clone_usd() blocks until the operation completes. Use clone_usd_async() for non-blocking behavior.ovrtx_clone_usd() is always asynchronous. You must wait on the returned op_index with ovrtx_wait_op() before using the cloned prims (e.g., writing attributes or stepping).> **Source:** directives in this skill to locate tested snippets before reusing API patterns.High-level overview of a typical ovrtx application lifecycle. Use when user asks how to structure an ovrtx program, what the main steps are, or how the pieces fit together.
Asynchronous operation patterns including polling, timeouts, and non-blocking workflows. Use when user asks about async rendering, non-blocking operations, polling, timeouts, or parallel rendering.
Creating persistent attribute bindings for efficient repeated writes to the same prims and attribute. Use when user asks about persistent bindings, repeated writes, efficient animation loops, bind_attribute, or updating transforms every frame with caller-owned tensors. Use mapping-attributes when the hot path needs zero-copy direct writes into ovrtx buffers.
Binding materials to prims at runtime. Use when user asks to assign a material, change a material, set material binding, or swap materials on a prim.
Available camera render outputs for Real-Time Path-Tracing (RT2) mode. Use when user asks what AOVs/render vars are available, what format or dtype an output has, or how to read a specific output like depth, normals, albedo, or distance.
Authoring and configuring OmniLidar sensor prims and lidar PointCloud render outputs. Use when user asks to create a lidar scene, configure an OmniLidar prim, choose lidar output frame/coordinate behavior, or request lidar PointCloud channels.