The metadata automatically handled by composition is timeCodesPerSecond . NVIDIA’s Learn OpenUSD units guidance states the distinction directly: timeCodesPerSecond is automatically reconciled during composition, while metersPerUnit, kilogramsPerUnit, and upAxis are not. Pipelines must therefore explicitly handle geometric orientation, spatial scale, and physics mass-unit mismatches when assembling assets from different sources.
Option A is correct because OpenUSD can automatically scale time-sampled values across sublayer, reference, and payload arcs when source and target layer stacks use different timeCodesPerSecond values. OpenUSD’s time-value documentation explains that when a targeted layer specifies timeCodesPerSecond, TimeCode coordinates and animated value coordinates are automatically scaled into the time frame defined by the source layer’s timeCodesPerSecond.
Options B , C , and D are incorrect because USD does not automatically rotate geometry for different upAxis, scale geometry for different metersPerUnit, or convert physics mass semantics for different kilogramsPerUnit. Those require pipeline conventions, validation, or corrective transforms. This aligns with Pipeline Development → Stage Metadata, Units, TimeCode Scaling, Asset Assembly, and Pipeline Validation .
