# InterpToMovement always returns zero velocity

**URL:** <https://forums.unrealengine.com/t/interptomovement-always-returns-zero-velocity/383588>\
**Category:** Character & Animation\
**Tags:** bug, unreal-engine, Blueprint, question\
**Created:** [February 1, 2017, 7:52am UTC](https://forums.unrealengine.com/t/interptomovement-always-returns-zero-velocity/383588 "2017-02-01T07:52:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CosmoGorynych](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@CosmoGorynych](https://forums.unrealengine.com/u/CosmoGorynych)\
**Post date:** [February 1, 2017, 7:52am UTC](https://forums.unrealengine.com/t/interptomovement-always-returns-zero-velocity/383588/1 "2017-02-01T07:52:51Z")

</div>

As the title shows, any time you try to get a velocity of an Actor with InterpToMovement component, you will get a zero vector. This affects both velocity of an Actor and Get method of InterpToMovement component.

Actor is really moving, but this always returns zeroes:

 ![124451-dw.jpg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/4/4/5/445816ba7fa6adde58a91fdcfe64e81e2e5b4d1c.jpeg)

It prevents from e.g. calculating the direction of the object, making the component a useless decorative movement type :c

---

<div class="post-metadata">

**Author:** ![TJ\_V](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tj_v/32/1008648_2.png) [@TJ\_V](https://forums.unrealengine.com/u/TJ_V)\
**Post date:** [February 3, 2017, 8:44pm UTC](https://forums.unrealengine.com/t/interptomovement-always-returns-zero-velocity/383588/2 "2017-02-03T20:44:46Z")

</div>

Hi CosmoGorynych,

I believe what you are seeing is inherited parameters from the UMovementComponent that are suppose to be hidden through code. Velocity isn’t part of the InterpToMovement node because it is literally interpolating between different points.

I have added [JIRA UE-41547](https://issues.unrealengine.com/issue/UE-41547) for this issue. Our developers will be investigating further. Follow that link to monitor the status of the report.

Cheers,

TJ