Accueil Explorer Aide
Connexion
godotengine
/
godot-docs
miroir de https://github.com/godotengine/godot-docs
Suivre 1
Voter 1
Fork 0
Fichiers
Aborescence: 7f2c19c1f3
Branches Tags
godot-docs
/
tutorials
/
navigation
/
navigation_debug_tools.rst

navigation_debug_tools.rst 4.3 KB
Historique Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495 
  1. .. _doc_navigation_debug_tools:
    2. 

  2. 

  3. Navigation debug tools
    4. 

  4. ======================
    5. 

  5. 

  6. .. note::
    7. 

  7. 

  8.     The debug tools, properties and functions are only available in Godot debug builds.
    9. 

  9.     Do not use any of them in code that will be part of a release build.
    10. 

  10. 

  11. Enabling navigation debug
    12. 

  12. -------------------------
    13. 

  13. 

  14. The navigation debug visualizations are enabled by default inside the editor.
    15. 

  15. To visualize navigation meshes and connections at runtime too, enable the option **Visible Navigation** in the editor **Debug** menu.
    16. 

  16. 

  17. .. image:: img/navigation_debug_toggle.png
    18. 

  18. 

  19. In Godot debug builds the navigation debug can also be toggled through the NavigationServer singletons from scripts.
    20. 

  20. 

  21. .. tabs::
    22. 

  22.  .. code-tab:: gdscript GDScript
    23. 

  23. 

  24.     NavigationServer2D.set_debug_enabled(false)
    25. 

  25.     NavigationServer3D.set_debug_enabled(true)
    26. 

  26. 

  27.  .. code-tab:: csharp
    28. 

  28. 

  29.     NavigationServer2D.SetDebugEnabled(false);
    30. 

  30.     NavigationServer3D.SetDebugEnabled(true);
    31. 

  31. 

  32. Debug visualizations are currently based on Nodes in the SceneTree. If the :ref:`NavigationServer2D<class_NavigationServer2D>` or :ref:`NavigationServer3D<class_NavigationServer3D>`
    33. 

  33. APIs are used exclusively then changes will not be reflected by the debug navigation tools.
    34. 

  34. 

  35. Navigation debug settings
    36. 

  36. -------------------------
    37. 

  37. 

  38. The appearance of navigation debug can be changed in the ProjectSettings under ``debug/shapes/navigation``.
    39. 

  39. Certain debug features can also be enabled or disabled at will but may require a scene restart to take effect.
    40. 

  40. 

  41. .. image:: img/nav_debug_settings.png
    42. 

  42. 

  43. Debug navigation mesh polygons
    44. 

  44. ------------------------------
    45. 

  45. 

  46. If ``enable_edge_lines`` is enabled, the edges of navigation mesh polygons will be highlighted.
    47. 

  47. If ``enable_edge_lines_xray`` is also enabled, the edges of navigation meshes will be visible through geometry.
    48. 

  48. 

  49. If ``enable_geometry_face_random_color`` is enabled, the color of each navigation mesh face will be mixed with a random color that is itself mixed with the color specified in ``geometry_face_color``.
    50. 

  50. 

  51. .. image:: img/nav_debug_xray_edge_lines.png
    52. 

  52. 

  53. Debug edge connections
    54. 

  54. ----------------------
    55. 

  55. 

  56. When two navigation meshes are connected within ``edge_connection_margin`` distance, the connection is overlaid.
    57. 

  57. The color of the overlay is controlled by ``edge_connection_color``.
    58. 

  58. The connections can be made visible through geometry with ``enable_edge_connections_xray``.
    59. 

  59. 

  60. .. image:: img/nav_edge_connection2d.gif
    61. 

  61. 

  62. .. image:: img/nav_edge_connection3d.gif
    63. 

  63. 

  64. .. note::
    65. 

  65. 

  66.     Edge connections are only visible when the NavigationServer is active.
    67. 

  67. 

  68. Debug performance
    69. 

  69. -----------------
    70. 

  70. 

  71. To measure NavigationServer performance a dedicated monitor exists that can be found within the Editor Debugger under *Debugger->Monitors->Navigation Process*.
    72. 

  72. 

  73. .. image:: img/navigation_debug_performance1.webp
    74. 

  74. 

  75. Navigation Process shows how long the NavigationServer spends updating its internals this update frame in milliseconds.
    76. 

  76. Navigation Process works similar to Process for visual frame rendering and Physics Process for collision and fixed updates.
    77. 

  77. 

  78. Navigation Process accounts for all updates to **navigation maps**, **navigation regions** and **navigation agents** as well as all the **avoidance calculations** for the update frame.
    79. 

  79. 

  80. .. note::
    81. 

  81. 

  82.     Navigation Process does NOT include pathfinding performance cause pathfinding operates on the navigation map data independently from the server process update.
    83. 

  83. 

  84. Navigation Process should be in general kept as low and as stable as possible for runtime performance to avoid frame rate issues.
    85. 

  85. Note that since the NavigationServer process update happens in the middle of the physics update an increase in Navigation Process will automatically increase Physics Process by the same amount.
    86. 

  86. 

  87. Navigation also provides more detailed statistics about the current navigation related objects and navigation map composition on the NavigationServer.
    88. 

  88. 

  89. .. image:: img/navigation_debug_performance2.webp
    90. 

  90. 

  91. Navigation statistics shown here can not be judged as good or bad for performance as it depends entirely on the project what can be considered as reasonable or horribly excessive.
    92. 

  92. 

  93. Navigation statistics help with identifying performance bottlenecks that are less obvious because the source might not always have a visible representation.
    94. 

  94. E.g. pathfinding performance issues created by overly detailed navigation meshes with thousand of edges / polygons or problems caused by procedural navigation gone wrong.
    95. 

  95.