When a process changes the topology or point count of a mesh, it must also update dependent geometric data whose interpolation depends on the mesh’s element counts. OpenUSD primvars are not arbitrary side data; their array sizes and ordering are tied to interpolation mode. For mesh vertex interpolation, the primvar array provides one element for each point, in the same order as the mesh points array. For faceVarying interpolation, the primvar array follows the flattened faceVertexIndices order.

Option B is correct because subdividing or replacing points changes the data contract for non-constant primvars such as display color, UVs, normals, or other interpolated values. The process authoring the stronger points opinion must ensure that related primvars remain valid for the resulting geometry. Option A is incorrect because points is an attribute and can be overridden by stronger opinions; render-time subdivision through subdivisionScheme is a separate mechanism. Option C is incorrect because USD composition does not automatically resize or reinterpret primvar arrays to match newly authored points. This aligns with Data Modeling → Meshes, Points, Primvars, Interpolation, Topology, and Geometry Validity .

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 .

Unexpected property values usually come from value resolution, time remapping, or competing authored opinions. NVIDIA’s Learn OpenUSD value-resolution guidance explains that OpenUSD determines the final value of a property by looking through the ordered sources that contribute information, from strongest to weakest, and resolving the relevant authored data according to property type. ( docs.nvidia.com )

Option B is correct because layer offsets retime animated data across composition arcs such as references, payloads, and sublayers. If an offset or scale is wrong, a time-sampled property can evaluate at an unexpected source time, producing an apparently incorrect value. Option D is correct because multiple layers can author opinions on the same property, and the stronger opinion wins according to composition and value-resolution rules. NVIDIA’s strength-ordering guidance emphasizes that LIVERPS and layer-stack ordering determine which opinions are considered strongest. ( docs.nvidia.com )

Option A is not a primary cause by itself; connections may affect shader or node-network behavior, but “too many” connections does not inherently change USD property resolution. Option C is incorrect because .usda, .usdc, and .usd are storage encodings for layers, not different composition semantics. This aligns with Debugging and Troubleshooting → Value Resolution, Layer Offsets, Composition Strength, and Property Stacks .