Godot version:
e1f2feec2eccbc0589a66b84ea8b3af34c1740b4
Issue description:
No navigation mesh generated on bake.
Error message:
ERROR: _navmesh_unlink: Condition ' !nm.linked ' is true.
At: scene/3d/navigation.cpp:145.
Steps to reproduce:
I add Navigation node to a scene, then add MeshInstance as a child of it (I used both imported meshes
and stock godot primitives), then as child of MeshInstance I add NavigationMeshInstance. On that I create NavigationMesh and press bake. No navigation mesh generated.
I see the following message on console:
ERROR: _navmesh_unlink: Condition ' !nm.linked ' is true.
At: scene/3d/navigation.cpp:145.
Didn't the _NavigationMeshInstance_ have to be a direct child of _Navigation_, and the _MeshInstance(s)_ have to be children of the _NavigationMeshInstance_ in order to be able to bake the navmesh? I thought that was the only way it was supposed to work.
Well, as I see 3D navigation example I see Navigation/Mesh/Navmesh tree.
Something should be corrected.
On Wed, Jul 18, 2018 at 3:01 PM, Carjan Radu-Liviu <[email protected]
wrote:
Didn't the NavigationMeshInstance have to be a direct child of
Navigation, and the MeshInstance(s) have to be children of the
NavigationMeshInstance in order to be able to bake the navmesh? I
thought that was the only way it was supposed to work. I have tested it and
it works on my PC.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/20208#issuecomment-405906444,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAX04t4wsAYGuH-tNL0_UtCYZyuI30Mks5uHyOrgaJpZM4VSU1g
.
@slapin I just checked this, the order is:
Navigation/NavigationMeshInstance/Map
Map is the Spatial that holds all the map with their collisions.
Thanks everyone, this looks like nav3d example issue as it have order
reversed.
On Mon, Jul 23, 2018 at 12:42 PM, kakoeimon notifications@github.com
wrote:
@slapin https://github.com/slapin I just checked this, the order is:
Navigation/NavigationMeshInstance/Map
Map is the Spatial that holds all the map with their collisions.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/20208#issuecomment-407000261,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAX0yP1KbO2GNETMw6yserQUnjivqnkks5uJZqDgaJpZM4VSU1g
.
As this is not Godot issue, but example issue, this should be closed.
Most helpful comment
Thanks everyone, this looks like nav3d example issue as it have order
reversed.
On Mon, Jul 23, 2018 at 12:42 PM, kakoeimon notifications@github.com
wrote: