# Unreal 4.11 Move Component To Node Rotation

**URL:** <https://forums.unrealengine.com/t/unreal-4-11-move-component-to-node-rotation/356659>\
**Category:** Community & Industry Discussion\
**Tags:** rotation, bug, move-component-to, UE4-11, unreal-engine, question\
**Created:** [May 6, 2016, 2:54pm UTC](https://forums.unrealengine.com/t/unreal-4-11-move-component-to-node-rotation/356659 "2016-05-06T14:54:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SwordSkill](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SwordSkill](https://forums.unrealengine.com/u/SwordSkill)\
**Post date:** [May 6, 2016, 2:54pm UTC](https://forums.unrealengine.com/t/unreal-4-11-move-component-to-node-rotation/356659/1 "2016-05-06T14:54:59Z")

</div>

Is there any way to make ‘Move Component To’ Blueprint node to always take the shortest path in regards to rotation, again, like it used to be in the older versions before 4.11?

Character seems to do a full spin around himself if rotation Yaw is within a certain radius.  
Gimbal Lock shouldn’t apply because it moves only in one axis.

Was there any specific reason why this node changed? I’m assuming this is a bug because I can’t find any other explanation as to why would anyone want to take the longest path on random occasions.

Here is a video explaining my problem:

---

<div class="post-metadata">

**Author:** ![SwordSkill](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SwordSkill](https://forums.unrealengine.com/u/SwordSkill)\
**Post date:** [May 6, 2016, 3:43pm UTC](https://forums.unrealengine.com/t/unreal-4-11-move-component-to-node-rotation/356659/2 "2016-05-06T15:43:26Z")

</div>

Edit: The Shortest Path on the Lerp Node works perfectly, I just tested it, however that still doesn’t change the fact that the ‘Move Component To’ node doesn’t work by always taking the Shortest Path which is a shame.

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_b9532c9a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_b9532c9a](https://forums.unrealengine.com/u/anonymous_user_b9532c9a)\
**Post date:** [May 9, 2016, 5:33pm UTC](https://forums.unrealengine.com/t/unreal-4-11-move-component-to-node-rotation/356659/3 "2016-05-09T17:33:07Z")

</div>

Hi SwordSkill,

I was able to reproduce this on my end and have entered a bug report, UE-30483, to be assessed by the development staff.

---

<div class="post-metadata">

**Author:** ![SwordSkill](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SwordSkill](https://forums.unrealengine.com/u/SwordSkill)\
**Post date:** [May 12, 2016, 7:02pm UTC](https://forums.unrealengine.com/t/unreal-4-11-move-component-to-node-rotation/356659/4 "2016-05-12T19:02:16Z")

</div>

Thanks, hopefully they will fix it by next update.

---

<div class="post-metadata">

**Author:** ![Raildex](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Raildex](https://forums.unrealengine.com/u/Raildex)\
**Post date:** [June 17, 2016, 7:14pm UTC](https://forums.unrealengine.com/t/unreal-4-11-move-component-to-node-rotation/356659/5 "2016-06-17T19:14:51Z")

</div>

I’m using MoveComponent To, too and an answer was, that it needed “fundamental shifts within the engine”

> **[MoveComponentTo Bug](https://forums.unrealengine.com/questions/375890/movecomponentto-bug.html)**
>
> Hi. If an axis goes from -180 to 180 or vice versa via MoveComponentTo, the Component rotates into it the "long" way, This is kind of annoying when using MoveComponentTo with a Ledge Climbing System.
