Navigation mesh have invalid regions

Development World Creation
, , ,
1

Empty map have navigation mesh data.

71896-bug.png
71896-bug.png1666×569 70.6 KB

After build:

71897-bug2.png
71897-bug2.png1304×600 154 KB

Map file: [bug.map][3]

2

Hello,

I have attempted to reproduce this issue by creating a new empty level and adding a Nav Mesh Bounds Volume, but I don’t see the same result.

  • Have you been able to reproduce this in a clean project?
  • If so, what are the steps I can follow to reproduce this on our end?
  • To be clear, the level is completely empty other than that Nav Mesh Bounds Volume?

Thank you

3

Hi,

This bug have two variations:

  1. We have a huge map, with 1000 actors and foliage placed in a scene (trees places via Foliage tool). And we have the same incorrect space in navigation mesh. Bug continue to exist even after deleting all the objects from the map. I dont not know how to reproduce that.

  2. I’ve done some research and turn out that the bug caused by trees collision, i captured a video showing steps to reproduce this bug in a simple way, where the only object in a scene is a tree.

Have you been able to reproduce this in a clean project?
Yes, you need trees only. I atteched the archive of a project, with a minimum assets enough to reproduce the bug Dropbox - Error - Simplify your life

If so, what are the steps I can follow to reproduce this on our end?
Here is video https://youtu.be/H3gQMAc2tGQ

To be clear, the level is completely empty other than that Nav Mesh Bounds Volume?
As i told before, there is two variations of this bug:

  1. The level is empty. Map contains NavMeshBoundsVolume and RecastNavMesh-Default only, (but level contaned a lot of actors in first place, but the bug is still exists, even after deleting all of them)

  2. Level contain single tree foliage, with collisions turned on.

4

I’ve looked into this issue a bit further, and it seems the NavMesh is generated properly, but the collision of the tree is off. The pivot point of the tree is not centered, which is causing the collision to be placed in the wrong place. This explains why you are seeing the NavMesh generating in areas that appear to be incorrect.

In terms of the empty level issue, I have still been unable to reproduce this on my end. Try building paths after you’ve deleted all of your actors and see if that removes the NavMesh. Also, I do not understand why you are deleting all of the actors from a level ,but keeping the NavMesh Bounds Volume. Can you explain this please? Thank you.

5

In terms of the empty level issue, I have still been unable to reproduce this on my end.

Empty level issue is a different bug, I think. For some reason UE4 think that there are some trees still on a map, but in reality they are not. We cant reproduce this bug. I’ll give you the project with level that have NavigationMesh still having a data, while there is no objects on the map
https://www.dropbox.com/s/yemp7b3ci9kzxcf/MyProjectEmptyBug.zip?dl=0
Also, check out the video https://youtu.be/svp7zwK4oks

Try building paths after you’ve deleted all of your actors and see if that removes the NavMesh. Also, I do not understand why you are deleting all of the actors from a level ,but keeping the NavMesh Bounds Volume. Can you explain this please?

I can’t delete Navigation Mesh Volume и RecastNavMesh-Default, because I need it to build paths. After rebuilding paths issue is still exists.

6

To be clear, you were not able to reproduce this bug in a clean project? If this is the case, it could be related to that specific project.

7

Yes, we are not able to reproduce this bug in a clean project.

8

Since we are not able to reproduce this issue on our end, and you are unable to reproduce the issue in a new project, there currently is nothing further that I can do to investigate this issue. If you happen to come across a way to reproduce the bug in a clean project, feel free to re-open this thread with the repro steps.

Have a great day,

Sean Flint