Skip to content

Fix path resolving issue when usd files are used in different systems#2492

Merged
sebastienblor merged 2 commits intoAutodesk:masterfrom
sebastienblor:ARNOLD-17152
Dec 5, 2025
Merged

Fix path resolving issue when usd files are used in different systems#2492
sebastienblor merged 2 commits intoAutodesk:masterfrom
sebastienblor:ARNOLD-17152

Conversation

@sebastienblor
Copy link
Copy Markdown
Collaborator

When usd doesn't manage to resolve a usd path (in particular due to tokens like udims), we still to resolve it properly by asking each layer if the path corresponds to a file on disk. In order to help this process, a "./" needs to be added at the beginning of the filename.
However, when usd still doesn't manage to resolve the path, we're keeping the "./" at the beginning of the arnold filename.
This isn't correct in specific use cases, when the usd file is loaded in a different system than it was exported.
For example, when we export a scene from maya or max on windows, the ocio configuration is authored with an absolute path (C:/Program Files/Autodesk/etc...), and when we render it on linux, TfIsRelativePath returns true. Because of that, arnold ends up with a path set to "./C:/Program Files/etc...." which prevents from using path mapping properly.

@sebastienblor sebastienblor merged commit 7f0d854 into Autodesk:master Dec 5, 2025
9 checks passed
@sebastienblor sebastienblor deleted the ARNOLD-17152 branch December 5, 2025 11:46
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

Successfully merging this pull request may close these issues.

2 participants