Skip to content

Conversation

@NoelStephensUnity
Copy link
Collaborator

Up-port of #2999 to v2.x.x.

This fixes the issue where a trigger that transitions to a state with a trigger that transitions back to the original state could cause NetworkAnimator to generate a false layer to layer state transition which would not only generate an additional message after the original trigger message, but would cause the non-authority instances to log a warning message.

MTTB-48
fix: #2828

Changelog

  • Fixed: Issue where a state with dual triggers, inbound and outbound, could cause a false layer to layer state transition message to be sent to non-authority NetworkAnimator instances and cause a warning message to be logged.

Testing and Documentation

  • Includes manual test.
  • Includes integration test.
  • No documentation changes or additions were necessary.

This is an up-port of the #2999 NetworkAnimator fix.
The ci runtime and editor manual tests for this fix.
@unity-cla-assistant
Copy link

unity-cla-assistant commented Aug 13, 2024

CLA assistant check
All committers have signed the CLA.

@NoelStephensUnity NoelStephensUnity changed the base branch from develop to develop-2.0.0 August 13, 2024 16:41
Adding changelog entry.
@NoelStephensUnity NoelStephensUnity marked this pull request as ready for review August 13, 2024 16:42
@NoelStephensUnity NoelStephensUnity requested a review from a team as a code owner August 13, 2024 16:42
@NoelStephensUnity NoelStephensUnity merged commit 503dd15 into develop-2.0.0 Aug 13, 2024
@NoelStephensUnity NoelStephensUnity deleted the fix/dual-triggers-generating-false-state-transition-up-port branch August 13, 2024 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Network Animator error on Client: [DestinationState To Transition Info] Layer (0) does not exist!

3 participants