# Setting "Disable Low Latency Update" to "true" makes the entire motionController (not just the children) lag behind. Is there any other workaround?

**URL:** <https://forums.unrealengine.com/t/setting-disable-low-latency-update-to-true-makes-the-entire-motioncontroller-not-just-the-children-lag-behind-is-there-any-other-workaround/450493>\
**Category:** XR Development\
**Tags:** UE4-22, unreal-engine, question\
**Created:** [June 11, 2019, 1:55pm UTC](https://forums.unrealengine.com/t/setting-disable-low-latency-update-to-true-makes-the-entire-motioncontroller-not-just-the-children-lag-behind-is-there-any-other-workaround/450493 "2019-06-11T13:55:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_cc4806ab](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_cc4806ab](https://forums.unrealengine.com/u/anonymous_user_cc4806ab)\
**Post date:** [June 11, 2019, 1:55pm UTC](https://forums.unrealengine.com/t/setting-disable-low-latency-update-to-true-makes-the-entire-motioncontroller-not-just-the-children-lag-behind-is-there-any-other-workaround/450493/1 "2019-06-11T13:55:29Z")

</div>

Hi!

We have a problem which hopefully get fixed with UE-74977

The suggested workaround with the motion controllers attachments lagging behind is setting “Disable Low Latency Update” to true, which sadly doesnt work for us because it makes the entire motion controller lag in the same maner as only the attachments did before.

Is there any other workarounds? The rest of the game doesnt lag.

Thanks!

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_cc4806ab](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_cc4806ab](https://forums.unrealengine.com/u/anonymous_user_cc4806ab)\
**Post date:** [August 13, 2019, 1:03pm UTC](https://forums.unrealengine.com/t/setting-disable-low-latency-update-to-true-makes-the-entire-motioncontroller-not-just-the-children-lag-behind-is-there-any-other-workaround/450493/2 "2019-08-13T13:03:31Z")

</div>

Still has a problem with this. Any news if its fixed in 4.23?

---

<div class="post-metadata">

**Author:** ![H4x03D](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@H4x03D](https://forums.unrealengine.com/u/H4x03D)\
**Post date:** [September 27, 2021, 2:05pm UTC](https://forums.unrealengine.com/t/setting-disable-low-latency-update-to-true-makes-the-entire-motioncontroller-not-just-the-children-lag-behind-is-there-any-other-workaround/450493/3 "2021-09-27T14:05:09Z")

</div>

Hi, this is the intended feature of _disabling_ the low latency tracking.  
The game tick is not on par with the actual tracking tick, thus resulting in a lagged behind position, which is “a few frames behind the true position”.

There is no workaround because that is an intended feature.

The VR template has changed how it works with OpenXR, for the better.  
If you want something to be displayed where the true position is without lag, make sure to attach the component to be tracked to the MotionController component inside your VR pawn (so that the tracked object is a child of the MotionController).

If you have any question just ask, even though your question is one year old