refactor: omit default texCoord in glTF exporter texture info#8741
Merged
Conversation
Follow-up cleanup for #8728. Only write texCoord on texture info objects when the material uses a non-default UV channel, matching the rest of the exporter's "omit defaults" convention.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up cleanup for #8728.
GltfExporter.attachTexturenow omits thetexCoordfield on texture info objects when the material uses the default UV0 channel.Changes:
texCoordwhenmaterial[\${semantic}Uv`]` is non-zero.metallicFactor,roughnessFactor,KHR_texture_transform.scale/offset/rotation).texCoordas0, so the exported asset is functionally identical for any conformant loader — just slightly smaller JSON in the common UV0-only case.No public API changes.