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

[EMSUSD-603] Has "fix bogus name clash errors when stripping namespaces" not been implemented? #3277

Open
sharktacos opened this issue Aug 14, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@sharktacos
Copy link

Saw this issue on OpenUSD from 2019:
PixarAnimationStudios/OpenUSD#683

Has this not been implemented on the Maya USD? Testing on Maya 2024.1 USD v23.1 it would appear it has not.

Steps to reproduce
reference in a Maya rig under a prim (used Mery rig as test)
"cache to USD" with the following options:
"merge transforms and shapes nodes" ON
"include namespaces" OFF

This results in the error:
“Multiple dag nodes map to the same prim path after stripping namespaces” and the cache is not exported.

Describe the bug
As the issue states on OpenUSD
"When exporter strips namespaces it checks if path was already visited and if so raises an error.
However when we also merge transforms and shapes, then it's not an error to map both of them to same primitive."

workaround:
set "merge transforms and shapes nodes" OFF.

Just wanted to bring this to folks' attention.

Specs (if applicable):
Windows 10 OS
Maya 2024.1
USD v23.1

@sharktacos sharktacos added the bug Something isn't working label Aug 14, 2023
@santosg87
Copy link
Collaborator

thanks for bringing this up @sharktacos! we will investigate a bit more and try to understand what could be going on here. the fix you mention, should be in our builds, as far as I can tell, since we are using a later version of USD than the merged issue. but it's possible the code path from the mayaReference is doing something unexpected. I will see what i can find :)

@santosg87
Copy link
Collaborator

Hi @sharktacos, after some investigation, the fix you mention is indeede in. with that said though, it seems the cache to USD path is doing something to still bypass that original fix, possibly due to the fact that we have a USD node above the mayaReference node.

If I export a rig from maya directly (without using the USD maya reference node), i am able to export without that error, but through cache i still see the problem.

I logged this internally so we can prioritize and discuss next steps. logged as EMSUSD-603

@santosg87 santosg87 changed the title Has "fix bogus name clash errors when stripping namespaces" not been implemented? [EMSUSD-603] Has "fix bogus name clash errors when stripping namespaces" not been implemented? Sep 6, 2023
@neilh-adsk neilh-adsk moved this to Needs triage in maya-usd Nov 6, 2023
@Autodesk Autodesk deleted a comment from maya-usd-git-sync bot Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Needs triage
Development

No branches or pull requests

2 participants