Fix gltf import naming_version mixup#119083
Merged
Merged
Conversation
akien-mga
approved these changes
Apr 29, 2026
Member
|
I added pipeline review but it's probably good to merge. |
aaronfranke
approved these changes
Apr 29, 2026
Contributor
|
Thanks! |
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
6 participants
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.
The PR #96748 introduced the gltf .import parameter "texture_map_mode", but in the compatibility handling overwrote "naming_version" instead. This leads to slightly different names in the imported nodes and (in our case) changed properties on those nodes in editable children getting lost.
This issue describes the problem very well: #118761
Fixes #118761