I am wondering if the NavMeshComponents from github is still on development.
It looks like it is been months without activity and there is nothing about navigation on the roadmap.
1 Like
No, apparently it’s part of the main release since about 5.6
Doesn’t look like it.
This is in 2017.2.0f1.
@Jakob_Unity 's last post is also almost 3 months old…
Seems like navigation is now abandoned just like networking was abandoned.
Ok I was going by [Solved]Additive Scene NavMesh Problem >"SetDestination" can only be called Error... and by the fact the API now allows runtime navmesh baking, which previously required these github assets. So what’s still missing - just the editor interface for the new features?
Hmm, yes I see.
The missing things? Well, support, updates, and bugfixes in general:
- The low-level / internal features have been added at least partially, but the editor tools were not merged into the editor
- Editor assets are outdated for v 2017.2 and don’t even work anymore.
- Still no async baking at runtime, no setting to set path calculations per frame for each agent individually, …
- Also issues keep piling up at the abandoned github repo.
Its really sad to see, people needed those features for a long time and really good progress was made.
But now Unity seemingly gave up half-way through. Seems to be becoming a recurring theme, I wonder whats up with that.
I think it’s something to do with Jakob himself rather than Unity as a studio. He was posting at least daily until late July then just suddenly stopped and there is no sign of life from him anywhere - that’s even when he stopped taking pull requests as there is one waiting from just after that time. It’s a huge mystery but it leaves me wondering whether he had made this his personal project and the rest of the Unity team don’t really even know about it. I wish there was a way to contact them - I even tried twitter to ask them to put an appearance in at these threads. So I am not sure why it seems so hard to simply say “Oh sorry we’ve had to shelve this” or whatever the case may be. It’s like the Marie Celeste - everything in suspended animation 
Maybe thats the way various of these new features come about, as side-projects for individuals who then move on elsewhere and no one is able to pick it up.
Do you still have the components from GitHub installed? If so, have you tried uninstalling them in case they are interfering with the parts of it that should be working by default?
1 Like
I don’t have them installed anymore. But I’m planning to fix the problems later since we need some of those components in our project. From what I’ve seen all the errors are really easy to fix.
Totally agree about simply telling people “we don’t have time for this anymore” (even if jakob is gone for whatever reason, isn’t his superior supposed to step in and notify people?)
Anyway, I’ll publish the improvements on the nav mesh components once I get around to updating them.
Ok but I hope you have your own fork, as I don’t think he’s taking pulls any more either
There is some development that can only be done by unity though.
From the project FAQ:
Moving NavMesh platforms: new API is required for consistently moving platforms carrying agents.
HeightMesh support and Auto Generated OffMeshLinks
What I would like to know if the project is going to be updated for further Unity3d releases. There is a branch for 2017.2 with two minor fixes made by another user (I didn’t try it myself) but nothing for 2017.3 (still in early beta though). And if we can expect any updates in functionality.
But I don’t really know if there is any Unity staff looking this sub-forum
Well, one thing is becoming fairly obvious. The one developer who was taking an active role in this feature has vanished since August. With any luck he is simply on extended Summer vacation…
Have you taken a look at navmesh builder api?
I have. I guess the project stopped before the editor bits made it into the release.
Howdy, I can check into this but I believe that dev of the navmesh components is currently halted while we wait for other pieces to fall into place.
Actually, I just looked and the 2017.2 branch of the Navmesh Components repo was updated 12 days ago.
Well that’s reassuring, thanks Is Jakob still with us, btw?
Just registering my interest and stating that a modern navigation system is not optional. If you want to remain at the forefront of game devs, you need to keep developing this if your not!
4 Likes
I know this forum hasn’t got much attention in years, but I want to say that I have used this repo in 2020 on the 2020.1.16f1 version, and it is working just as expected, if not better. I am truly taken away by the package/extension, and definitely saved me a major headache of generating NavMeshes at runtime through other means. Definitely a project that should continue to be worked on from this humble poster’s opinion.
1 Like
I’ve been avoiding using them as I have a feeling they will be abandoned as they are STILL not incorporated in a package. It would be great if someone from Unity could update us on the intention of these components!
1 Like
We’ve recently published NavMesh Components package to the Unity Registry, it is available for Unity 2019.4 and newer versions.
You can use it in your projects by adding the following dependency in your Packages\manifest.json files:
“com.unity.ai.navigation.components”: “1.0.0-exp.1”
Or by doing Add from Git, and enter “com.unity.ai.navigation.components”
It is the same version as the one on GitHub.
More information about what is coming next for navigation in Unity, should be communicated soon in the forum!
5 Likes
That’s good to hear, can you share if there will be something regarding the local avoidance improvements which helps to resolve the problem i have presented in the movie on first post in that thread?
https://discussions.unity.com/t/821269