overview_of_debugging_tools.rst 2.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. .. _doc_overview_of_debugging_tools:
  2. Overview of debugging tools
  3. ===========================
  4. Introduction
  5. ------------
  6. When developing your game, you would want to test your game and debug when problems occurred. Godot provides several debugging options and tools which aid your debugging process.
  7. Debug options
  8. -------------
  9. There are a few options that you can enable when running your game in the editor which can help you in debugging your game.
  10. These options are located in ``DEBUG`` in the main menus.
  11. .. image:: img/overview_debug.png
  12. Here are the descriptions of the options:
  13. Deploy with Remote Debug
  14. ++++++++++++++++++++++++
  15. When exporting and deploying, the resulting executable will attempt to connect to the IP of your computer, in order to be debugged.
  16. Small Deploy with Network FS
  17. ++++++++++++++++++++++++++++
  18. Export or deploy will produce minimal executable. The filesystem will be provided from the project by the editor over the network.
  19. On Android, deploy will use the USB cable for faster performance. This option speeds up testing for games with a large footprint.
  20. Visible Collision Shapes
  21. ++++++++++++++++++++++++
  22. Collision shapes and raycast nodes(for 2D and 3D) will be visible on the running game.
  23. Visible Navigation
  24. ++++++++++++++++++
  25. Navigation meshes and polygons will be visible on the running game.
  26. Sync Scene Changes
  27. ++++++++++++++++++
  28. Any changes made to the scene in the editor will be replicated in the running game.
  29. When used remotely on a device, this is more efficient with network filesystem.
  30. Sync Script Changes
  31. +++++++++++++++++++
  32. Any script that is saved will be reloaded on the running game.
  33. When used remotely on a device, this is more efficient with network filesystem.
  34. Debugging tools
  35. ---------------
  36. The ``Debugger`` is the second option in the bottom panel. Click on it and a new panel occurs.
  37. .. image:: img/overview_debugger.png
  38. The ``Debugger`` provides certain tools under different tabs.
  39. Here are some brief descriptions of the tools:
  40. Debugger
  41. ++++++++
  42. Monitor the game running process.
  43. Errors
  44. ++++++
  45. Print out errors when running the game.
  46. Profiler
  47. ++++++++
  48. Profiling the performance of the any function call in the running game.
  49. Monitors
  50. ++++++++
  51. Monitors the performance of the running game, such as the fps and physics collisions.
  52. Video Mem
  53. +++++++++
  54. Listing the video memory usage of the running game.
  55. Misc
  56. ++++
  57. Miscellaneous options for debug.
  58. Remote in Scene dock
  59. --------------------
  60. When running your game, a bar will occur at the top of the ``Scene`` dock. You can switch to ``Remote`` and inspect or change the nodes' parameters in the running game.
  61. .. image:: img/overview_remote.png
  62. .. note:: Some editor settings related to debugging can be found inside the ``Editor Settings``, under Network>Debug and Debugger sections.