Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.2f1
Issue ID
941758
Regression
No
ChildAnimatorStateMachine.position doesn't change the StateMachines position
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. Right click "SetupAnimationController" -> "Mod" -> "Setup" -> "NewAnimationController"
3. Click on the new "animationController"
4. "Window" -> "Animator"
Expected Result: "BUG1" and "BUG2" State Machines are in different (set in code) places
Actual Result: "BUG1" and "BUG2" State Machines are on top of each other
Reproduced with: 2017.3.0a5, 2017.2.0b9, 2017.1.0p5, 5.6.3p2, 5.5.4p4, 5.4.5p5
Note:
The position doesn't change, even thought through Debug.Log you can see that the Vector3 is changed.
Changing the position on the State Machine creation works, but after that ChildAnimatorStateMachine.position doesn't affect the State Machine
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Add comment