Description

When opening a map with ISM in place, NavOctree is not updated because the ISM bounds are assumed invalid and the geometry is not taken into account in the navmesh build.  The following log output is generated at this time. 

LogNavigation: Warning: FNavigationOctree::AddNode: Empty bounds, ignoring InstancedStaticMeshComponent /Game/Developers/Collections/ism_cs_nav_test.ism_cs_nav_test:PersistentLevel.BP_ISM_C_1.NODE_AddInstancedStaticMeshComponent-0. LogNavigation: Warning: FNavigationOctree::AddNode: Empty bounds, ignoring InstancedStaticMeshComponent /Game/Developers/Collections/ism_cs_nav_test.ism_cs_nav_test:PersistentLevel.BP_ISM_C_1.NODE_AddInstancedStaticMeshComponent-0. 

Manually changing the ISM location or updating the bounces will eliminate this problem. Also, if this map is set as the startup map when the editor is launched, the problem does not occur. This is most likely a regression in UE5.5.

Steps to Reproduce
  1. Open the attached project
  2. Open "ism_cs_nav_test" map
  3. Navmesh build by selecting "Build Paths" in the editor
    Result: 
    Collisions are not taken into account around the mesh built with ISM 
    Expected: 
    Navmesh is generated taking ISM collisions into account

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-272945 in the post.

0
Login to Vote

Fixed
ComponentUE - AI - Navigation
Affects Versions5.5
Target Fix5.6
Fix Commit40572522
CreatedApr 15, 2025
ResolvedApr 15, 2025
UpdatedApr 16, 2025
View Jira Issue