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

Unnest UV reader and optimize #1915

Merged
merged 1 commit into from
Dec 16, 2021

Conversation

JGamache-autodesk
Copy link
Collaborator

First item in to fix in Issue #1834

  • The UsdUVTexture and UsdTransform2d are no longer nested under the
    file node
  • Shared place2dTexture nodes result in shared UsdUVTexture
  • If a file node does not have a place2DTexture node, then is shares a
    common UsdUVTexture

More to follow.

- The UsdUVTexture and UsdTransform2d are no longer nested under the
  file node
- Shared place2dTexture nodes result in shared UsdUVTexture
- If a file node does not have a place2DTexture node, then is shares a
  common UsdUVTexture
@@ -77,7 +78,7 @@ TF_DEFINE_PRIVATE_TOKENS(
_tokens,

// UsdPrimvarReader_float2 Prim Name
((PrimvarReaderShaderName, "TexCoordReader"))
((PrimvarReaderShaderName, "shared_TexCoordReader"))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could changing this name affects loading of existing files?

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. The name of the place2dTexture node is not restored when importing (and it was not previously written, as you can see).

@JGamache-autodesk JGamache-autodesk added the ready-for-merge Development process is finished, PR is ready for merge label Dec 16, 2021
@seando-adsk seando-adsk merged commit 48d571a into dev Dec 16, 2021
@seando-adsk seando-adsk deleted the t_gamaj/MAYA-114979/unnest_texture_reader branch December 16, 2021 21:58
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 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.

4 participants