Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a6
Issue ID
601742
Regression
No
Transition names are not informative enough
Transition names are not informative enough
2) How can we reproduce it using the example you attached
1. Make the following simple controller:
Add a state machine to the Base Layert: Machine1 add also a state: State1 (make it default state)
Add a state to the Machine1: State2
Add a state machine to the Machine1: Machine2
Add a state to the Machine2: State2
2. Make 2 transitions from the State1:
Transition1: to the State2 inside the Machine1
Transition2: to the State2 inside the Machine2 (inside Machine1)
3. Select the State1 and notice in the Inspector there ate two identical transitions. Users will be unable to tell which one is which. Including a hierarchy would be helpful here.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] The Player freezes when disabling Bluetooth while connected to the headphones
- Addressable bundles are not retrieved from the cache when a WebGL Player is refreshed
- Sprites are incorrectly occluded by Sprite Physics Shape culling when behind in sorting order
- CPU usage is increased when the Editor is idle with the ProBuilder Package installed
- Unstable lighting when additional light sources are added in Shader Graph nodes
Add comment