Search Issue Tracker
Won't Fix
Won't Fix in 1.7.X
Votes
0
Found in [Package]
1.7.4
Issue ID
TB-199
Regression
No
Infinite Animation clip glitches when Animation Track ends
Steps to reproduce:
- Open the "Timeline-Cinemachine-Test-Suite" project
- Open the "TL - Blend Clips Scene" Scene
- Enter the Play mode
- Observe both "Troll" animations
Expected: Animations are smooth
Actual: Animation glitches one time when the "Troll" is walking
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b11, 2023.2.0a9
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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.
If you feel this issue does not have an acceptable workaround or that you are still blocked by this issue and strongly feel like this should be addressed, reply to this notification to re-open the issue and explain why this is the case. Or, simply log a new bug if the context (version, repro steps) has changed since the original bug report.
Resolution Note (1.7.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.
If you feel this issue does not have an acceptable workaround or that you are still blocked by this issue and strongly feel like this should be addressed, reply to this notification to re-open the issue and explain why this is the case. Or, simply log a new bug if the context (version, repro steps) has changed since the original bug report.