When USD computes the position of a PointInstancer instance, what additional position-related information is used...

A PointInstancer instance position is not computed from the per-instance positions array alone. NVIDIA’s Learn OpenUSD point-instancing lesson explains that authored positions are in the local coordinate space of the PointInstancer. For the final world-space transform, USD combines multiple transforms: first the prototype root transform , then the instance-specific transform components such as scales[i], orientations[i] , and positions[i], and finally the transform authored on the PointInstancer prim itself.

Option B is correct because it includes both additional transform sources that affect the resulting placement: the prototype root’s transform and the PointInstancer prim’s transform. This matters in production asset aggregation because prototypes may carry their own local placement or orientation, while the instancer prim may be moved, rotated, or scaled as a whole. Option A is incomplete because it incorrectly discards the prototype root transform. Option C is incorrect because it treats instance positions as isolated data and ignores the composed transform stack. This aligns with Content Aggregation → Asset Modularity and Instancing → PointInstancer, Prototype Roots, Instance Transforms, and Transform Composition .