You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting up a UsdGeomPointInstancer with prototypes defined under an over specified prim (a structure suggested by the docs), the bounding box computed by the registered ComputExtents plugin does not correctly compute prototype bounding boxes. Similar to #1436 which fixed this issue for the usdImaging adapter, I think the compute extents plugin should be updated to allow traversal of prototypes that are under an over.
Steps to Reproduce
Save the following into a pointinstancer_extents.usda layer
There's some workarounds for this that resolve the problem. You can make sure the prototypes are actually defined by defining the Prototypes parent. You can make sure there is extents authored on your UsdGeomPointInstancer prim. But it would be nice if the ComputeExtents plugin supported this suggested workflow without the need for these workarounds.
System Information (OS, Hardware)
Linux (AMD Ryzen 5 2600, NVIDIA GTX 1060)
Usd v24.11
The text was updated successfully, but these errors were encountered:
…over
FixesPixarAnimationStudiosGH-3395. As described at
https://openusd.org/docs/api/class_usd_geom_point_instancer.html#UsdGeomPointInstancer_protoProcessing
PointInstancers can define prototypes under a parent prim specified as an over.
The ComputeExtent plugin registered for PointInstancer was not correctly computing
prototype bboxes in this case. This extends UsdGeomBBoxCache to allow for a custom
prim predicate to be passed, which the updated ComputeExtent plugin takes advantage of
to traverse prototype prims in this case.
Description of Issue
When setting up a UsdGeomPointInstancer with prototypes defined under an over specified prim (a structure suggested by the docs), the bounding box computed by the registered ComputExtents plugin does not correctly compute prototype bounding boxes. Similar to #1436 which fixed this issue for the usdImaging adapter, I think the compute extents plugin should be updated to allow traversal of prototypes that are under an over.
Steps to Reproduce
pointinstancer_extents.usda
layerWorkarounds
There's some workarounds for this that resolve the problem. You can make sure the prototypes are actually defined by defining the Prototypes parent. You can make sure there is extents authored on your UsdGeomPointInstancer prim. But it would be nice if the ComputeExtents plugin supported this suggested workflow without the need for these workarounds.
System Information (OS, Hardware)
Linux (AMD Ryzen 5 2600, NVIDIA GTX 1060)
Usd v24.11
The text was updated successfully, but these errors were encountered: