Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
0
Found in
2017.2.0b8
Issue ID
945035
Regression
Yes
Transition between animations makes GetIKRotation and GetIKPosition return incorrect value
Steps to reproduce:
1) Download attached project 'New Unity Project 6.zip' and open in Unity
2) Open scene 'Clean Scene' and press Play
3) Click L.mouse button on the Scene view
Observe the Console window and you will see that values of the GetIKRotation and GetIKPosition will be returned incorrectly (Position: (-1.8, 0.4, -22.7) Rotation: (350.6, 336.6, 258.0))
Expected result: Values of the GetIKRotation and GetIKPositionshould should be ~ Position: (-1.7, 1.5, -22.7) Rotation: (349.0, 353.8, 259.3) (check attached image 'expected.png')
Actual result: Values of the GetIKRotation and GetIKPositionshould are ~ Position: (-1.8, 0.4, -22.7) Rotation: (350.6, 336.6, 258.0) (check attached image 'actual.png')
Reproduced with:
2017.1.0a1, 2017.1.0p5, 2017.2.0b9, 2017.3.0a5
Not reproduced with:
5.5.4p3, 5.6.3p2
Regression since:
2017.1.0a1
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
- [macOS] “Input.GetMouseButtonDown” gets set to true when pressing and when releasing the mouse button in the Device Simulator view if "targetFrameRate" is set in the script
- UWP Capabilities are not changed when rebuilding the project
- [Oculus] Lights causing artifacts when Forward+ Rendering is selected
- Game Window Icons are white when in light mode
- Crash on VFXMemorySerializer::StoreObjects when converting to Subgraph Block
MaulikKaloliya
Oct 14, 2017 05:05
This issue not fixed, still happening in 2017.2.0f3