NCP-OUSD OpenUSD Development Questions and Answers

The correct exporter behavior is to generate sparse overrides that represent only the authored contribution of the current workstream. In OpenUSD data exchange workflows, an exporter should not blindly rewrite the full imported asset when the intent is to preserve collaborative, non- destructive editing. Instead, the exporter should author only the changes required to express the current application’s contribution: modified prims, newly added prims, changed attributes, relationships, metadata, or other authored opinions.

Option A is correct because an over is specifically used to contribute opinions to an existing prim without redefining the entire prim structure. This allows the exported layer to sit above the source asset in a layer stack and override only the relevant data. Option B incorrectly equates sparsity with splitting each prim into separate referenced layers; USD sparsity is achieved by authoring minimal opinions, not by unnecessary layer fragmentation. Option C is incorrect because exporting full definitions for every prim and property would duplicate unchanged data, reduce clarity, and undermine USD’s composition-based collaboration model. This maps to the NVIDIA OpenUSD Development Study Guide topics Data Exchange, especially exporter design, data transformation, sparse authoring, and collaborative layer-based workflows.

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 .

An authored opinion may be valid and still not appear in the final composed stage because USD resolves competing opinions by strength ordering . NVIDIA’s Learn OpenUSD strength-ordering guide explains that, for each prim and property, the composition engine evaluates opinions from contributing layers and composition arcs using LIVRPS, giving precedence to stronger opinions when conflicts occur. It also states that stronger layers can override or add to data defined in weaker layers, enabling non-destructive edits and overrides.

Option D is correct because a weaker layer’s opinion can be hidden by a stronger opinion authored elsewhere in the layer stack or through a stronger composition context. This is a normal result of USD composition, not an error. Option A is incorrect because editability controls whether a layer can be modified, not whether its authored opinions can contribute during composition. Option B may indicate invalid or poorly modeled data, but schema choice alone is not the general reason an opinion loses. Option C can be a troubleshooting case for missing referenced content, but the question asks why opinions from a composed layer may not take effect. This aligns with Composition → Layer Stacks, Opinion Strength, LIVRPS, Value Resolution, and Non-Destructive Overrides .

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 .

A well-designed model kind hierarchy is important because it gives tools a reliable, high-level “table of contents” for a complex stage. NVIDIA’s Learn OpenUSD guide explains that model hierarchy is designed to prune traversal at a relatively shallow point in the scenegraph. Without model hierarchy, traversal may need to pass through all prims in a scene, which can be costly. The key pruning point is the component model boundary: ancestors of components participate in the model hierarchy, while descendants are outside the model hierarchy.

Option A is correct because pipeline tools can use kind metadata to find meaningful asset boundaries, traverse assemblies and groups efficiently, and avoid descending into every geometric or implementation-level prim. Option B is inaccurate because kind metadata is not primarily a composition-engine optimization mechanism; USD composition resolves scene description based on composition arcs and strength ordering. Option C is also not the primary purpose. Avoiding duplication is addressed more directly by references, payloads, instancing, inherits, specializes, and asset-structure reuse. This aligns with Content Aggregation → Asset Structure → Model Hierarchy → Model Kinds, Components, Assemblies, Groups, and Efficient Traversal .

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.

An inherit arc lets prims receive scene description from a source prim, commonly a class prim, and enables modifications to that inherited source to broadcast to all inheriting prims in the relevant composition context. NVIDIA’s Learn OpenUSD inherits lesson states that after an inherit arc is established, the source prim and its descendants can be modified in a stronger layer, including across references, and those modifications are broadcast and applied to all prims that inherit it. ( docs.nvidia.com )

Option B is correct because it captures the defining production use: central refinement of many related prims without editing every instance individually and without modifying the original referenced asset globally. NVIDIA’s strength-ordering lesson also describes inherits as the arc that allows opinions on one source prim to affect all prims that author an inherit arc to that source. ( docs.nvidia.com )

Option A is incorrect because inherits are not simply a replacement for references; they solve broadcast refinement and reusable opinion-sharing problems. Option C is conceptually adjacent but imprecise: inherits may resemble inheritance patterns, but USD inherit arcs are composition mechanisms, not an object-oriented programming system. This aligns with Composition → Inherits, Class Prims, Broadcast Refinement, Encapsulation, and LIVERPS Strength Ordering .

Option C correctly describes the relationship between interpolation and element counts for mesh normals and normal-like primvars. In UsdGeomMesh, vertex interpolation provides one value per mesh point, while faceVarying interpolation provides one value for each face-vertex, meaning each corner of each face can carry its own value. This distinction is essential for representing smooth normals, hard edges, UV seams, and other discontinuities across faces. OpenUSD’s UsdGeomMesh documentation defines vertex interpolation as one element per point and faceVarying interpolation as one element for each face-vertex that defines the mesh topology.

Option A is incorrect because authored normals do not always have to match the number of points; the required count depends on the normals interpolation. Face-varying normals, for example, require one value per face corner rather than one per point. Option B is incorrect because normals should generally not be authored on subdivision meshes; subdivision algorithms define their own normals. OpenUSD notes that authored normals should only be used for polygonal meshes where subdivisionScheme = "none".

This aligns with Data Modeling → UsdGeomMesh, Normals, Primvar Interpolation, Vertex Data, Face-Varying Data, and Polygonal Mesh Representation .

Options B and C are correct. The official OpenUSD layer-format conversion tutorial states that usdcat can convert between layer formats using the -o option and an output filename with the desired extension. For example, converting text .usda to binary .usdc is performed with a command such as usdcat -o NewSphere.usdc Sphere.usda.

Option C is also correct because .usd is an extension that can hold either text or binary USD data. The same OpenUSD tutorial explains that a .usda or .usdc file can be converted to .usd without changing the underlying format by simply renaming the file; USD detects the actual format when opening it.

Option A is not correct in this context because .usdz is a package/archive format, and the OpenUSD toolset identifies usdzip, not usdcat, as the utility for creating .usdz packages containing USD assets. Option D is incorrect because renaming a text .usda file to .usdc does not convert it into USD’s binary crate representation. This aligns with Data Exchange → USD File Formats, usdcat, usdzip, USDA, USDC, USD, and USDZ Packaging .

The visibility opinions that must be updated are on World , Scope , and Cube . In OpenUSD, visibility is hierarchical and pruning. UsdGeomImageable defines the visibility attribute with allowed values inherited and invisible; effective visibility is computed from the most ancestral authored invisible opinion. The OpenUSD API further states that MakeVisible() may need to override ancestor visibility and hide sibling branches to preserve the intended result. ( openusd.org )

In the given scene, /World is explicitly invisible, so the entire subtree is invisible regardless of descendants. /World must therefore be changed to visible behavior, typically visibility = "inherited". /World/Xform/Scope is also explicitly invisible, so Scope must also be changed to inherited to allow its children to be evaluated as visible. Once those ancestor invisibility opinions are removed, both Sphere and Cube would become visible by inheritance. To make only the sphere visible, the Cube must receive an explicit visibility = "invisible" opinion. The sphere does not require an authored visibility opinion because it becomes visible through inheritance. This aligns with Visualization → UsdGeomImageable, Visibility, Hierarchical Pruning, and Effective Visibility Computation .

ETL is useful for USD data exchange because it separates the problem into disciplined phases instead of forcing extraction, interpretation, optimization, and client-specific restructuring into one converter step. NVIDIA’s Learn OpenUSD data exchange guidance describes a two-phase approach, extract and transform, inspired by ETL. The extract phase should translate source data to OpenUSD as directly as possible, mapping source concepts to USD concepts to preserve the integrity and structure of the original data. The transform phase then applies optional changes such as user export options, content-structure changes, and optimizations for workflow or client performance.

Option B is correct because this separation of concerns makes converters easier to maintain, test, and adapt. Option D is correct because the pattern preserves source fidelity first, then permits controlled tailoring for specific downstream needs. Option A is incorrect because NVIDIA explicitly notes that data exchange is typically lossy and not every data model maps directly. Option C is incorrect because the guide states there is no single content structure suitable for every organization or workflow. This aligns with Data Exchange → Two-Phase Data Exchange, Data Extraction, Data Transformation, Export Options, and Pipeline Adaptability .

A reference composition arc brings scene description from another asset into the prim where the reference is authored, then combines that referenced data with local opinions on the destination prim. NVIDIA’s Learn OpenUSD references guide states that when a prim is composed through a reference arc, USD first composes the layer stack of the referenced prim, adds the resulting prim spec to the destination prim, and then applies overrides or additional composition arcs from the destination prim.

Option D is correct because /Root/Chair receives the composed contents of chair.usda, while the locally authored xformOp:scale = (1.5, 1.5, 1.5) remains part of the destination prim’s stronger local opinions. If the referenced chair asset also authored a corresponding scale opinion on the same property, the local opinion would win by standard USD strength ordering, where stronger opinions override weaker ones non-destructively.

Option A is incorrect because references are not bidirectional synchronization links; editing the referencing layer does not automatically modify chair.usda. Option B is too narrow because references compose all targeted scene description, not only variant sets. Option C is incorrect because a reference does not discard local opinions. This aligns with Composition → References, Local Opinions, Layer Strength, and Non-Destructive Overrides .

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 valid asset-structure principles are Legibility , Navigability , and Modularity . NVIDIA’s Learn OpenUSD asset-structure guide identifies four principles of scalable asset structure: Legibility , Modularity , Performance , and Navigability . It defines legibility as making an asset structure easy to understand and interpret, modularity as enabling flexibility and reuse, and navigability as making it easy for users to find and access the features and properties they need. ( docs.nvidia.com )

Option A is correct because clear names, organization, and intent make assets easier to troubleshoot, exchange, and maintain. Option C is correct because downstream users and tools must be able to locate meaningful prims, properties, variants, payloads, and interfaces efficiently. Option D is correct because reusable modular components support parallel workstreams and scalable aggregation. Option B is incorrect because redundancy is generally discouraged; NVIDIA’s modularity guidance emphasizes reuse and avoiding duplicated data. Option E is incorrect because “compressability” is not one of the stated principles. This aligns with Content Aggregation → Asset Structure Principles → Legibility, Modularity, Performance, Navigability .

A conceptual data mapping document primarily records how concepts and data from a source format map into OpenUSD concepts, schemas, prims, properties, and authored scene description. NVIDIA’s Learn OpenUSD Data Extraction lesson states that producing such a document is valuable because it serves as a data specification for extraction implementation, helps stakeholders set requirements and expectations, and helps developers understand which features are supported between two formats and what to expect from the extraction phase. ( docs.nvidia.com )

Option D is correct because the document is specifically about translation between OpenUSD and another data representation, such as a DCC format, interchange format, or custom application model. Option A is broader than the purpose of the document; an end-to-end workflow specification may include tools, review, publishing, validation, and delivery, while conceptual mapping focuses on data correspondence. Option B is also too narrow because content structure is only one possible mapped concept. Option C is incorrect because storage requirements are not the core concern. This aligns with Data Exchange → Data Extraction, Conceptual Data Mapping, Format Translation, and Converter Design .

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 exporter should validate and correct authored extent values on every exported UsdGeomBoundable prim. The extent attribute is the local-space bounding range of the authored geometric primitive, and if it is authored incorrectly, clients that trust the authored extent can display oversized or inaccurate bounds. NVIDIA’s asset-requirements documentation states that “Boundable geometry primitives should have valid extent values,” and its compliance guidance says to author extent for boundable geometry and compute it at time samples where geometry-affecting attributes change. ( docs.omniverse.nvidia.com )

Option B is correct because it preserves the intended best-fit bounds and works consistently for any exported boundable prim. Option A is unreliable as an export strategy: OpenUSD may compute extent through registered compute functions when no extent is authored, but this can be expensive and is not a substitute for correct exported data. The OpenUSD UsdGeomBoundable documentation strongly encourages proper authoring of extent. ( openusd.org ) Option C is incorrect because extentsHint is not the replacement for per-primitive boundable extent. Option D is unrelated to geometric bounds. This aligns with Data Exchange → Validation, Geometry Export, Boundable Extents, and Data Quality .

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 .