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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment