Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
6
Found in [Package]
1.0.0
Issue ID
TB-13
Regression
No
Recording rotations in Timeline gives unpexpected incorrect values
When recording animation on a Timeline track, rotation values are not properly evaluated and existing values change. Existing keys/values should never be affected by a new key, at a new time, but they are. This also results in the the Inspector showing one value, and the curve another, for the same frame/time.
repro:
-create a Cube
-create a Timeline
-enable rec mode
-set a first rotation key (0,0,0) at time 0
(keys at time 0 have 0,0,0 values)
-move time to frame 60 and set another rotation key with a rotation value
(keys at time 0 now have 0,0,-360 values = bad)
-move time to frame 30 and set another rotation key with a new rotation value
(keys at time 0 now have 0,-360,0 values = bad)
(this value also some times becomes 180, 180,-180)
workaround: disabling/re-enabling the Timeline Preview mode resets first key values to expected 0,0,0
see attached TLrec.mp4
This does not repro in a standalone Animation Window, and is Timeline related.
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.0.X):
There are no fixes planned for this Bug
Resolution Note (1.0.X):
Despite our best efforts, we haven't found a solution that wouldn't require a significant rewrite of parts of the animation system, which we are not prepared to undertake for the foreseeable future.