JoltPhysics VS NavMeshComponents

There is now also https://github.com/jrouwe/JoltPhysics which is used in Horizon Forbidden West.

Apparenty, this is a game engine used by Horizon Forbidden West and I was curious what you all think about this project: https://github.com/jrouwe/JoltPhysics

As far as physics engines go: Jolt currently seems to kinda disrupt the decade-long equilibrium, at least as far as I'm aware:

https://github.com/jrouwe/JoltPhysics

No, they replaced Bullet with Jolt. That is considerably more than "some adjustment", regardless of what you think of the result.

A multithreaded rigid-body engine for games: https://github.com/jrouwe/JoltPhysics

Would you rather they use Jolt Physics? https://github.com/jrouwe/JoltPhysics S&box is thinking of using this engine instead of Source 2's Rubicon. As they say, maybe someone could / would hook up Jolt as a GDExtension.

So if you use the github Navmesh Components, you can change the voxel height and tile size manually. That MIGHT be able to fix the seam issue you have.

There's a Brackeys tutorial on this, but it's four years old and to get it to work you'll have to add unity.ai.navigation as a package. It used to be included in UnityEngine.AI, but now it's referred to as experimental in the documentation as well as the Navigation window in 2021 LTS. It hasn't been updated in three years so I assume that experiment failed. Below is how to achieve the same thing with the current built in functionality.

I've been using Unity for a few months now and what is most frustrating is how lazy the company presents itself.

They basically found that the Asset Store is such a huge source of revenue for them that they now completely over-leverage it and abuse the community for profit. For the few things they do ship, they routinely break things for backwards incompatibility or literally just ship half complete "products". If you want to do anything meaningful in Unity you either have to build it yourself from the ground up or buy plugins.

An example: their AI navigation system is so lacking in features, they haven't updated it in nearly two years, and the last ship they did was literally half broken and buggy for several use cases. https://github.com/Unity-Technologies/NavMeshComponents

I assume the ai package you included was the same as this https://github.com/Unity-Technologies/NavMeshComponents ? If so I would look at the examples there and adapt the local navmesh builder to your usecase. You don't need to run it every frame, you could run it every X seconds or after travelling a certain distance to save performance.

If you want to stick with standard unity stuff to start with, the Unity NavMeshComponents are a good start:

1)The built in Navmesh of unity. I prefer using NavMeshComponents https://github.com/Unity-Technologies/NavMeshComponents

You can use NavMeshBuilder.UpdateNavMeshDataAsync to bake parts of a new navmesh at runtime in a very efficient way (i.e. won't slow down framerate), but the documentation is both confusing and nearly non-existent. The best way to learn how to do this properly is to carefully study Unity's LocalNavMeshBuilder code and extrapolate. I seriously wish they'd expand on this and make it more accessible, but so far this is the best I've found.