You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add tip and warning about TileMap build-in navigation
Adds a tip to TileMap navigation section that informs users to prefer baking the TileMap navigation.
Also adds a warning that 2D navigation meshes can not overlap.
Copy file name to clipboardExpand all lines: tutorials/2d/using_tilemaps.rst
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,15 @@ Navigation
81
81
- **Navigation Visible** Whether or not the TileMapLayer's navigation meshes are
82
82
visible. If set to default then it depends on the show navigation debug settings.
83
83
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
+
84
93
You can reorder layers by drag-and-dropping their node in the Scene tab. You can
85
94
also switch between which TileMapLayer node you're working on by using the buttons
0 commit comments