Maya Scene exports do not default to including nodes that not children of members #71
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.
Changelog Description
On Maya scene exports only include the relevant history for the selected nodes downstream and upstream and not upstream, and also their downstream descendant children.
Additional info
Note: This may affect maya scene exports, camera rig exports and layout exports. However, I do feel this is a way more sensible default behavior on exports with construction history enabled.
With this change, if you have a hierarchy like:
And
obj1
is inside the instance then after this PRobj2
is not included.Before this PR all other descendents from upstream groups would be included, regardless of whether they were "inputs" to the
obj1
.After this PR, if
obj2
is an input connection toobj1
(e.g. there are active constraints drivingobj1
or some other connections driving it) thenobj2
will still be included.As such, only objects actively contributing to members of the instance will still be included in the output.
Testing notes:
obj1
- it should not includeobj2
obj2
toobj1
(e.g. translate connection)obj2
should also be included inobj2
.obj1
transforms.