Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-1885
Regression
No
[Backport] Stepped keys in ".fbx" asset do not always have the correct animation curves when imported to Unity
Reproduction steps:
1. Create a new Unity project and open it
2. Import attached "1322543Test.fbx" asset to your project
3. Select this asset and look at the Inspector window
4. Select the Animation tab and uncheck the "Resample Curves" checkbox, set "Anim. Compression" to off, and check the "Animated Custom Properties" checkbox and click on Apply
5. In the top toolbar click on Window/Animation/Animation to open the Animation window
6. Expand imported asset and click on "Take 001" to view it in the Animation window
7. In the Animation window, select "Curves" to view animations in Curves mode and select "Animator.Eyelid Shape_L"
8. Look at frames 241-242
Expected result: No inconsistencies are observed, meaning that stepped keys were imported correctly
Actual result: A giant dip in the animation curve is observed between 241 and 242 frames
Reproducible with: 2018.4.35f1, 2019.4.27f1, 2020.3.9f1, 2021.1.0a7
Not reproducible with: 2021.1.0a8, 2021.1.8f1, 2021.2.0a17
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
Fix has caused regressions elsewhere so we don't intend to backport to 2020.3 currently.