Difference between revisions of "Debug"

From Luanti Wiki
Jump to navigation Jump to search
(→‎Profiler graphs: list graphs)
(Replaced content with "[https://dev.luanti.org/debug/ This page has moved to the Luanti Developer Wiki]")
Tag: Replaced
 
(8 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Languages}}
+
[https://dev.luanti.org/debug/ This page has moved to the Luanti Developer Wiki]
__NOTOC__
 
{{incomplete}}
 
The '''debug screen''' can be access by pressing the <kbd>F5</kbd> key (by default) and shows various technical information about Minetest which are mostly interesting for developers, but some information are also useful for players, especially the [[coordinates]].
 
 
 
It contains various information useful for development and testing. Press <kbd>F5</kbd> to access different debug screen modes:
 
 
 
* Debug screen disabled
 
* Debug info
 
* Debug info + profiler graph
 
* Debug info + wireframe (only with “debug” [[Privileges|privilege]])
 
 
 
== Debug info ==
 
=== Basic debug info ===
 
The basic debug information is located at the top left of the screen. It looks like this:
 
 
 
[[File:Debug.png]]
 
 
 
==== First row ====
 
* '''Minetest X.Y.Z''': The [[Version number|version number]] of [[Minetest]]
 
* '''FPS''': Number of [https://en.wikipedia.org/wiki/Frames_per_second frames per second], denotes how fast everything is [https://en.wikipedia.org/wiki/Rendering_%28computer_graphics%29 rendered]. Higher = better. It is limited at 60 by default. An FPS lower than 30 is pretty bad (try to lower graphics settings or close some background applications)
 
* '''drawtime''': An average time (in milliseconds) it's taking to render each frame, not including processing other than rendering. Lower is better
 
* '''dtime jitter''': Jitter in the time difference between rendering frames, including all processing. Minetest remembers the previous drawtime values over a few seconds in the past. This value shows how much higher than the average the ''peak'' value (over the last few seconds) was. A value of 50% or lower is considered okay
 
* '''view range''': Your current viewing range in nodes. “All” means unlimited. By default, you can adjust this with <kbd>+</kbd>, <kbd>-</kbd> and <kbd>R</kbd>.
 
* '''RTT''': [https://en.wikipedia.org/wiki/Round_trip_time Round Trip Time] in seconds. This is especially important when connected to a server. Lower is better
 
 
 
==== Second row ====
 
* '''pos''': Your [[coordinates]]: X, Y and Z
 
* '''yaw''': Your current horizontal looking direction (also known as “yaw”) in degrees (0-360). For convenience, also the cardinal direction (e.g. “North”)<ref>0° translates to “North”, 270° to “East”, 180° to “South” and 90° to “West”. Note that the concept of cardinal directions does not really make sense in Minetest, as the world is a cube, not a sphere, and there are no poles. In this context, the names “North”, “South”, “West” and “East” are just synonyms for the 4 directions</ref> as well as the approximate axis direction are shown (e.g. “+Z”)
 
* '''seed''': The [https://en.wikipedia.org/wiki/Random_seed random seed] used by the [[map generator]] to generate the current world. Equal seeds (along with equal mapen settings) will lead to equal worlds
 
* '''pointed''': The [[Itemstrings|itemstring]] of the current pointed [[Blocks|node]] (if any).
 
* '''param2''': Value of <code>param2</code> of the current pointed node (if any). This contains some additional info for a node, such as rotation, color, etc, which is important for programmers. The meaning of <code>param2</code> is explained in the Lua API documentation.
 
 
 
=== When pointing an entity ===
 
When you point an entity or object (such as a dropped item or player), the following information is shown to the left:
 
 
 
* Entity type: See [http://dev.minetest.net/ActiveObject ActiveObject] on the Minetest Developer Wiki
 
* '''hp''': Health in hit points (→[[Player#Health]])
 
* '''armor''': Armor groups, determine how the entity receives damage
 
 
 
=== Profiler graphs ===
 
The profiler graphs show the performance of Minetest in a more detailed fashion.
 
 
 
The following graphs are available:
 
 
 
* '''rudp_rtt'''
 
* '''rudp_jitter'''
 
* '''packets_lost'''
 
* '''num_processed_meshes'''
 
* '''mainloop_sleep'''
 
* '''mainloop_other'''
 
* '''mainloop_dtime'''
 
* '''mainloop_draw'''
 
* '''client_received_packets'''
 
 
 
'''TODO: Explain the meaning of these graphs!'''
 
 
 
== Footnotes ==
 
<references/>
 

Latest revision as of 19:58, 22 December 2024