Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
5.6.3f1
Issue ID
963053
Regression
No
When a Parent gameobject is trying to change Child's Animator.Parameter, Parent's Animator.Parameter is changed instead
Steps to reproduce:
1. Open QA's attached project
2. In the Hierarchy select "Parent" gameobject
3. Open Animation tab, switch from "Dopesheet" to "Curves" and observe that Property "Child : Animator.Control Parameter" is set to change from 0 to 1
4. Play the Scene and observe that Parent Animator's ControlParameter is changing instead of Child Animator's parameter
Expected result: Child Animator's ControlParameter is changing from 0 to 1
Actual result: Parent Animator's ControlParameter is changing from 0 to 1
Reproduced with: 5.5.4f1, 5.6.4p2, 2017.1.2p2, 2017.2.0p1, 2017.3.0b7, 2018.1.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment