Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2023.1.10f1
2023.2.0b6
Issue ID
UUM-47128
Regression
No
Animator node- Inconsistent transition representation for multiple transitions to self.
Many small arrows appear for multiple transitions to self. This does not follow the default format where three triangles represents multiple transitions between states.
- Create a new Unity project and add a new GameObject to the sample scene
- Add an animator component to this object using the inspector
- Create a new animator controller in the project window and drag this into the animator controller field reference
- Open up the Animator window: Window => Animation => animator
- Create a blank new state by right clicking the animator controller window: Create state =:> empty
- Right click on this new node and select create transition then click on the new node again- a white arrow should appear beneath the node
- Repeat this numerous times until multiple white arrows are visible stacked on top of each other (refer to picture B for guidance)
Expected result: The state shows either a single arrow pointing to itself or a three arrow representation where three white triangles appear below the node pointing to itself from the bottom of the node.
Actual result: Multiple white triangle stack on top of each other underneath the node.
!DefaultMultiTransitionLine.PNG|width=269,height=302!!MultipleArrows.PNG|width=287,height=128!
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Localization Group Rules bypasses Locale logic when SharedGroup asset provided
- UI Toolkit World UI Text Field unfocuses immediately when clicking on it using XR Controller
- Crash on CallWindowProcW when entering Play mode for the second time and running the Editor in the background while using System.Windows.Forms functions
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
Resolution Note:
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.
Resolution Note (2023.2.X):
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.