Official There's a new Navigation package in town!

Does this package support Entities?

 

@ChinnyBJ I hope you are still at Unity.

Can you please tell us if the massive layoffs will affect the development of the new navigation package? Thanks.

 

This really is a huge problem. I am facing the same problem at the moment. My agents are just running/clipping through all the terrain trees. And there is nothing i could do to get the navmesh to work..

My player character collides with the trees, so the Tree Colliders seem to be set up correctly.

Does someone know a solution to that problem?

 

@ChinnyBJ Thank you for this update, I am happy to see Unity's new modular design paying off and resulting in smaller build when unnecessary functionality is not forced into the build because of the new package system.

However, I am having a problem, I am on 2022.2.12, fresh project, imported the navigation package, and opened the new 'navigation' window, not the legacy one, but I can't find an option to bake in it.



It's funny because the documentation mentions to use the obsolete window to bake.

 

You need to use a gameobject with a navmesh surface component on it, that is the only way with the new package I think

 

That worked perfectly, thanks.

 

I was lost, now...im im PANIC

 

Super annoying that NavMeshSurface is in the wrong namespace

 

Does anyone know of this package would work well in an ECS heavy project? It seems like it relies on GameObjects so I assume the answer is no.

 

Has anyone had any success generating bidirectional links with the NavMeshSurface component? They only seem to work in a single direction and I would like to change that, however when I check the documentation I get a "Sorry this page seems to be missing!".

https://docs.unity3d.com/Packages/c...1/manual/BuildingOffMeshLinksAutomatically.md
https://docs.unity3d.com/Packages/com.unity.ai.navigation@1.1/manual/CreateOffMeshLink.html

Edit: after a googling I found out you can't traverse upwards. Having the same flexibility of manually created links is a feature request. Thanks.

 

So, with the deprecation of everything in UnityEngine.Experimental.AI is there a replacement on the horizon soon? NavMeshQuery was extremely useful and starting from 2023.2.0a22+ it's no longer available for use.

 

Is that official currently working on dots navigation and current navigation system will be deprecated soon?

 

Thanks for the response, I stand corrected regarding the removal remark. However this still doesn't answer my initial question where I've asked if a replacement of those experimental functions will be added. Do you happen to know the answer to that?

 

But wasn't navmesh query the only thing for navigation in DOTS?

 

Hey,
This is a super interesting topic, and I hope my opinions won't offend anybody. I'd love to share my perspective.
First of all, it's really great to see navigation getting more attention, especially with the increased control over the NavMesh building process. I've noticed users creating many cool extensions out of it, like this one: https://github.com/h8man/NavMeshPlus.

@laurentlavigne's comment might come across as a bit harsh, but I do share a similar sentiment with him. "Improved Collision Avoidance" and "Navigation authoring UX & workflow improvements" seem to fall more into the "nice to have" category. Both of these can already be addressed at the user level, and the asset store offers good solutions for them (of course, as a publisher, my perspective might be seen as biased). However, working on the low-level navmesh side is a true roadblock, at least in my opinion, and probably for others as well. For this reason, I would love to see the roadmap focus more on providing extensible groundwork, rather than trying to tackle specific use cases.

To be honest, I'm quite concerned about this. I understand that the API was never intended to be available as a proper API interaction with the NavMesh in a Burst-compatible way. However, this decision could potentially impact the adoption of Unity's nav mesh in data-oriented projects. As a matter of fact, I know that I might have to remove Unity nav mesh integration from my packages going forward in 2024. I'm curious to know the main reasoning behind this decision. Perhaps the API can be left as is, with clear communication that it won't be extended, in order to save development time on your side and ultimately removed once replacement API is set.

P.S. I am creator of Agents Navigation and Local Avoidance.

 

i'm not sure if i fully understand this but, in this case, the asset store should be a place for alternatives, not the only solution, because they costs money, money that many devs (including me) do not have, do not forget that releasing a game is not exactly free either

 

I am using Unity 2022.3.3f1, I install AI Navigation and these error show up. Can someone help me fix this!

 

Does this package work with Entities? Is there lower level API that can be used with entities?

 

Yeah, there was, and it was deprecated just recently. Genius move right?

 

I’m sorry to hear that. I think a good way to design a package is to design some lower level APIs that are public that you then build the higher level APIs and the UX and quality of life features on. Then the average user can use the higher level APIs and then users with advanced use cases are free to use the lower level APIs. I believe the Splines package was designed this way.