Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix UsdGeomPointInstancer ComputeExtents when prototypes are under an over #3396

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

cbillingham
Copy link

@cbillingham cbillingham commented Nov 4, 2024

Description of Change(s)

Allow UsdGeomBBox to take in a custom prim traversal predicate so that UsdGeomPointInstancer can compute bboxes of prototypes that exist under an over as described by the docs

Fixes Issue(s)

#3395

Checklist

…over

Fixes PixarAnimationStudiosGH-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.
@@ -439,7 +465,7 @@ UsdGeomBBoxCache::_ComputeBoundWithOverridesHelper(
}

GfBBox3d result;
UsdPrimRange range(prim);
UsdPrimRange range(prim, _primPredicate);
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was a bit unsure about this change. Looking at where this is called, it seemed to me that this should be following the same predicate as the other traversals, but it was not before. Let me know if I need to roll this back

@cbillingham
Copy link
Author

I took a stab at addressing this, but let me know if I went down the the wrong path

@jesschimein
Copy link
Collaborator

Filed as internal issue #USD-10392

❗ Please make sure that a signed CLA has been submitted!

@jesschimein
Copy link
Collaborator

/AzurePipelines run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@cbillingham
Copy link
Author

Filed as internal issue #USD-10392

❗ Please make sure that a signed CLA has been submitted!

I should have one sent in Feb 2021. Let me know if I need to send in a new one

@pixar-oss
Copy link
Member

Thank you for flagging that! We have your CLA on file; so sorry for the confusion!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants