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
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Add comment