Fix Exception when exporting an Animator | Fix null reference exception when bone frame is not found #129
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 this error
Fix null reference exception when bone frame is not found
Add null check for frame lookup result before accessing _frameToNode dictionary.
Previously, if FindFrameByPath returned null, the code would throw a
NullReferenceException when trying to use the frame as a dictionary key.
Now properly handles missing frames by passing IntPtr.Zero to AsFbxMeshAddCluster,
consistent with the original null path handling.