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
- Unstable lighting when additional light sources are added in Shader Graph nodes
- AnalyticsSessionInfo.sessionFirstRun value is not affected when the corresponding data file is removed
- Branch Rotation can't be undone
- "Rotate Branch" is too sensitive to mouse movement
- Renders "Add" button has no OnHover action
Add comment