Move skin registration process into deferred on ready #97489
Merged
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.
Fixes #97459
Since the initial update of the skin is done in the skeleton's deferred process, it seems that the process that searches for the skeleton when the skin is first loaded into the tree should also be moved to the deferred process.
However, I am not so familiar with the Skin deformation process in MeshInstance3D, so I am not sure if this is really the correct fix. Although, I think it is safe since this just move the process timing on loading, but please review/test carefully. cc @fire @MajorMcDoom