Gamedev:DebugDrawModes - Revision history

Flozi: /* /DebugColVol (alt+v) */ about the points

2020-06-25T14:46:40Z

/DebugColVol (alt+v): about the points

← Older revision		Revision as of 15:46, 25 June 2020
Line 18:		Line 18:
	== /DebugColVol (alt+v) ==		== /DebugColVol (alt+v) ==
	[[File:DebugColVol.jpg\|400px\|left\|/DebugColVol]]		[[File:DebugColVol.jpg\|400px\|left\|/DebugColVol]]
	Draws unit and feature [[Gamedev:CollisionVolumes\|collision volumes]] as purple meshes. When hit by a weapon the meshes turn red. Since 99.0 weapon debug spheres are also drawn in this mode for the [[Animation-LuaCallins#Weapons\|AimFromWeapon()]] position, [[Animation-LuaCallins#Weapons\|QueryWeapon()]] (muzzle) position and unit target position. Shields spheres are drawn in blue.		Draws unit and feature [[Gamedev:CollisionVolumes\|collision volumes]] as purple meshes. When hit by a weapon the meshes turn red. Since 99.0 weapon debug spheres are also drawn in this mode for the [[Animation-LuaCallins#Weapons\|AimFromWeapon()]] position, [[Animation-LuaCallins#Weapons\|QueryWeapon()]] (muzzle) position and unit target position. Shields spheres are drawn in blue. Weapon 'Query' points are in red, orange if aiming. Weapon 'AimFrom' points are in yellow. The unit centre is in magenta, and if it is different the target point of the unit is in red.
	<br clear="all"/>		<br clear="all"/>

Flozi: /* /DebugColVol (alt+v) */

2020-05-28T12:04:59Z

/DebugColVol (alt+v)

← Older revision		Revision as of 13:04, 28 May 2020
Line 18:		Line 18:
	== /DebugColVol (alt+v) ==		== /DebugColVol (alt+v) ==
	[[File:DebugColVol.jpg\|400px\|left\|/DebugColVol]]		[[File:DebugColVol.jpg\|400px\|left\|/DebugColVol]]
	Draws unit and feature [[Gamedev:CollisionVolumes\|collision volumes]] as purple meshes. When hit by a weapon the meshes turn red. Since 99.0 weapon debug spheres are also drawn in this mode for the [[Animation-LuaCallins#Weapons\|AimFromWeapon()]] position, [[Animation-LuaCallins#Weapons\|QueryWeapon()]] (muzzle) position and unit target position.		Draws unit and feature [[Gamedev:CollisionVolumes\|collision volumes]] as purple meshes. When hit by a weapon the meshes turn red. Since 99.0 weapon debug spheres are also drawn in this mode for the [[Animation-LuaCallins#Weapons\|AimFromWeapon()]] position, [[Animation-LuaCallins#Weapons\|QueryWeapon()]] (muzzle) position and unit target position. Shields spheres are drawn in blue.
	<br clear="all"/>		<br clear="all"/>

Flozi: /* /DebugColVol (alt+v) */ 99.0- draw weapon debug spheres in /debugcolvol (aimfrom pos, muzzle pos, target pos)

2015-07-18T11:57:14Z

/DebugColVol (alt+v): 99.0- draw weapon debug spheres in /debugcolvol (aimfrom pos, muzzle pos, target pos)

← Older revision		Revision as of 12:57, 18 July 2015
Line 18:		Line 18:
	== /DebugColVol (alt+v) ==		== /DebugColVol (alt+v) ==
	[[File:DebugColVol.jpg\|400px\|left\|/DebugColVol]]		[[File:DebugColVol.jpg\|400px\|left\|/DebugColVol]]
	Draws unit and feature [[Gamedev:CollisionVolumes\|collision volumes]] as purple meshes. When hit by a weapon the meshes turn red.		Draws unit and feature [[Gamedev:CollisionVolumes\|collision volumes]] as purple meshes. When hit by a weapon the meshes turn red. Since 99.0 weapon debug spheres are also drawn in this mode for the [[Animation-LuaCallins#Weapons\|AimFromWeapon()]] position, [[Animation-LuaCallins#Weapons\|QueryWeapon()]] (muzzle) position and unit target position.
	<br clear="all"/>		<br clear="all"/>

Abma: fix link

2015-02-05T23:47:48Z

fix link

← Older revision		Revision as of 00:47, 6 February 2015
Line 32:		Line 32:

	== /DebugTraceRay ==		== /DebugTraceRay ==
	It is meant for debugging trajectories of ballistic projectiles. [https://springrts.com/mantis/view.php?id=4664\| Currently broken in 98.0]		It is meant for debugging trajectories of ballistic projectiles. [https://springrts.com/mantis/view.php?id=4664 Currently broken in 98.0]

	<br clear="all"/>		<br clear="all"/>

Abma: /* /DebugTraceRay */

2015-02-05T23:46:50Z

/DebugTraceRay

← Older revision		Revision as of 00:46, 6 February 2015
Line 32:		Line 32:

	== /DebugTraceRay ==		== /DebugTraceRay ==
	It is meant for debugging trajectories of ballistic projectiles. [https://springrts.com/mantis/view.php?id=4664\|Currently broken in 98.0]		It is meant for debugging trajectories of ballistic projectiles. [https://springrts.com/mantis/view.php?id=4664\| Currently broken in 98.0]

	<br clear="all"/>		<br clear="all"/>

Abma: /* /DebugTraceRay */

2015-02-05T23:45:56Z

/DebugTraceRay

← Older revision		Revision as of 00:45, 6 February 2015
Line 32:		Line 32:

	== /DebugTraceRay ==		== /DebugTraceRay ==
	~~Is intended to draw the result~~ of ~~ray tracing calls~~. Currently broken in 98.0.		It is meant for debugging trajectories of ballistic projectiles. [https://springrts.com/mantis/view.php?id=4664\|Currently broken in 98.0]

	<br clear="all"/>		<br clear="all"/>

Flozi: category

2014-10-12T14:10:59Z

Flozi: Flozi moved page User:Flozi/Gamedev:DebugDrawModes to Gamedev:DebugDrawModes without leaving a redirect: done

2014-10-12T14:10:37Z

Flozi moved page User:Flozi/Gamedev:DebugDrawModes to Gamedev:DebugDrawModes without leaving a redirect: done

← Older revision	Revision as of 15:10, 12 October 2014
(No difference)

Flozi: first draft

2014-10-12T14:02:39Z

first draft

New page

= Debug Drawing Modes =
Spring has several drawing modes which are useful for debugging and performance checking.
They are listed below by [[UI commands]] with their default key binding.

== /Debug (alt+b) ==
[[File:Debug.jpg|400px|left|/Debug]]
Draws a toggleable list of engine functions and a breakdown of how much time is spent computing them. When toggled on a line graph is drawn to illustrate the change in performance over time.

Since 97.0 there is a new '''Frame Grapher''' visualisation which shows how the last half-second was spent:

* Green are video frames
* Red are simframes
* Blue is swapBuffer (gpu/vsync)
* Pink is lua gc
<br clear="all"/>

== /DebugColVol (alt+v) ==
[[File:DebugColVol.jpg|400px|left|/DebugColVol]]
Draws unit and feature [[Gamedev:CollisionVolumes|collision volumes]] as purple meshes. When hit by a weapon the meshes turn red.
<br clear="all"/>

== /DebugPath (alt+p) ==
[[File:DebugPath_Close.jpg|400px|left|/DebugPath Close up view]][[File:DebugPath_Far.jpg|400px|left|/DebugPath Far out view]]

Draws pathfinder routes, colour coded by accuracy.

* Red is the most finely computed pathing
* Green is intermediate paths
* Blue is least accurate long range path
<br clear="all"/>

== /DebugTraceRay ==
Is intended to draw the result of ray tracing calls. Currently broken in 98.0.

<br clear="all"/>

== /DebugDrawAI ==
[[File:DebugDrawAI_E232AI.jpg|400px|left|/DebugDrawAI implemented in E232AI]]
This mode is toggled through the engine but is up to the native AI to implement itself. The image shows how [[AI:Skirmish:List|E232AI]] implements a real-time threatmap rendering and a real-time performance profiler.

← Older revision		Revision as of 15:10, 12 October 2014
Line 39:		Line 39:
	[[File:DebugDrawAI_E232AI.jpg\|400px\|left\|/DebugDrawAI implemented in E232AI]]		[[File:DebugDrawAI_E232AI.jpg\|400px\|left\|/DebugDrawAI implemented in E232AI]]
	This mode is toggled through the engine but is up to the native AI to implement itself. The image shows how [[AI:Skirmish:List\|E232AI]] implements a real-time threatmap rendering and a real-time performance profiler.		This mode is toggled through the engine but is up to the native AI to implement itself. The image shows how [[AI:Skirmish:List\|E232AI]] implements a real-time threatmap rendering and a real-time performance profiler.

			[[Category: Game Dev]]