Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0a5
2019.1.8f1
2019.2.0a1
2019.3.0a1
Issue ID
1165368
Regression
Yes
Custom Property attribute is displayed as missing when using Animated Custom Properties on FBX import
How to reproduce:
1. Open the attached project ("case_1165368-Animation_Custom_Properties.zip")
2. Open the repro scene ("SampleScene")
3. Open the "Animation" tab
4. Select the "sphere" object in the Hierarchy
5. Notice in the "Animation" tab that the custom property is marked as missing
Expected results: The custom property attribute is not marked as missing
Actual results: the custom property attribute is marked as missing
Reproducible with: 2019.1.0a5, 2019.1.9f1, 2019.2.0b8, 2019.3.0a8
Does not reproduce with: 2017.4.30f1, 2018.4.3f1, 2019.1.0a4
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2019.3):
Fixed in 2019.2.11f1, 2019.3.0a11