# Navigation plugin computeSmooth

**URL:** <https://forum.babylonjs.com/t/navigation-plugin-computesmooth/53169>\
**Category:** Questions\
**Created:** [September 2, 2024, 10:10am UTC](https://forum.babylonjs.com/t/navigation-plugin-computesmooth/53169 "2024-09-02T10:10:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Cedric](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/cedric/32/2742_2.png) [@Cedric](https://forum.babylonjs.com/u/Cedric)\
**Post date:** [September 2, 2024, 10:16am UTC](https://forum.babylonjs.com/t/navigation-plugin-computesmooth/53169/2 "2024-09-02T10:16:32Z")

</div>

I’ve found some context here : [NavMesh: Paths don't follow NavMesh surface - #10 by Cedric](https://forum.babylonjs.com/t/navmesh-paths-dont-follow-navmesh-surface/46713/10)

and related PR : [expose seed and computepath smooth by CedricGuillemet · Pull Request #265 · BabylonJS/Extensions · GitHub](https://github.com/BabylonJS/Extensions/pull/265)

IIRC, default path computation is straight and does not respect navmesh geometry. The change improves path computation with more respectful to corridors and heights.

I’m all in with recast.js replacement as long as features available and documented are present 🙂

---

_[View the full topic](https://forum.babylonjs.com/t/navigation-plugin-computesmooth/53169)._