Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2017.3.0a2
2018.2.0a1
2018.2.3f1
2018.3.0a1
2019.1.0a1
Issue ID
1091972
Regression
Yes
Root values played by the Timeline that has a recorded track are incorrect when using SetAnimationClipSettings
How to reproduce:
1. Download and open the project from OC
2. In the Project window go to Scenes and open "Scene" scene
3. In the Hierarchy select Test Functions game object and click "Set Animation Clip Settings Publicly"
4. Go to Window -> Sequencing -> Timeline
5. Select Timeline game object in the Hierarchy
6. In the Timeline window move the Playhead to the right
Expected result: The animation starting position is identical to the one set with the "Set Animation Clip Settings Via Reflection" button in the Test Function game object
Actual result: The animation starting position is different from the one set with the "Set Animation Clip Settings Via Reflection" button in the Test Function game object
Reproducible with: 2017.3.0a2, 2017.4.16f1, 2018.1.9f2, 2018.2.19f1, 2018.3.0f1, 2019.1.0a11
Not reproducible with: 2017.3.0a1
Note: Changing any Animation Clip Setting in the Debug mode makes the correct root values to be visible
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment