메뉴
Loading a base USD scene with additional runtime prims in tests. Use when a doc test needs to combine a scene file with RenderProducts or other prims that aren't in the original scene.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | combining-scene-with-runtime-prims |
| description | Loading a base USD scene with additional runtime prims in tests. Use when a doc test needs to combine a scene file with RenderProducts or other prims that aren't in the original scene. |
ovrtx only supports one root layer per renderer. Documentation tests often need a base scene (for cameras, lights, geometry, and materials) plus doc-specific prims such as RenderProduct or RenderVar definitions. For that case, use open_usd_from_string() / ovrtx_open_usd_from_string() with an inline root USDA layer that contains a subLayers composition arc to the base scene and authors the extra prims in the same root layer.
This inline sublayer pattern is supported and is the preferred docs-test pattern when the code example needs to demonstrate a single composed stage. Use add_usd_reference* only when the example specifically needs to add or remove referenced content after a root stage is already open.
Build one inline root USDA string that:
subLayers = [@/path/to/base_scene.usda@] to bring in the actual scene content.open_usd_from_string() in Python or ovrtx_open_usd_from_string() in C.Python source:
tests/docs/python/test_sensor_configuration.pysnippetdoc-add-render-config-layerC source:
tests/docs/c/test_sensor_configuration.cppsnippetdoc-add-render-config-layer-c
USD subLayers is a composition arc that layers multiple USD files into a single stage. The inline USDA becomes the "stronger" layer (opinions win), and the sublayered scene file provides the base content. ovrtx sees this as one root layer containing everything.
defaultPrim or prefix_path is required for this pattern. Those are reference-addition concerns, not root-layer sublayer concerns.simple_camera.usda and add /Render/Camera in the stronger layer./Camera0, the RenderProduct's rel camera must point to /Camera0, not /World/Camera.renderer fixture does not reset automatically. Use open_usd* to replace the root stage for each test, or call reset_stage() explicitly before additive reference tests.open_usd() and open_usd_from_string() separately to combine layers. The second call replaces the root stage, discarding the first.add_usd(), add_usd_layer(), and ovrtx_add_usd() are old names. Use open_usd* for root layers and add_usd_reference* for additive references.add_usd_reference* just to combine base scenes with RenderProducts. Inline subLayers keep the snippet as one root stage and match the documented pattern./Camera0, not /World/Camera. If the RenderProduct points at the wrong path, the step will produce no frames.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.
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.