Search Issue Tracker
By Design
Votes
1
Found in
2018.4
2019.3.9f1
2020.2
Issue ID
1238942
Regression
No
Unable to add script properties of a custom Object type to be tracked in the Animation window
How to reproduce:
1. Open the attached project "1238942.zip"
2. Open the "test" scene
3. Open Animation window
4. Select GameObject "Test"
5. In Animation window click "Add Property" and expand "Test Object Ref Script (Script)"
Expected result: all variables, including the ones of type ScriptableObject, MonoBehaviour, and UnityEngine.Object, are shown in a list
Actual result: only variables of type Sprite and float are shown in a list
Reproducible with: 2018.4.22f1, 2019.3.12f1, 2020.1.0b6, 2020.2.0a8
Workaround: using Animation Events bypasses these limitations
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Cosmetic fix, low priority. We only support Sprite objects at the moment