Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b12
Issue ID
645562
Regression
No
When setting another state as default, the ex-default one gets executed out of order.
When setting another state as default, the ex-default one gets executed out of order.
Repro:
1. Add 2 states (one default), and add motions to them
2. Make transitions from Entry to Default to state2 to exit
3. Play the scene - it works fine (default then state2 is being executed)
4. Exit play mode. Make the the state2 a default state
5. Play again - the ex-default state is still being execute even though there is no transition leading into it.
Expected: the ex-default state gets ignored
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment