Search Issue Tracker
Fixed in 2020.1
Votes
0
Found in
2019.2
2019.3
2019.3.0f1
2020.1
Issue ID
1201758
Regression
No
Case mismatch when accessing animated curves from the animator or a AnimationJob
How to reproduce:
1. Open user-submitted project (customProperties)
2. Open the SampleScene
3. Disable 'Directional Light' 'StructToArray' Component
4. Enable 'testProperties/pCube1' Property Stream Handle Example Component
5. Enter Play Mode
Expected result: the Console logs values of Animator.pCube1.bob
Actual result: the Console logs '0'
Reproducible with: 2019.2.15f1, 2019.3.0f2, 2020.1.0a15
Could not test with: 2017.4.35f1, 2018.4.14f1(Animator properties do not change values at all even in the Animator window)
Notes:
Changing the Animator property 'pCube1.bob' to 'PCube1.bob' does not cause this issue
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
- Unity crashes when opening the project
- "Color Picker not supported on this platform" error is thrown when UseOSColorPicker is set to true on Windows
- Lightmap Encoding Quality settings do not apply to baked lightmap textures
- GameObject is not culled and can be seen in the Frame Debugger when Camera is facing away from it
- [UIR] Lines separating packages wiggle in Packman at 150%
Resolution Note (fix version 2020.1):
Since bindings/curves are uniquely identified using hashes of the supplied name(s), there isn't a way to fix this directly - however, a warning was added to inform about duplicate curve bindings.