-
Notifications
You must be signed in to change notification settings - Fork 450
fix: NetworkAnimator destinationStateMachine exception [MTT-5083] #2309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: NetworkAnimator destinationStateMachine exception [MTT-5083] #2309
Conversation
Manual test that validates this fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
This resolves the issue where
NetworkAnimator
was 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
NetworkAnimator
issue where it was not checking forAnimatorStateTtansition.destinationStateMachine
and any possible sub-states defined within it.NetworkAnimator
issue where the host client was receiving the ClientRpc animation updates when the host was the owner.NetworkAnimator
issue with using pooled objects and when specific properties are cleaned during despawn and destroy.NetworkAnimator
was checking for animation changes when the associatedNetworkObject
was not spawned.Testing and Documentation