-
Notifications
You must be signed in to change notification settings - Fork 214
EMSUSD-1555 Duplicating a Physical Sky to USD using Arnold options is missing data #3919
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
|
IDK if we would not be better off squashing all those commits into a single one? Maybe creating a new PR? |
@pierrebai-adsk I can do that. Out of curiosity, can't we squash during merge? |
lib/mayaUsd/fileio/jobs/writeJob.cpp
Outdated
| } | ||
|
|
||
| // Collect extra prims paths from chasers | ||
| for (const SdfPath& path : chaser->GetExtraPrimsPaths()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is a way to insert a range in C++ std::vector? Not super important.
When "Duplicate as Usd data" is select from the context ops menu on a maya object, we only translate to Usd the selected maya object.
This can be a problem when there are extra prims created by a chaser, for example. Those would be discarded.
With those changes, we allow the users to register the path for those extra prims created so that it can be queried when merging the maya object into Usd.