Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.1
2018.2
2018.3
2018.3.14f1
2018.4
2019.1
2019.2
2019.3
2020.1
Issue ID
1202394
Regression
Yes
The total frames of the animation does not fill the timeline
How to reproduce:
1. Open the attached 2018.3.14f1.zip project
2. Go to the Project window and select 724184.fbx
3. In the Inspector window-> Animation inspect the Length of the animation
4. Open the attached FBXTest.zip folder it has four folders with four animations of different lengths
5. Copy one animation with different length from the provided in the Unity project and then paste and replace that animation in the Project folder->Asstets
6. Go back to the Editor-> Project folder and select Scenes folder and select 724184.fbx
7. inspect the Length of the animation in the Inspector window
8. Repeat 2-7 steps to reproduce the issue (see the attached Repro-1202394.mov)
Expected: The total frames of the animation does not fill the timeline
Actual: The timeline is one second long, and the animation length is a subset of that
Reproducible with: 2018.1.0b6, 2018.1.b7, 2018.2.21f1, 2018.3.14f1, 2018.4.14f1, 2019.2.16f1, 2019.3.0f3, 2020.1.0a16
Not reproducible with: 2017.4.35f1, 2018.1.0b5
Notes:
- It is hard to reproduce, on 2018.1.0b5 I tired to reproduce for about 20min. Looks like it regressed in 2018.1.0b6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
- "Custom Render Queue" field cannot be set above "2000" when changing it in the Inspector window using Debug mode
Add comment