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

Chasers to provide more robust methods to get translated paths #3363

Open
gelshoffNV opened this issue Oct 3, 2023 · 1 comment
Open

Chasers to provide more robust methods to get translated paths #3363

gelshoffNV opened this issue Oct 3, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@gelshoffNV
Copy link

There is currently a useful method for returning a mapping of translated Maya DagPaths to USD paths, using GetDagToUsdMap. It could be more useful to be able to call methods like GetDagPath() by providing the USD path and GetUsdPath() by providing the DagPath. It's also important to be able to fetch DG nodes, like GetDepNode() by providing the USD Path and GetUsdPath() by providing just the DG name.

This is especially important when maya nodes have namespaces, since they will either be stripped in USD or sanitized by replacing ':' with '_', which makes it difficult to figure out which maya node belongs to which usd node and vise versa.

The translator could keep a running map of all translated nodes and where they went in USD and either make that private and expose functions like I suggested or just make the mapping public, but not limited to DagPaths.

@gelshoffNV gelshoffNV added the enhancement New feature or request label Oct 3, 2023
@neilh-adsk neilh-adsk moved this to Needs triage in maya-usd Nov 6, 2023
@maya-usd-git-sync
Copy link

Issue synced internally to EMSUSD-826

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Needs triage
Status: Needs triage
Development

No branches or pull requests

1 participant