|
1 | | -# Godot Debug Menu |
2 | | - |
3 | | -Displays performance information in a Godot project during gameplay. Inspired by |
4 | | -id Tech 6/7's performance overlay. |
5 | | - |
6 | | -## Why use this debug menu? |
7 | | - |
8 | | -- Compared to the Godot editor's Profiler, Monitors and Visual Profiler bottom |
9 | | - panels, you can look at an in-game debug menu while the project is running, |
10 | | - even in fullscreen if you only have a single monitor. |
11 | | - - Rendering performance is highly dependent on window size, so resizing the |
12 | | - window is not advised for reliable performance measurements in real world |
13 | | - scenarios. |
14 | | -- This debug menu accurately displays graphs and best/worst frametime metrics |
15 | | - over a period of the last 150 rendered frames, which is useful to diagnose |
16 | | - stuttering issues. The Monitor bottom panel is only updated once a second and |
17 | | - doesn't feature a 1% low FPS metric, which makes tracking stuttering |
18 | | - difficult when relying solely on the monitors. |
19 | | -- This debug menu can be used in exported projects to reliably test performance |
20 | | - without any editor interference. This includes testing on mobile and Web |
21 | | - platforms, which tend to be more difficult to set up for profiling within |
22 | | - Godot (if it's even possible). |
23 | | -- This debug menu can be used in exported projects for tech support purposes. |
24 | | - For example, in a bug report, you could ask a player to upload screenshots |
25 | | - with the debug menu visible to troubleshoot performance issues. |
26 | | - |
27 | | -External tools such as RTSS or [MangoHud](https://github.com/flightlessmango/MangoHud) |
28 | | -provide some insight on how well a project actually runs. However, they lack |
29 | | -information on engine-specific things such as per-frame CPU/GPU time and |
30 | | -graphics settings. |
| 1 | +# Debug Menu add-on demo project for Godot 4.x |
| 2 | + |
| 3 | +**Displays performance information in a Godot project during gameplay.** |
| 4 | +Can be used when running from the editor and in exported projects. |
| 5 | +Inspired by id Tech 6/7's performance overlay. |
| 6 | + |
| 7 | + |
| 8 | + |
| 9 | +This repository contains the demo project for the |
| 10 | +[Debug Menu add-on](https://github.com/godot-extended-libraries/godot-debug-menu). |
| 11 | +The add-on's code is included in this repository and is mirrored periodically. |
| 12 | + |
| 13 | +Please report issues specific to the add-on |
| 14 | +[here](https://github.com/godot-extended-libraries/godot-debug-menu), not in this repository. |
| 15 | + |
| 16 | +## Try it out |
| 17 | + |
| 18 | +> **Note** |
| 19 | +> |
| 20 | +> This add-on only supports Godot 4.x, not Godot 3.x. |
| 21 | +
|
| 22 | +### Using the Asset Library |
| 23 | + |
| 24 | +- Open the Godot project manager. |
| 25 | +- Navigate to the **Templates** tab and search for "debug menu". |
| 26 | +- Install the [*Debug Menu Demo*](https://godotengine.org/asset-library/asset/1903) project. |
| 27 | + |
| 28 | +### Manual installation |
| 29 | + |
| 30 | +Manual installation lets you try pre-release versions of this demo by following its |
| 31 | +`master` branch. |
| 32 | + |
| 33 | +- Clone this Git repository: |
| 34 | + |
| 35 | +```bash |
| 36 | +git clone https://github.com/godot-extended-libraries/godot-debug-menu-demo.git |
| 37 | +``` |
| 38 | + |
| 39 | +Alternatively, you can |
| 40 | +[download a ZIP archive](https://github.com/godot-extended-libraries/godot-debug-menu-demo/archive/master.zip) |
| 41 | +if you do not have Git installed. |
| 42 | + |
| 43 | +- Import the Godot project using the project manager and open it in the editor. |
| 44 | +- Run the main scene by pressing <kbd>F5</kbd>. |
31 | 45 |
|
32 | 46 | ## License |
33 | 47 |
|
|
0 commit comments