-
Notifications
You must be signed in to change notification settings - Fork 203
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
Use "mtl" as default scope name on export #2903
Use "mtl" as default scope name on export #2903
Conversation
This centralizes the declaration of the name and the two environment variable affecting it. It also exposes that name to the Python API for use in export scenarios. Unit tests that were relying on "Looks" had the USD_FORCE_DEFAULT_MATERIALS_SCOPE_NAME added to their environment when running.
@@ -797,8 +789,6 @@ global proc int mayaUsdTranslatorExport (string $parent, | |||
$currentOptions = mayaUsdTranslatorExport_AppendJobContexts($currentOptions, "jobContext"); | |||
} | |||
|
|||
$currentOptions = mayaUsdTranslatorExport_AppendFromEnvElseDefault($currentOptions, "materialsScopeName", "MAYAUSD_MATERIALS_SCOPE_NAME", `getMayaUsdString("kExportMaterialsDefaultScopeName")`); | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No longer necessary.
|
||
The `MAYAUSD_MATERIALS_SCOPE_NAME` environment variable can be used to change | ||
that default on a global level. The value defined in that env var will take | ||
precedence over any value passed in the materialsScopeName argument. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Not sure I like that. Maybe this should override only when a materialsScopeName
argument is not provided?)
@seando-adsk Ready for merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll defer to the code review to Pierre/Jonathan.
This centralizes the declaration of the name and the two environment variable affecting it. It also exposes that name to the Python API for use in export scenarios.
Unit tests that were relying on "Looks" had the
USD_FORCE_DEFAULT_MATERIALS_SCOPE_NAME added to their environment when running.