You are debugging a stage where a prim is expected to have opinions from a referenced asset, but those opinions are not appearing in the composed scene. Which of the following are logical things to check to troubleshoot this issue?
Correct Answer: C,D
The first logical checks are the reference target and any variant selections affecting the prim. Option D is correct because if the referenced asset path is wrong, the asset cannot be resolved, or the referenced layer lacks the expected target prim or defaultPrim, the referenced opinions will not appear. NVIDIA's default-prim guidance explains that a reference without a prim path relies on the referenced layer's defaultPrim; without it, the reference can compose as empty. ( docs.nvidia.com ) Option C is also correct because variant selections can alter what scene description is composed. NVIDIA's variant-set material explains that variants may change attributes, visibility, activation, or even reference paths; when variants change references or activation, USD recomputes the composed structure. ( docs.nvidia.com ) Option A is generally not the right diagnosis because payload arcs are weaker than reference arcs in standard LIVERPS ordering, so they are not the first candidate for overriding a reference at the same site. Option B is unrelated to whether a reference composes; model kind affects organization and traversal, not basic reference resolution. This aligns with Debugging and Troubleshooting # References, Asset Resolution, defaultPrim, Variant Selections, and Composition Diagnostics .
NCP-OUSD Exam Question 17
In what way do variant sets in OpenUSD enhance flexibility in scene descriptions?
Correct Answer: A
Variant sets enhance flexibility by allowing a prim to expose named alternatives, where one variant selection contributes its authored opinions to the composed result. NVIDIA's Learn OpenUSD material describes variant sets as a way to define "alternative representations for a prim and switch between them without duplicating data." It also explains that a prim may have one or more named variant sets, each containing variant choices, and that the selected variant composes the opinions authored for that choice. Option A is correct because variant sets support selectable alternatives such as different model shapes, material looks, levels of detail, configurations, or composition arcs. This gives downstream tools or stronger layers the ability to choose a representation non-destructively without rewriting the asset. Option B is inaccurate because variants are not permanently merged into the prim; only the selected variant participates in the composed scene. Option C is incorrect because conflict resolution is handled by USD's composition and value-resolution rules, not automatically by variant sets themselves. Option D is also incorrect because USD does not statically combine every variant into a single representation. This aligns with the NVIDIA OpenUSD Development Study Guide topics Composition # Variant Sets , Composition Arcs , and LIVERPS strength ordering .
NCP-OUSD Exam Question 18
When prioritizing ease of interchange and reducing dependencies between different applications in a pipeline, why might codeless schemas, schemas defined purely in .usda files, be preferred over codeful schemas, schemas with generated classes using usdGenSchema?
Correct Answer: A
Codeless schemas are preferred when the pipeline goal is portability, easy distribution, and reduced application coupling. NVIDIA's Learn OpenUSD schema guidance states that schemas define data models and optional APIs for encoding and interchanging 3D and non-3D concepts, and notes a trend toward codeless schemas for easier distribution, with schemas becoming more focused on data modeling rather than behavior implementation. Option A is correct because a codeless schema can be distributed as schema data and plugin metadata without requiring every consuming application to compile, link, or ship custom generated C++/Python schema classes. OpenUSD's schema-generation documentation identifies codeless schemas as schemas produced without corresponding C++ classes, where only generatedSchema.usda and plugInfo.json are essential for runtime registration. Option B is incorrect because strongly typed convenience APIs are the advantage of codeful generated schemas. Option C is incorrect because fallback values are authored in schema definitions. Option D is incorrect because codeful and codeless schemas can both participate in schema registration and value interpretation. This aligns with Customizing USD # Schemas, API Schemas, Codeless Schemas, Schema Registry, Data Modeling for Interchange .
NCP-OUSD Exam Question 19
Consider a USD that has a root Xform, that has a child Sphere, that in turn has a child Cube. Xform - Sphere -- Cube When you open the USD, you see the sphere and the cube. But when you author the Sphere to be invisible, the sphere disappears, but the Cube is still visible. What could be causing this behavior?
Correct Answer: B
The issue is caused by an invalid scenegraph structure: a Cube gprim is nested below a Sphere gprim. OpenUSD considers nesting gprims under other gprims invalid, and usdchecker warns on this construct because important USD features such as activation and visibility are hierarchical and pruning. The OpenUSD glossary states that when an ancestor gprim is deactivated or made invisible, there should be no way for a descendant gprim to remain active or visible. ( openusd.org ) Option B is correct because the authored hierarchy violates the expected gprim organization. The correct structure is to place geometry prims under transform or organizational prims, such as Xform or Scope, rather than directly under other gprims. Option A is incorrect because USD visibility is not purely explicit per prim. NVIDIA's Omniverse visibility guide states that setting a prim's visibility to invisible makes the prim and all children invisible. ( docs.omniverse.nvidia.com ) Option C is also incorrect because setting the Sphere invisible should hierarchically affect descendants in a valid hierarchy. This aligns with Visualization # Visibility, Imageable Prims, Gprim Structure, and Valid Scenegraph Organization .
NCP-OUSD Exam Question 20
Why would you not see a sphere when opening this scene? #usda 1.0 ( defaultPrim = "wall_a_inst" upAxis = "Z" ) def Xform "wall_a_inst" ( instanceable = true variants = { string Emissive = "Default" } prepend variantSets = "Emissive" ) { def Sphere "Sphere" { } variantSet "Emissive" = { "Daytime" { } "Default" { } } }
Correct Answer: C
The sphere is not visible because the prim wall_a_inst is marked instanceable = true and also has a variant set, which is a composition arc. NVIDIA's Learn OpenUSD instancing module states that "Instancing is driven by your composition arcs," and explains that instanceable prims generate implicit prototypes from composed scenegraph content provided through those arcs. It also states that variant sets participate in composition and that variant selections are evaluated when OpenUSD determines which implicit prototypes to create. In this layer, the Sphere is authored as a local child of the instanceable prim, but it is outside the selected "Emissive" variant. Since the selected variants "Default" and "Daytime" contain no sphere definition, the composed prototype for the instance contains no visible sphere. This is an instancing/composition issue, not a visibility-purpose issue and not a material-binding issue. Option A is incorrect because the USDA does not mark the sphere as guide geometry. Option B is incorrect because missing materials would not remove the sphere from the scenegraph. Option C correctly identifies that local child opinions outside the relevant composition arc are not contributing to the instanced scenegraph. This aligns with Content Aggregation # Asset Modularity and Instancing # Scenegraph Instancing, Variant Set Refinement, and Composition Arcs .