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

Use "mtl" as default scope name on export #2903

Merged
merged 1 commit into from
Feb 28, 2023

Conversation

JGamache-autodesk
Copy link
Collaborator

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.

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")`);

Copy link
Collaborator Author

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.
Copy link
Collaborator Author

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?)

@JGamache-autodesk JGamache-autodesk added the ready-for-merge Development process is finished, PR is ready for merge label Feb 27, 2023
@JGamache-autodesk
Copy link
Collaborator Author

@seando-adsk Ready for merge.

Copy link
Collaborator

@seando-adsk seando-adsk left a 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.

@seando-adsk seando-adsk merged commit d962150 into dev Feb 28, 2023
@seando-adsk seando-adsk deleted the gamaj/use_asset_wg_default_material_scope_name branch February 28, 2023 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
import-export Related to Import and/or Export materials ready-for-merge Development process is finished, PR is ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants