clone node associations in GLTFLoader #31051
Open
Conversation
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
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.
Description
GLTFLoader doesn't correctly assign the
nodesassociation when multiplenodes reference the same mesh. The problem occurs in
_loadNodeShallowwhere
nodesproperty is added to the shared object describing the node/meshassociation.
For example, in the CesiumMilkTruck model nodes 0 (Wheels) and 2 (Wheels.001)
reference the same mesh 0, but resulting associations for both three.js meshes are
{meshes: 0, primitives: 0, nodes: 2}.A simple solution is to clone the association object if there are multiple references to
the same mesh.