Pathfinding - Revision history

Geep: Add new section Viewing AI Current Path Goals and Obstacles

2024-10-10T18:02:42Z

Add new section Viewing AI Current Path Goals and Obstacles

← Older revision		Revision as of 18:02, 10 October 2024
Line 105:		Line 105:
	The cvar "tdm_ai_showdest 1" will draw arrows from AI to their intended destination.		The cvar "tdm_ai_showdest 1" will draw arrows from AI to their intended destination.

			==Viewing AI Current Path Goals and Obstacles==
			''Adapted from [[https://forums.thedarkmod.com/index.php?/topic/9082-newbie-darkradiant-questions/&do=findComment&comment=497044 boissiere, 2024]]''

			The following CVars, if set, give visual indications as to what AIs are actually trying to do:

			* tdm_ai_debug_blocked
			* tdm_ai_showdest
			* tdm_ai_showtasks

			For instance, suppose there's an intermittent behavioral problem, i.e., an AI sometimes stops proceeding along a path. Using the CVars to compare what happens when it works against when it doesn't may provide insight.

			See further below for more troubleshooting ideas.

	==Why ''func_static'' Brushes Anyway?==		==Why ''func_static'' Brushes Anyway?==
Line 118:		Line 130:

	==Problems, Troubleshooting==		==Problems, Troubleshooting==
			''See also the "Viewing..." sections above.''

	If AI are walking on patches and behaving strangely, make sure you have layers of monsterclip or worldspawn underneath the patch.		If AI are walking on patches and behaving strangely, make sure you have layers of monsterclip or worldspawn underneath the patch.

Frost Salamander: add steps to create func_aas_obstacle entity

2022-07-12T19:38:59Z

add steps to create func_aas_obstacle entity

← Older revision		Revision as of 19:38, 12 July 2022
Line 66:		Line 66:

	Based on changing conditions you might want an available route to become blocked, or vice-versa, open up later. MonsterClip is fixed, but you may enable and disable a func_aas_obstacle by triggering it. The "start_on" spawnarg will have it active (1) or inactive (0) to begin with.		Based on changing conditions you might want an available route to become blocked, or vice-versa, open up later. MonsterClip is fixed, but you may enable and disable a func_aas_obstacle by triggering it. The "start_on" spawnarg will have it active (1) or inactive (0) to begin with.

			To create a func_aas_obstacle entity:
			# create a brush of the desired size and shape
			# give it the texture 'textures/editor/aasobstacle'
			# convert it to a func_aas_obstacle entity (right-click -> Convert to Entity -> Func/func_aas_obstacle)


	Note, if you want it to exist on a certain difficulty level, but not another, you have to use "diff_#_change_0" "start_on" with "diff_#_arg_0" "0" to change the start_on spawnarg rather than simply "diff_#_nospawn", as the latter won't remove it without quitting/reloading TDM and cause pathing issues.		Note, if you want it to exist on a certain difficulty level, but not another, you have to use "diff_#_change_0" "start_on" with "diff_#_arg_0" "0" to change the start_on spawnarg rather than simply "diff_#_nospawn", as the latter won't remove it without quitting/reloading TDM and cause pathing issues.

Geep: Add links to Teleporting entities

2021-12-14T19:06:05Z

Add links to Teleporting entities

← Older revision		Revision as of 19:06, 14 December 2021
Line 1:		Line 1:
	''Written by Fidcal''		''Written by Fidcal''

	For information on using path entities, see [[Path Nodes]].		For information on using path entities, see [[Path Nodes]]. For pathfinding after teleport, see [[Teleporting entities]].

	==Introduction==		==Introduction==

Dragofer at 09:30, 27 February 2019

2019-02-27T09:30:05Z

← Older revision		Revision as of 09:30, 27 February 2019
Line 43:		Line 43:
	* When walking over a ''monster_clip'' brush surface, AI may stray up to around 18 units out of the 'corridor' of ''monster_clip''. It may be that the edge is calculated for the centre of the AI and not its outer width. For this reason you should reduce the horizontal width by around 18 to keep the AI pathfinding away from the edges where appropriate. For example on a bridge without side rails or walls, if an AI is to turn left or right at the end it will likely move over to one side or other of the bridge as it walks across and is likely to have one leg over the edge! By reducing the ''monster_clip'' width you will keep the AI in a corridor down the middle. If there were a side rail or wall of course then that would have its own ''monster_clip'' so that would keep them on the straight and narrow.		* When walking over a ''monster_clip'' brush surface, AI may stray up to around 18 units out of the 'corridor' of ''monster_clip''. It may be that the edge is calculated for the centre of the AI and not its outer width. For this reason you should reduce the horizontal width by around 18 to keep the AI pathfinding away from the edges where appropriate. For example on a bridge without side rails or walls, if an AI is to turn left or right at the end it will likely move over to one side or other of the bridge as it walks across and is likely to have one leg over the edge! By reducing the ''monster_clip'' width you will keep the AI in a corridor down the middle. If there were a side rail or wall of course then that would have its own ''monster_clip'' so that would keep them on the straight and narrow.
	* AI walking over a lone ''monster_clip'' brush that has no entity core will sink into it by about 28 units. This means that if you make an invisible AI-only bridge of ''monster_clip'' then it needs to be 28 units higher than where you want the AI's feet to touch. So a channel with side walls with top surfaces at 100 will need a bridge whose top surface is at 128 in order for the AI to walk smoothly across flush with the side walls. Because 14 to 16 is the maximum step height for an AI you will need a short step of ''monster_clip'' at the entrance and exit for the AI to get on. So this step might be 14 units high but can and should be very shallow - even one unit deep is enough for the AI to pass smoothly on to the main bridge.		* AI walking over a lone ''monster_clip'' brush that has no entity core will sink into it by about 28 units. This means that if you make an invisible AI-only bridge of ''monster_clip'' then it needs to be 28 units higher than where you want the AI's feet to touch. So a channel with side walls with top surfaces at 100 will need a bridge whose top surface is at 128 in order for the AI to walk smoothly across flush with the side walls. Because 14 to 16 is the maximum step height for an AI you will need a short step of ''monster_clip'' at the entrance and exit for the AI to get on. So this step might be 14 units high but can and should be very shallow - even one unit deep is enough for the AI to pass smoothly on to the main bridge.


			==''monster_clip'' : Systematic Method for Adding Pathfinding to Uneven Terrain==

			See [[Systematic Method for Adding Pathfinding to Uneven Terrain]] for an approach to covering larger areas which have irregular surfaces.


	==Preventing and Reducing Pathfinding Complexity in Select Locations==		==Preventing and Reducing Pathfinding Complexity in Select Locations==

Petike: adding category tag

2018-11-21T14:16:16Z

adding category tag

← Older revision		Revision as of 14:16, 21 November 2018
Line 122:		Line 122:
	[[Category:Mapping Tutorials]]		[[Category:Mapping Tutorials]]
	[[Category:AI]]		[[Category:AI]]
			[[Category:AI Tutorials]]

Petike: adding category tag

2018-11-21T13:59:00Z

adding category tag

← Older revision		Revision as of 13:59, 21 November 2018
Line 117:		Line 117:

	If AI need to hit a pathnode exactly, you can add the spawnarg "move_to_position_tolerance" "8" to the path_corner. This means the AI must hit the corner more precisely. You can do the opposite if you don't care whether AI hit the path_corner precisely, and use a large number like 20. This can avoid problems with AI circling to find a specific pathnode.		If AI need to hit a pathnode exactly, you can add the spawnarg "move_to_position_tolerance" "8" to the path_corner. This means the AI must hit the corner more precisely. You can do the opposite if you don't care whether AI hit the path_corner precisely, and use a large number like 20. This can avoid problems with AI circling to find a specific pathnode.



	[[Category:Editing]]		[[Category:Editing]]
	[[Category:Tutorial]]		[[Category:Tutorial]]
			[[Category:Mapping Tutorials]]
			[[Category:AI]]

VanishedOne: /* Problems, Troubleshooting */ I checked the spelling against DR, which doesn't have the typo

2016-03-31T15:58:02Z

Problems, Troubleshooting: I checked the spelling against DR, which doesn't have the typo

← Older revision		Revision as of 15:58, 31 March 2016
Line 116:		Line 116:
	One mapper reported pathfinding broke down due to some monsterclip penetrating a visportal. Split in two either side cured the problem. There is no known reason why monsterclip should affect visportals, but something to check as a last resort. Broken visportals in general have been known to affect pathfinding.		One mapper reported pathfinding broke down due to some monsterclip penetrating a visportal. Split in two either side cured the problem. There is no known reason why monsterclip should affect visportals, but something to check as a last resort. Broken visportals in general have been known to affect pathfinding.

	If AI need to hit a pathnode exactly, you can add the spawnarg "~~move_to_position_tolerence~~" "8" to the path_corner. This means the AI must hit the corner more precisely. You can do the opposite if you don't care whether AI hit the path_corner precisely, and use a large number like 20. This can avoid problems with AI circling to find a specific pathnode.		If AI need to hit a pathnode exactly, you can add the spawnarg "move_to_position_tolerance" "8" to the path_corner. This means the AI must hit the corner more precisely. You can do the opposite if you don't care whether AI hit the path_corner precisely, and use a large number like 20. This can avoid problems with AI circling to find a specific pathnode.

Springheel: /* Problems, Troubleshooting */

2014-02-13T15:30:48Z

Problems, Troubleshooting

← Older revision		Revision as of 15:30, 13 February 2014
Line 115:		Line 115:

	One mapper reported pathfinding broke down due to some monsterclip penetrating a visportal. Split in two either side cured the problem. There is no known reason why monsterclip should affect visportals, but something to check as a last resort. Broken visportals in general have been known to affect pathfinding.		One mapper reported pathfinding broke down due to some monsterclip penetrating a visportal. Split in two either side cured the problem. There is no known reason why monsterclip should affect visportals, but something to check as a last resort. Broken visportals in general have been known to affect pathfinding.

			If AI need to hit a pathnode exactly, you can add the spawnarg "move_to_position_tolerence" "8" to the path_corner. This means the AI must hit the corner more precisely. You can do the opposite if you don't care whether AI hit the path_corner precisely, and use a large number like 20. This can avoid problems with AI circling to find a specific pathnode.



	[[Category:Editing]]		[[Category:Editing]]
	[[Category:Tutorial]]		[[Category:Tutorial]]

Springheel: /* Problems, Troubleshooting */

2014-02-11T20:53:07Z

Problems, Troubleshooting

← Older revision		Revision as of 20:53, 11 February 2014
Line 107:		Line 107:
	==Problems, Troubleshooting==		==Problems, Troubleshooting==

	One mapper reported pathfinding broke down due to some monsterclip penetrating a visportal. Split in two either side cured the problem. There is no known reason why monsterclip should affect visportals, however.

	~~Others have said unsealed non-working visportals or ones crossed by func_statics also might cause pathfinding problems.~~

	If AI are walking on patches and behaving strangely, make sure you have layers of monsterclip or worldspawn underneath the patch.		If AI are walking on patches and behaving strangely, make sure you have layers of monsterclip or worldspawn underneath the patch.
Line 117:		Line 114:
	AI may not properly path to path_corners that are less than 16 units away from worldspawn, including monsterclip.		AI may not properly path to path_corners that are less than 16 units away from worldspawn, including monsterclip.

			One mapper reported pathfinding broke down due to some monsterclip penetrating a visportal. Split in two either side cured the problem. There is no known reason why monsterclip should affect visportals, but something to check as a last resort. Broken visportals in general have been known to affect pathfinding.

	[[Category:Editing]]		[[Category:Editing]]
	[[Category:Tutorial]]		[[Category:Tutorial]]

Springheel at 20:52, 11 February 2014

2014-02-11T20:52:05Z

← Older revision		Revision as of 20:52, 11 February 2014
Line 112:		Line 112:

	If AI are walking on patches and behaving strangely, make sure you have layers of monsterclip or worldspawn underneath the patch.		If AI are walking on patches and behaving strangely, make sure you have layers of monsterclip or worldspawn underneath the patch.

			Another thing to check is whether your path corners are at ground level. If they are too high above the ground or too low into it, AI may refuse to go there.

			AI may not properly path to path_corners that are less than 16 units away from worldspawn, including monsterclip.


	[[Category:Editing]]		[[Category:Editing]]
	[[Category:Tutorial]]		[[Category:Tutorial]]