NVIDIA NCP-OUSD - OpenUSD Development

The most essential composition arc for components in a model hierarchy is the payload . NVIDIA’s Learn OpenUSD glossary describes payloads as composition arcs similar to references, but with deferred loading for scalability, and specifically notes that payloads are typically added to component asset root prims for efficient scalable composition. ( docs.nvidia.com )

Option A is correct because component models act as the leaf or pruning boundary of the model hierarchy. NVIDIA’s model-kind guidance explains that the model hierarchy is designed to prune traversal at the component boundary, and that component models cannot contain other component models as descendants. ( docs.nvidia.com ) Payloads reinforce that design by allowing large component contents to remain unloaded until needed, improving stage-opening performance and enabling scalable aggregation of large scenes.

Option B is incorrect because inherits are mainly for reusable class-style opinions. Option C is useful for alternatives such as LODs or looks, but it is not the essential component-loading mechanism. Option D is a weaker composition mechanism used for specialization and fallback-style refinement. This aligns with Content Aggregation → Asset Structure, Model Hierarchy, Components, Payloads, and Scalable Scene Assembly .

Custom attributes in OpenUSD are user-defined properties authored on prims to store additional typed data beyond predefined schema attributes. NVIDIA’s Learn OpenUSD material states that custom attributes can hold “numeric values, strings, or arrays,” and that custom attributes are created with UsdPrim::CreateAttribute(), where Sdf.ValueTypeNames represents the attribute type. NVIDIA’s OpenUSD data type reference lists Asset with the USDA value type token asset, and StringArray with the USDA token string[], making asset paths and string arrays valid attribute value types.

Option B is correct because asset path values are represented through the asset value type and are commonly used for resource references such as textures or external asset identifiers. Option C is correct because string[] is a valid array value type. Option A is incorrect because USD does not have a native struct attribute type; NVIDIA recommends namespace-prefixed attributes for mapping grouped or compound fields. Option D is incorrect in this context because dictionaries are associated with metadata/customData patterns, not ordinary typed custom attributes. This aligns with Customizing USD → Custom Properties, Sdf.ValueTypeNames, Namespaced Attributes.

The geometric attribute that should be kept in sync is extent. In OpenUSD, point position values describe the authored point locations for point-based geometry, while extent represents the local-space geometric range or bounding box of a boundable primitive. The OpenUSD UsdGeomBoundable specification describes extent as a three-dimensional range measuring the authored gprim in its own local space, and states that if extent is authored, it should be authored at every time sample where geometry-affecting properties are authored to ensure correct evaluation.

Option C is correct because changing point positions can change the object’s local bounds. If the authored extent is not updated, downstream systems may compute incorrect framing, culling, selection bounds, or bounding-box display. Option A is incorrect because purpose classifies geometry for render, proxy, guide, or default visibility categories. Option B is incorrect because xformOps describe transform operations on the prim, not the local geometric bounds derived from point positions. Option D is incorrect because faceVertexIndices describes mesh topology, not the bounding range. This aligns with Data Modeling → Geometry Attributes, Point-Based Geometry, Boundable Prims, Extent, and Time-Sampled Geometry .

The Python snippet authors a reference opinion directly on the prim /refSphere in a new anonymous root layer. Usd.Stage.CreateInMemory() creates an empty stage, and OverridePrim("/refSphere") authors an over prim spec because no concrete type is being defined. The call refSphere.GetReferences().AddReference("./HelloWorld.usda") adds a reference composition arc to that same prim, so the root layer serializes the opinion as prepend references = @./HelloWorld.usda@.

Option C is correct because ExportToString() prints the authored contents of the root layer, not the fully expanded composed result of the referenced asset. The referenced HelloWorld.usda layer has defaultPrim = "hello", so omitting a prim path in AddReference() targets the referenced layer’s default prim. NVIDIA’s reference documentation explains that a reference may omit the prim path when the referenced layer has a default prim, and the target prim will be resolved from that metadata. ( docs.nvidia.com )

Option A is incorrect because the reference is not authored under /hello; /hello exists only inside the referenced file. Option B is incomplete because it omits the reference metadata. This aligns with Composition → References, Default Prim, Layer Authoring, and Exported Layer Opinions .

The valid imageable purpose values among the options are guide , render , and proxy . NVIDIA’s Learn OpenUSD glossary describes purpose as a UsdGeomImageable attribute used to classify geometry into visibility categories that can gate traversals such as rendering or bounding-box computation. It lists purpose values including default , render , proxy , and guide . ( docs.nvidia.com )

Option A is correct because guide is used for guide or helper geometry that should generally appear only when an interactive application has been asked to display guides. Option C is correct because render identifies final-quality render geometry. Option E is correct because proxy identifies lightweight preview or proxy representation. OpenUSD’s UsdGeomImageable documentation confirms the allowed values as default, render, proxy, and guide. ( openusd.org )

Option B is incorrect because lights are represented through lighting schemas, not as an imageable purpose token. Option D is incorrect because materials and shading assignments are represented through UsdShade schemas and relationships, not through imageable purpose. This maps to Visualization → Imageable Purpose, Render/Proxy/Guide Geometry, Hydra Traversal, and Display Filtering .

The most plausible cause is that the two environments are resolving asset identifiers differently. NVIDIA’s Learn OpenUSD glossary defines asset resolution as the process of translating an asset path into the actual location of a consumable resource, and identifies ArResolver as the plugin point that can be customized to resolve assets through site logic, databases, or version-control systems.

Option C is correct because the same authored USD layer can contain references, payloads, textures, or other asset-valued paths that are resolved at runtime. If one user’s resolver context maps @character.usd@ to version 12 while another maps it to version 15, or if one environment cannot resolve a dependency at all, the composed stage can differ. This can manifest as missing geometry, stale geometry, missing materials, or unresolved payloads. References and payloads are composition arcs that bring external scene description into the stage, so resolution differences directly affect what data is available for composition.

Option A is incorrect because USD does not change composition semantics based on available memory. Option B is not the primary explanation here; instance prototypes are derived from composed instance data, but the root problem described is inconsistent asset resolution. This aligns with Debugging and Troubleshooting → Asset Resolution, References, Payloads, Resolver Contexts, Missing Dependencies .

The correct answer is list ops . API schemas are not encoded as a simple boolean flag on a prim. Instead, applied API schemas are stored in the apiSchemas metadata as token-valued listOp data. OpenUSD’s UsdPrim::ApplyAPI() documentation states that applying an API schema stores the schema name by adding it to the token-valued listOp metadata apiSchemas. Its RemoveAPI() documentation states that removing an API schema authors an explicit deletion of that schema name from the same listOp metadata.

This is what enables non-destructive removal in stronger layers. A weaker layer may apply an API schema, while a stronger layer can delete that schema token from the composed list without modifying the weaker source layer. NVIDIA’s OpenUSD glossary describes list editing as sparse ordered-list composition using operations such as prepend, append, delete, and explicit replacement, allowing stronger layers to modify lists contributed by weaker layers.

Option B is incorrect because arrays store values but do not provide list-edit composition semantics. Option C is incorrect because booleans cannot represent ordered additive and subtractive composition. This aligns with Customizing USD → API Schemas, apiSchemas Metadata, List Editing, and Non-Destructive Layering .

Option A is correct because local opinions are the strongest opinions in USD composition strength ordering. NVIDIA’s Learn OpenUSD strength-ordering guide describes LIVRPS, now also written as LIVERPS with relocates included, as the ordered set of composition operations used to determine which opinions win. The order is strongest to weakest: local , inherits, variant sets, relocates, references, payloads, and specializes.

When debugging an unexpected value, local opinions should be inspected first because a directly authored opinion in the local layer stack can override opinions arriving through other composition arcs. NVIDIA’s tracing guidance also highlights how complex composition debugging becomes when many prims, properties, layers, and arcs contribute competing opinions.

Option B is false because specializes arcs are not unoverrideable; they are the weakest fallback-style opinions in the composition order. Option C is false because references are stronger than payloads in LIVRPS/LIVERPS ordering, so checking payloads before references reverses the standard diagnostic priority. This aligns with Debugging and Troubleshooting → LIVERPS Strength Ordering, Local Opinions, References, Payloads, Specializes, and Composition Diagnostics .

OpenUSD file format plugins belong under the Data Exchange topic because they expand how USD participates in interchange workflows. Their purpose is to allow OpenUSD to read, interpret, and in some cases write data using formats beyond the native USD file types such as .usd, .usda, .usdc, and .usdz. Through these plugins, external file formats can be exposed to USD as layers and can participate in composition arcs such as references, payloads, and sublayers. This allows pipelines to integrate heterogeneous asset sources while still using USD’s scene description model, composition engine, and layer-based workflows.

Option A is correct because it directly identifies the function of file format plugins: extending OpenUSD functionality for reading and writing various file formats. Option B is incorrect because visualization is only one possible downstream use of exchanged data, not the purpose of the plugin system. Option C is incorrect because translation between formats does not inherently guarantee lossless preservation of every schema, opinion, or semantic construct. Option D is incorrect because compression is not the primary role of file format plugins. This aligns with the NVIDIA OpenUSD Development Study Guide topic Data Exchange , especially file formats, connectors, and plugin-based interoperability.