Skip to content

Commit c34eaeb

Browse files
authored
Merge pull request #9736 from smix8/tilemap_navwarn
Add tip and warning about TileMap build-in navigation
2 parents e9f7c18 + 48343be commit c34eaeb

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

tutorials/2d/using_tilemaps.rst

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,15 @@ Navigation
8181
- **Navigation Visible** Whether or not the TileMapLayer's navigation meshes are
8282
visible. If set to default then it depends on the show navigation debug settings.
8383

84+
.. tip::
85+
86+
TileMap built-in navigation has many practical limitations that result in inferior pathfinding performance and pathfollowing quality.
87+
88+
After designing the TileMap consider baking it to a more optimized navigation mesh (and disabling the TileMap NavigationLayer) using a :ref:`NavigationRegion2D <class_NavigationRegion2D>` or the :ref:`NavigationServer2D <class_NavigationServer2D>`. See :ref:`doc_navigation_using_navigationmeshes` for additional information.
89+
90+
.. warning::
91+
2D navigation meshes can not be "layered" or stacked on top of each other like visuals or physic shapes. Attempting to stack navigation meshes on the same navigation map will result in merge and logical errors that break the pathfinding.
92+
8493
You can reorder layers by drag-and-dropping their node in the Scene tab. You can
8594
also switch between which TileMapLayer node you're working on by using the buttons
8695
in the top right corner of the TileMap editor.

0 commit comments

Comments
 (0)