Official Experimental AI Navigation Package

Thank you nonetheless.

 

The package hasn't been updated since they moved it over from Github a year ago. Really seems like Unity has abandoned navmesh functionality altogether, given that the built-in stuff is also not being updated despite the existence of serious bugs in the baking system. We're going to look into using third party alternatives.

The OP of this thread has not even posted on the forums since August.

 

actually they mute about the dev, see this to get the newer version https://docs.unity3d.com/Packages/com.unity.ai.navigation@1.1/changelog/CHANGELOG.html

 

Holy ... it's alive

 

:O :O :O

The navigation team never do manage to navigate to the forums do they? Must be a URL carving bug.

Spoiler: It's ALIVE!

Joking aside, please note:

• Minimum supported version is increased to Unity 2022.2

 

<

lol

 

Wow. So Unity does not have official stable nav-mesh package for 2021.3 LTS. There are only experimental packages until 2022.2 ...

Seriously?

 

The packages are just C# tooling though - you get all the source and can nose through it. Used it for years to bake without islands inside etc.

Still, the naming does put people off a lot, and that's Unity's decision (tm).

 

Why do trigger volumes get included in nav mesh generation for NavMeshSurface when geometry is set to Physics Colliders? And there's no option to not include triggers?

This seems like behaviour that nobody would want

 

lol, I'm not sure why you should trust in unity with these decisions / communications in the long run. This is navigation, there should be a stable core library (with runtime support)

they just abandon their projects left and right

 

Running 2021.3.4f1. Can't seem to add the package to the project. Even the previous version which is listed for 2019.4+ in the docs. Am I doing *it* wrong. Or do we really have to convert the project to 2022 beta ?

 

For the record this is still unstable as heck. The moment I include it (the most recent, non-experimental version) in a project, I end up with rendering errors on URP (including completely dropping my terrain textures even in edit mode), minute-long loading times for navigation mesh generation, and other issues.

I could forgive that, it's in pre-release now; but what irks me more is that they put together a several-part video tutorial back in 2017 on it, and it's still not available in late 2022. Why put together a tutorial for a hypothetical, and at least partially closed-source, feature? It literally wasn't even out of experimental yet.

Don't get me wrong, I don't believe in trolling; I try to keep my comments real and honest, but constructive. That said, I believe that Unity's built-in navigation system is functionally and fundamentally broken without these features.

(I am, literally, now building my own system on the last LTS and ignoring traditional navigation meshes entirely. I have a two-month deadline, so this hurts quite a bit.)

Was it not possible to release a stripped-down portion as a package, and leave more advanced features in experimental and pre-release?

 

https://docs.unity3d.com/2018.1/Documentation/ScriptReference/Experimental.AI.NavMeshQuery.html
https://docs.unity3d.com/2023.1/Documentation/ScriptReference/Experimental.AI.NavMeshQuery.html

For 5 years now the intended feature set hasnt been complete. Any update?

 

1.0.0-pre4 has bug in Unity 2023:

Code (CSharp):

1. Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak

Updating to newest hidden one fixes it. I wonder if that old package also has the bug but it's not shown.

 

Im having the same problem, I can't seem to find this package

 

It seem there is already 1.1.1 released

https://docs.unity3d.com/Packages/com.unity.ai.navigation@1.1/changelog/CHANGELOG.html

Also I am quite frustrated that NavMeshQuery have no API utilizing Ray object, which is very common behaviour in third person view

 

im a bit dumdum abt it but how do i generate navmesh during runtime with it?

 

I think that package are not directly related about generating navmesh at runtime. Actually, in unity, NavMesh are not technically being generated, it was singleton global data that would be modified and updated

There are some API related to this system such as NavMeshBuilder.UpdateNavMeshData

You can take a look at what we discussed about them in here

https://forum.unity.com/threads/update-navmesh-at-runtime.475237/#post-7417196

 

Throwing my hat in the ring for 2D support, essentially the feature set of https://github.com/h8man/NavMeshPlus: 2D colliders as nav-mesh sources.