-
We recently upgraded our MayaUsd plugin from v0.19 to v0.22 and I'm noticing some different behaviour in how the exportRoots flag is working. I used to be able to extract certain roots, while respecting a list of nodes requested for export. But this appears to no longer work properly. For example, here is what is in my maya scene:
My end goal is to output a usd file with the following hierarchy:
I used to be able to accomplish this with:
but now as of v0.22 it seems to be including the entire subtree beneath the roots, essentially ignoring the "nodes_to_export" list:
Is this a bug, or has this functionality changed? Using: |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
It appears that the way you have to do it now is actually select your I'd much prefer it if it still worked the way you're describing it used to work. Having to actually select things on an export feels gross to me. |
Beta Was this translation helpful? Give feedback.
-
I have logged this issue internally for the team to take a look at. I don't think this behavior should have changed. Thank you @g-k-s-g-k-s for the workaround though. |
Beta Was this translation helpful? Give feedback.
-
Created this issue from this discussion: #2968 |
Beta Was this translation helpful? Give feedback.
-
Thanks @santosd, much appreciated. I agree with @g-k-s-g-k-s, having to select stuff in order to export is not ideal. This is actually a longstanding gripe I have the exportSelected functionality in the cmds.file() command... Would be great to achieve this by passing a list of items, rather than relying on selection. But that's a battle for a different day. |
Beta Was this translation helpful? Give feedback.
I have logged this issue internally for the team to take a look at. I don't think this behavior should have changed. Thank you @g-k-s-g-k-s for the workaround though.