There should be no need to use the NavMeshComponents GitHub using NavMesh

I just started using the NavMesh for multiple NavMesh Agents and runtime update of the mesh and I found out that to use them you must use the NavMesh Components for Runtime NavMesh Building from GitHub.

I think that it is misleading. If the features are not fully functional, they should not be partially implemented in Unity. For instance: if you cannot use different types of agents to bake the mesh, why are you allowed to create multiple agents?

What is the point of having to download assets from a GitHub repository?

I assume that the Unity developers might have some reasons but at the same time it decreases ease of use of the Unity's AI features.

Additionally, I think that, while using those downloaded components, the updating Unity for ongoing projects is more risky/difficult because you will have to update them separately.
Using the package is easier but still...

What do you think? Is there any chance that those components end up added on the editor by default?

 

Same thought about this!

 

Definitely agree. I spent two days on this issue, had to revert back to an older version because NavMeshComponents isn't supported on the current one. Being able to create different agents on the navigation menu but cannot use them. What is the point? It is extremely confusing.

 

Especially when this has been the case for years. It just seems like not much gets done around here in much of a hurry. Sure feels pretty pro.

 

there is a package you can download "AI Navigation" now that seems to be the old github repo repackaged within unity. However, it's considered "experimental" and doesn't show up by default unless you turn experimental packages on in the editor. I agree though kind of strange how even now its pretty unintuitive to actually integrate it into a project