Add UFE path handling and utilities to support paths that identify point instances of a PointInstancer #1027
Conversation
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
mattyjams
commented
Dec 22, 2020
b458b52 to
5d6e227
Compare
5d6e227 to
7aebebd
Compare
|
Just rebased to resolve conflicts from the merge of #1039. |
ppt-adsk
reviewed
Jan 14, 2021
7aebebd to
32299f7
Compare
32299f7 to
9c50995
Compare
ppt-adsk
reviewed
Jan 20, 2021
…nd accessor for retrieving it Additional class documentation was added to describe the handling of point instances generated by PointInstancer prims, and how their semantics differ between USD and UFE.
…for a USD path If an instanceIndex is provided, the path segment for a point instance with that USD path and index is returned.
Because of the conflicting Python bindings between USD and UFE, we cannot return an instance of Ufe::PathSegment and instead must return the path segment as a string.
…ce index tail component from a Ufe::Path
…ePathToPrim() This will become relevant when the Viewport 2.0 render delegate appends an instance index path component to the UFE paths of PointInstancer prims in order to uniquely identify point instances. Trying to get the PointInstancer prim using the full path would fail, since the path includes the instance index component.
…epresenting point instances
For UFE versions before version 2, the work that was previously local to ufePathToPrim() to turn a std::string into a Ufe::Path was broken out into a helper function so that it could be shared between ufePathToPrim() and ufePathToInstanceIndex().
Because of the conflicting Python bindings between USD and UFE, we cannot receive or return instances of Ufe::Path and instead must use strings.
When a scene item represents a point instance, its Ufe::Path will end with a path component that is all digits representing the instance index (e.g. ".../PointInstancer/12345"). Point instances are generated by a PointInstancer prim based on data members on the PointInstancer and the prototype being instanced. There is otherwise no direct mapping of a point instance to any location in USD namespace. As a result, we treat point instances as child-less in UFE. For the same reason, point instances don't really have a "parent" in USD either, but in UFE we consider the PointInstancer prim the "parent" of a point instance it generated. This allows pick-walking from a point instance up to the PointInstancer prim that generated it. Note that the reverse is *not* true. The point instances generated by a PointInstancer cannot be retrieved by querying the PointInstancer for its children.
…ndling of point instances
9c50995 to
e9de85a
Compare
ppt-adsk
approved these changes
Jan 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR represents all of the plumbing necessary to work with UFE paths that identify individual instances of a
PointInstancerprim. It was distilled from #936 as well as some offline discussion. This PR stops short of making the Viewport 2.0 render delegate point instance selection-aware. That and manipulation will be added in subsequent PRs.The path to a point instance is constructed by simply appending the instance's
instanceIndexas a final component of the USDUfe::PathSegment, for example:/PointInstancer/12345. This is a valid path in UFE, but it is not a validSdfPath, since all elements of anSdfPathneed to be C identifiers and cannot start with a digit. We take advantage of this fact to quickly identifyUfe::Pathsto point instances and avoid having to do too much string manipulation. Utilities were added and wrapped to Python to handle adding or stripping theinstanceIndexcomponent when necessary. All of the path manipulation specifics about how point instance paths are constructed or parsed should be consolidated inlib/mayaUsd/ufe/Utils.cpp, so if we choose to change the path representation or apply a similar pattern to other prim component types (e.g. individual points/edges/faces of aMeshprim), we should hopefully only have one place we'll need to change it.Test USD files and Maya scenes with proxies that use them were added at three different scales: 14 instances, 7,000 instances, and 70,000 instances. The test added in this PR only makes use of the 14 instance sample, but the imaging and manipulation tests to be added in subsequent PRs will also use the large scale samples.