# Motion Controller occluded when in close proximity to player character...

**URL:** <https://forums.unrealengine.com/t/motion-controller-occluded-when-in-close-proximity-to-player-character/273790>\
**Category:** Mobile\
**Tags:** unreal-engine, FeatureRequest, UE4-27\
**Created:** [January 20, 2022, 3:59pm UTC](https://forums.unrealengine.com/t/motion-controller-occluded-when-in-close-proximity-to-player-character/273790 "2022-01-20T15:59:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hanus35](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/hanus35/32/637725_2.png) [@hanus35](https://forums.unrealengine.com/u/hanus35)\
**Post date:** [January 20, 2022, 3:59pm UTC](https://forums.unrealengine.com/t/motion-controller-occluded-when-in-close-proximity-to-player-character/273790/1 "2022-01-20T15:59:32Z")

</div>

I posted a link below of my issue. It’s driving me nuts!!! lol The motion controllers location and tracking are fine. But once I bring the controller close to me it disappears. Hand tracking works fine too. I can access the menus when doing the proper pinches… But since they are close to the player character they can’t be seen.

You can see in the video. I am moving the controller with my foot so I can actually see it in game. You’ll see as I move the controller closer to me it begins to clip with something… There is nothing for it to clip with though…

[![]( " - YouTube") ](https://www.youtube.com/watch?v=QhHkWkNpO6A)

---

<div class="post-metadata">

**Author:** ![hanus35](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/hanus35/32/637725_2.png) [@hanus35](https://forums.unrealengine.com/u/hanus35)\
**Post date:** [January 20, 2022, 4:06pm UTC](https://forums.unrealengine.com/t/motion-controller-occluded-when-in-close-proximity-to-player-character/273790/2 "2022-01-20T16:06:39Z")

</div>

I migrated my entire project to the VR Template and motion controllers work fine. I then copied over my config files and they bug out again. So the issue is coming from some type of setting… Anyone know what setting could cause this issue?
