NCP-OUSD practice question 9 of 10

A key responsibility of the pipeline is to assemble content that may have divergent stage metadata across layer stacks. Which of these metadata is automatically handled by composition when they diverge across layer stacks?

Full set: 71 questions
Answer options
A: timeCodesPerSecond Correct answer
B: upAxis
C: kilogramsPerUnit
D: metersPerUnit
Correct Answer:
A. timeCodesPerSecond
Explanation

The USD core automatically converts authored time samples from referenced layers so that all samples on the composed stage are expressed in the root layer’s timeCodesPerSecond. Divergent axis or unit metadata (upAxis, metersPerUnit, kilogramsPerUnit) are merely authored values; composition does not reconcile them—clients must handle any mismatch.

Why Incorrect

B. upAxis differences are not reconciled; applications must re-orient geometry.
C. No automatic mass-unit scaling is performed; values remain as-authored.
D. metersPerUnit is passed through; it is up to clients to scale geometry.

References

1. Pixar USD “Stage Metadata”, §“timeCodesPerSecond – automatic conversion across layer stacks”.

2. USD Geometry Guide, §“Units and Up Axis” – note on lack of automatic conversion.

3. NVIDIA Omniverse Docs “Reference Best Practices”, §2.3 warning on mismatched metersPerUnit/upAxis.

Scroll to Top