NavMesh Extension (NavMesh Drawing & Portals)

I think he is looking to auto generate a nav mesh using the Unity Bake option and then to be able to edit that nav mesh. That is the situation I am in at least. I do not use Unity's agent system but I would like to generate a nav mesh using the bake system. Then I would like to be able to edit polygons on that mesh. Say delete some, add polygons in other places, etc.

 

Unity only provides API to pass in mesh data for baking NavMesh data. Since there is no API to edit existing (baked) NavMeshes, this is impossible to do.

 

Can this be used to have A.I drive/walk/run on spheres? I would like to use it for a planetary game well a series of planetary games

 

@Vampyr_Engel It would be very difficult to use it on spheres, since the editor tools produce mostly flat or diagonal meshes, so I wouldn't recommend it for your use case.

 

OK thanks

 

Can anyone tell me how to resume drawing current mesh in navmesh extension?
I don't know how I did it in the first place but then I don't know how.

 

@umair21 Did you select your mesh game object so that its NavMesh Extension component shows up in the Inspector? There is a button for entering Edit mode, which allows adding or removing vertices.

 

With the release of Unity 2019.1 this week, we have deprecated our asset "NavMesh Extension" on the Unity Asset Store, effectively removing it from sale.

Existing customers can still download it via their purchased assets overview. Also, we are going to provide support on our forum for as long as possible. However, please note that there won't be further updates, in the cases of feature requests, bugs or Unity incompatibility errors.

NavMesh Extension had a very specific use case in mind when releasing it on the Asset Store - the ability to easily draw (flat) walkable meshes in smaller environments, like rooms, houses, or cities. After 5 years of supporting it and adding new features now and then, it became clear that the scope this asset was designed to cover, was not enough in order to appeal for a broad audience. In addition to Unity limitations we could not work around at that time (such as 2D NavMeshes, or modifying the NavMesh data array at runtime), we received a lot of mixed reviews on the Unity Asset Store. Finally, Unity introduced their own update on the NavMesh features in the 2017.2 cycle, called NavMesh components. As these components basically replace our asset in many areas, I do recommend using them instead. Now with the features transitioned to official Unity components and us providing support for 2 additional years, interest in our asset has almost vanished, so we pushed that "exit" button to put more energy and focus on our other assets.

Thank you for your understanding.