OpenUSD Fundamentals and Data Modeling
Free NVIDIA-Certified Professional: OpenUSD Development practice — 6 questions on OpenUSD Fundamentals and Data Modeling, with explanations. No sign-up. Full 12-question mixed test →
A prim's Radius attribute has a default value of 1.0 authored in a weak sublayer, and a full set of time samples (frames 1-48) authored in a stronger sublayer of the same stage. Querying the stage at frame 24 for this attribute, what value does USD's value resolution return?
USD value resolution picks the strongest layer that has any opinion (default or time samples) for the attribute across the whole layer stack; if that strongest layer has time samples, they are used (with interpolation) and weaker layers' defaults are ignored entirely rather than merged.
In USD's LIVRPS composition strength ordering, which arc resolves with strength weaker than References but stronger than Specializes?
LIVRPS stands for Local, Inherits, VariantSets, References, Payloads, Specializes in decreasing strength order, so Payloads sit directly between References and Specializes.
A modeling artist needs per-face-vertex normals on a mesh so that faces sharing a vertex can each have a distinct normal value, producing visually hard edges at seams. Which primvar interpolation should be authored for the normals primvar?
faceVarying interpolation authors one value per face-vertex (per corner of each face), allowing adjacent faces sharing a topological vertex to have independent values, which is required for hard-edged normals.
On a stage, a prim is authored with kind = component, and that same prim has child prims authored with kind = group beneath it. When this stage is checked against USD's model-hierarchy conventions, what is the result?
USD's model-hierarchy convention treats component as a leaf-level model kind representing an indivisible asset; components are not expected to contain further group/component structure beneath them, so nesting a group under a component violates the hierarchy convention.
A prim needs two independent collections named 'render' and 'proxy', both built using UsdCollectionAPI. What is the correct way to author this in the prim's apiSchemas metadata?
UsdCollectionAPI is a multiple-apply API schema, meaning it can be applied more than once on the same prim as long as each application is distinguished by a unique instance name in the apiSchemas listOp metadata.
Which statement correctly distinguishes a USD relationship from an attribute connection?
Relationships are untyped, non-time-varying namespace objects used to reference other objects in the scene graph (e.g., material bindings), whereas connections are metadata on a typed attribute that redirect the attribute's value resolution to another attribute, commonly used for shading networks.
Ready for the real thing?
The full course: two full-length practice tests, video lessons for every exam domain, hands-on labs and detailed explanations.
$109.99 $34.99 with code FREETEST33 — valid through September 7.
Get my $34.99 deal →