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
- Changing scale of Tree prefab instance (in scene) and then undo/redo changes the source prefab scale and all painted instances
- Material properties are not correctly setup when assigning a ShaderGraph to a newly created material
- [iOS] Device.generation returns "DeviceUnknown" with some devices
- Misleading upgrade prompt when opening Project from Hub with an incremented project version
- Crash on GameObject::ActivateAwakeRecursivelyInternal when enabling a broken Prefab
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.