[usdMaya] Adding an option to put everything into a parent scope. #223
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
|
Filed as internal issue #147636. |
pmolodo
force-pushed
the
pr/export_parent_scope
branch
from
446b66a to
824494d
Compare
sirpalee
force-pushed
the
pr/export_parent_scope
branch
from
824494d to
3999403
Compare
sirpalee
force-pushed
the
pr/export_parent_scope
branch
from
3999403 to
137e7bb
Compare
|
Note, the PR was updated to work with the recent exportParam changes for the shader exporter and I added tests. |
pixar-oss
added a commit
that referenced
this pull request
Mar 19, 2018
[usdMaya] Adding an option to put everything into a parent scope.
AdamFelt
pushed a commit
to autodesk-forks/USD
that referenced
this pull request
Apr 16, 2024
Regular update of adsk/dev branch from pixar dev
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.
Description of Change(s)
This adds an option to the maya usd export, that will place all the created nodes under a user-named Scope. It's useful because usd's referencing system works on a single top-level node - so if you're exporting a maya scene that has multiple top-level nodes, and want the entire scene to be easily referenced via USD, you need to place it all under one top node.
We're already using this in several places through our pipeline, and think other facilities would likely find it handy as well.
Included Commit(s)
Fixes Issue(s)