NCP-OUSD practice question 1 of 10

Considering the following scene description: def "ParkingLot" { def "Car_1" ( instanceable = true references = @Car.usd@ ) { } def "Car_2" ( instanceable = true references = @Car.usd@ ) { } } Disabling the instanceable metadata on the prim at path /ParkingLot/Car_2 by setting it to false has the following effects: Choose two.

Full set: 71 questions
Answer options
A: Other prims using the same prototype, such as /ParkingLot/Car_2, will also get their instanceable metadata disabled.
B: Existing opinions in a local layer from the root LayerStack targeting a child of /ParkingLot/Car_1 will take effect.
C: Existing opinions in a local layer from the root LayerStack targeting a child of /ParkingLot/Car_1 will be ignored. Correct answer
D: Recomposition will be triggered from the hierarchy starting at /ParkingLot/Car_1. Correct answer
Correct Answer:
C. Existing opinions in a local layer from the root LayerStack targeting a child of /ParkingLot/Car_1 will be ignored.; D. Recomposition will be triggered from the hierarchy starting at /ParkingLot/Car_1.
Explanation

Turning instanceable off on /ParkingLot/Car2 removes it from the shared prototype, forcing USD to recompute instancing. Car1 stays instanceable, so opinions targeting its children remain suppressed, while recomposition is triggered for any prims whose prototype membership changes—including Car1 via the prototype map update.

Why Incorrect

A. Instanceable=false is applied only to the edited prim; it does not cascade to other instances.
B. Car1 remains instanceable; child opinions are still ignored, not activated.
D. (selected) Re-indexing the prototype set updates Car1, so recomposition starts there as the prototype owner.

References

1. Pixar USD “Instancing and Prototypes”, OpenUSD 24.03, §“Breaking an Instance”, para 2-4

2. NVIDIA Omniverse Docs, “Instanceable Metadata”, 2023.r2, §“Effect on Composition”

3. Pixar USD API, “UsdPrim::SetInstanceable()”, OpenUSD 24.03, note 3

Scroll to Top