Hey all,
I had a question about a behavior of the Scene Inventory that seemed odd to me.
In one of my scenes, I’ve loaded the model product (.ma) of an asset using the ReferenceLoader. In the Scene Inventory, I’m trying to switch the folder and change to the rig product. This appears to be bringing the right data into the scene, as I can see my rig sets, but the model namespace persists in the group names in my outliner, and is also present in the Scene Inventory.
Was wondering if this is a bug? I’m currently using core 1.5.0 and maya 0.4.12. Thanks in advance!
Changing the namespaces indeed does not happen on switch. This has been somewhat intentional in the fact that historically there were cases where reference edits started failing when changing namespaces around on the references. But more so - if that namespace ended up in a different scene down the line (in a nested way) where you also wanted to start to use the switch behavior then you’d definitely be losing your reference edits because now inside the reference namespace you’re loading content that internally also started having different namespaces - which may bring problems on that front.
All things aside, implementing a namespace change on switch from a code perspective isn’t hard - whether it’s the right idea from a production/pipeline perspective always was the bigger issue.
Yeah, it all makes sense but isnt maya user allowed to alter the namespace any time via Namespace editor while still keeping all ref edits intact? Its not forbidden natively so could be used by Ayon too, or?
I think we should switch the namespace too…if no harm would occur. If so then yeah, different story then!
Correct - you can. I’m not sure if nowadays in recent Maya releases it still sometimes suffer from the namespace change edit. The bug that occurred at the time was that a Maya scene save and reopen would lose the edits after the namespace was changed.
Just getting back to this subject now, but thank you both for the replies!
In short it sounds like we’ll need to do our own testing to see whether or not nested references are going to be a concern in our workflow, and accordingly we may implement our own namespace changes upon scene build/load. In any case, we now have clarification that the scene inventory’s treatment of namespaces is expected.
