Skip to content
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

"Namespace mapping" feature #173

Open
AndreyZhukov opened this issue May 15, 2020 · 1 comment
Open

"Namespace mapping" feature #173

AndreyZhukov opened this issue May 15, 2020 · 1 comment

Comments

@AndreyZhukov
Copy link

It would be awesome to have a "Namespace mapping" feature which will change (remap) namespacing betweeen Maya and Unity.
E.g. I have the same rig referenced in a Maya scene several times, so I use different namespaces for them. But in Unity i would like to have a different namespace. Or even better, to place it outside the MeshSyncServer hierarchy (is it possible?) Sorry, I think my thoughts ramble now...
The thing is, when I have multiple instances of the same rig (under different namespaces) in Maya, and want to remove namespace, all of these rigs "become one", i mean they "write" to the same rig in Unity during syncing. So then Unity doesn't know which one to "take"/"read". Maybe with "Selected only" feature it would be possible to Remove Namespaces only on selected rig.
I guess now it's possibly not clear enough and I'll try to clarify in further posts.

@sindharta
Copy link
Contributor

I kind of get what you are saying.
It would be helpful if you can clarify more what this means, maybe with some pictures that you have in Maya.

The thing is, when I have multiple instances of the same rig (under different namespaces) in Maya, and want to remove namespace, all of these rigs "become one", i mean they "write" to the same rig in Unity during syncing. So then Unity doesn't know which one to "take"/"read".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants