# Instanced or hierarchical meshes don't affect navigation

**URL:** <https://forums.unrealengine.com/t/instanced-or-hierarchical-meshes-dont-affect-navigation/606416>\
**Category:** Getting Started & Setup\
**Tags:** unreal-engine, UE5-0, bug-report, question\
**Created:** [July 16, 2022, 5:11pm UTC](https://forums.unrealengine.com/t/instanced-or-hierarchical-meshes-dont-affect-navigation/606416 "2022-07-16T17:11:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cheekycheetah](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@cheekycheetah](https://forums.unrealengine.com/u/cheekycheetah)\
**Post date:** [July 16, 2022, 5:11pm UTC](https://forums.unrealengine.com/t/instanced-or-hierarchical-meshes-dont-affect-navigation/606416/1 "2022-07-16T17:11:56Z")

</div>

I am generating trees and other objects as instanced and hierarchical meshes but when this is done at runtime it doesn’t have any effect on navigation.

There’s a bug report here: [Unreal Engine Issues and Bug Tracker (UE-150147)](https://issues.unrealengine.com/issue/UE-150147) which might have resolved this issue for 5.1, but it only talks about foliage and not general instanced meshes or hierarchical ones. Regardless, it’s probably not out for a little while…

I’m wondering if anyone has a workaround for this at the moment?

---

<div class="post-metadata">

**Author:** ![oxyg1n](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/oxyg1n/32/992508_2.png) [@oxyg1n](https://forums.unrealengine.com/u/oxyg1n)\
**Post date:** [July 17, 2022, 4:35pm UTC](https://forums.unrealengine.com/t/instanced-or-hierarchical-meshes-dont-affect-navigation/606416/2 "2022-07-17T16:35:57Z")

</div>

This is quite the issue for me as well.

My game takes place in a forest with procedural foliage trees and since upgrading to UE5 the monsters are having a terrible time getting to their destinations. I’m actually surprised this made it to 5.0.

I’m planning on releasing this game later this year. Hopefully this issue is merged into release soon.

---

<div class="post-metadata">

**Author:** ![cheekycheetah](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@cheekycheetah](https://forums.unrealengine.com/u/cheekycheetah)\
**Post date:** [July 18, 2022, 11:53am UTC](https://forums.unrealengine.com/t/instanced-or-hierarchical-meshes-dont-affect-navigation/606416/3 "2022-07-18T11:53:15Z")

</div>

So after a lot of fiddling yesterday, I found a temporary solution… If you move the parent actor that contains all of the instances, it seems to update the navmesh. You have to actually move it at least a cm though, can’t just set it to the same position.

I’m also building a procedural forest, so it’s probably not super efficient to move all these instances, but at least it works for the moment and hopefully 5.1 will bring a fix for this.