Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.5f1
2019.2.0a1
2019.3.0a1
Issue ID
1160784
Regression
No
The Transition ExitTime for a Transition towards EXIT is not evaluated
How to reproduce:
1. Open user-supplied project
2. Open "SampleScene"
3. Select "Player" >"Body"
4. In Animator Window double click "Locomotion" > "Air"
5. Select a transition from "Landing" to "Exit"
6. Play the Scene and press spacebar
Expected result: Exit time is evaluated
Actual result: Animation plays until its end, though Exit Time is set to 0.25
Reproduced in: 2017.4.27f1, 2018.4.1f1, 2019.1.5f1, 2019.2.0b5, 2019.3.0a4
Comments (2)
-
ryanbabraham
May 19, 2020 09:14
It is an informative post, and it gave some information about the transition exit time. You gave a step by step instruction and easy to understand the issue. https://www.thecbdnewshub.com I think your post will be useful to everyone. Thanks for sharing the valuable information for us.
-
ivaanadam01
Mar 09, 2020 11:59
good<a href="https://www.google.com/">click</a>
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note:
By design : we cannot evaluate a transition twice in the same frame, which is unfortunately problematic when in the situation where the exit time needs to be evaluated at the end of another transition. Changing this would be too impactful and may break many existing projects