Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2020.2
Issue ID
1241162
Regression
No
Previous Transition indicator becomes active and stuck in a loop when transitioning to Exit Node
Steps to reproduce:
1. Open the attached (case_1228989.zip) project
2. Select the "Test" GameObject
3. Open the Animator window (Window > Animation > Animator)
4. Enter Play Mode
5. Right-click on "New State" in the Animator State Machine
6. Select "Make Transition"
7. Make the transition to Exit
Expected result: Transition is shown to Exit Node
Actual result: Previous Transition indicator becomes active and stuck in a loop (repro.mp4 video attached)
Reproducible with: 2018.4.23f1, 2019.3.16f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14
Notes:
- The issue occurs only when transitioning to Exit Node, when transitioning to other states the issue does not occur
- When testing in 2019 stream NullReferenceExceptions are being thrown to reproduce the issue: exit PlayMode -> make the transition -> enter The PlayMode
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This is expected. A transition to an exit node that leads nowhere transitions to the layer default state.