Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2017.4.X, 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2019.2
2019.2.14f1
2020.1
Issue ID
1201584
Regression
No
Setting EditorCurveBinding.type to a custom component bind to "MonoBehavior" instead of the derived class
How to reproduce:
1. Open the project
2. Open the "SampleScene" scene
3. Windows > Animation > Animation
4. Select testProperties in the Hierarchy
5. Reimport the "testProperties" prefab
6. Notice that the "Take 001" animation has pCube:MonoBehavior.Properties._0 properties
Actual result: The EditorCurveBinding.type gets set to MonoBehaviour.
Expected result: The EditorCurveBinding.type is set to FloatProperty (derived from MonoBehaviour).
Reproducible with: 2020.1.0a15, 2019.3.0f1, 2019.2.15f1.
Notes:
- The custom binding is assigned in AssetImporter.cs at OnPostprocessGameObjectWithAnimatedUserProperties callback.
- Can't test 2018.4 and 2017.4 because the animation gets corrupted.
-----------------
Fixed in 2020.1.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
- 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.2):
fixed in 2019.2.20f1
Resolution Note (fix version 2017.4):
Fixed in 2017.4.39f1