-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adjust Hydra model schemas to address a recent performance
regression involving UsdImaging Native Instance Aggregation. Aggregation uses Hydra model schemas as part of the aggregation key. Originally this only covered UsdGeomModelAPI, which holds fields related to draw mode that must be considered when determining instance aggregation. Recently, to support other model-related capabiliites, I added UsdModelAPI to this Hydra model schema. The reasoning at the time was to align with how the USD API schemas both use the same "model:" namespace for their USD attributes. However, the "modelPath" portion of this defeated aggregation effectiveness, because otherwise-equivalent native instances might have distinct modelPaths. To address this, we first considered removing "modelPath", which would fix the aggregation issue. Clients wanting to find the model path would simply need to traverse the scene index to find the prim where the closest model schema data source was introduced. However, further discussion lead to considering that we should keep the UsdModelAPI and UsdGeomModelAPI representations in Hydra schemas distinct. This change implements that, introducing a GeomModel schema in Hydra. (Internal change: 2303046)
- Loading branch information
Showing
14 changed files
with
614 additions
and
402 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.