Search Issue Tracker
Fixed in 1.4.4
Votes
0
Found in [Package]
1.0.0
Issue ID
1274892
Regression
No
A keyframe is set in a wrong position when animating a Timeline Clip which doesn't have a frame recorded at the 0th frame
How to reproduce:
1. Open the attached "1274892" project
2. Open the "SampleScene" Scene
3. Open the Timeline window (Window->Sequence->Timeline)
4. In the Hierarchy select the "Sphere" GameObject
5. In the Timeline double click on the recorded Clip
6. In the Animation window start recording
7. In the Animations Timeline move the Playhead to the 27th frame
8. Move the "Sphere" GameObejct in the Scene to record a keyframe
Expected result: The keyframe appears on the 27th frame
Actual result: The keyframe appears on the 26th frame
Reproducible with: 1.0.0, 1.5.0-preview.4 (2018.4.27f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0b2)
Notes:
- The issue is reproducible only when animating a Timeline Clip. Does not reproduce when animating an Animation or Timeline track
- The issue will not reproduce if the Timeline Clip has a frame recorded on a 0th frame
- Recording in the Timeline on the 0th frame and then moving the Clip will not reproduce the issue
- Not having anything recorded on the 0th frame in the Timeline and then moving the Clip to the 0th frame position will produce the issue
- The issue is reproducible only when recording a keyframe at certain frames (for example trying to put a keyframe on the 20th frame will work as intended and the keyframe will be created at 20th frame but trying to create a keyframe at the 27th frame, the keyframe will be created at the 26th frame instead)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Render Pipeline Converter selected asset counter reports one fewer item when using manual selection
- [Android] [Adreno] [WebGL] A light cookie is not rendered with shader compile error when WebGL build is launched on a device with Adreno GPU
- Rigibody sliding over a flat surface that is made of several GameObjects detects false collisions when Collision Detection is set to "Continuous" or "Continuous Dynamic"
- UI Toolkit Label height is incorrectly calculated when using max-width with percentage value
- Visual Effect Material causes Scene view to update continuously when both Scene and Game views are open, despite "Always Refresh" being disabled
Add comment