fix: NetworkAnimator destinationStateMachine exception [MTT-5083]#2309
Merged
NoelStephensUnity merged 29 commits intodevelopfrom Jan 12, 2023
Merged
Conversation
Manual test that validates this fix.
Contributor
jeffreyrainy
left a comment
There was a problem hiding this comment.
Mistakenly approved wrong PR, please wait for actual review before acting on this approval.
This includes some updates to NetworkAnimator that will remove the need to synchronize client's using RPCs but instead use the new OnSynchronize method. Fixed an issue with using pooled objects and when specific properties are cleaned during despawn and destroy.
jeffreyrainy
approved these changes
Dec 12, 2022
lpmaurice
previously approved these changes
Dec 14, 2022
0xFA11
approved these changes
Jan 12, 2023
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.
This resolves the issue where
NetworkAnimatorwas not checking forAnimatorStateTtansition.destinationStateMachine, which was causing an exception, and adding any possible states with triggers defined within it. This also prevents the server from sending itself messages about animation state changing (#2305).MTT-5083
MTT-5122
GitHub Issues Resolved:
#2305
#2293
#2374
#2366
#2368
Changelog
NetworkAnimatorissue where it was not checking forAnimatorStateTtansition.destinationStateMachineand any possible sub-states defined within it.NetworkAnimatorissue where the host client was receiving the ClientRpc animation updates when the host was the owner.NetworkAnimatorissue with using pooled objects and when specific properties are cleaned during despawn and destroy.NetworkAnimatorwas checking for animation changes when the associatedNetworkObjectwas not spawned.Testing and Documentation