GSoC Smarter pathfinder - Revision history

Abma at 19:23, 7 March 2012

2012-03-07T19:23:50Z

← Older revision		Revision as of 20:23, 7 March 2012
Line 1:		Line 1:
			{{deprecated\|deprecated: kloot is already working on this}}

	= GSoC idea: Smarter pathfinder =		= GSoC idea: Smarter pathfinder =

Abma: /* Possible Mentor(s) */

2012-03-02T17:54:20Z

Possible Mentor(s)

← Older revision		Revision as of 18:54, 2 March 2012
Line 25:		Line 25:
	* Navigation mesh could be introduced for better paths and faster searches - at the cost of generating the mesh and updating it online due to terrain modification		* Navigation mesh could be introduced for better paths and faster searches - at the cost of generating the mesh and updating it online due to terrain modification

	~~== Possible Mentor(s) ==~~		[[Category:GSoC]]

	~~{{GSoC2010_bottom}}~~

Koshi: backlink and category via template

2010-03-13T17:19:48Z

backlink and category via template

← Older revision		Revision as of 18:19, 13 March 2010
Line 27:		Line 27:
	== Possible Mentor(s) ==		== Possible Mentor(s) ==

	~~[[Google_Summer_of_Code_2010]]~~		{{GSoC2010_bottom}}

Tobi: Protected "GSoC Smarter pathfinder": protecting during application period [edit=sysop:move=sysop] (expires 22:00, 10 April 2010 (UTC))

2010-03-12T16:05:27Z

Protected "GSoC Smarter pathfinder": protecting during application period [edit=sysop:move=sysop] (expires 22:00, 10 April 2010 (UTC))

← Older revision	Revision as of 17:05, 12 March 2010
(No difference)

Koshi: /* Possible Mentor(s) */

2010-03-12T15:50:13Z

Possible Mentor(s)

← Older revision		Revision as of 16:50, 12 March 2010
Line 26:		Line 26:

	== Possible Mentor(s) ==		== Possible Mentor(s) ==

	~~[http://www.example.com FORUMLINK]~~

	[[Google_Summer_of_Code_2010]]		[[Google_Summer_of_Code_2010]]

Brain damage at 15:17, 12 March 2010

2010-03-12T15:17:02Z

← Older revision		Revision as of 16:17, 12 March 2010
Line 4:		Line 4:
	Current pathfinder is rather inflexible and inefficient.		Current pathfinder is rather inflexible and inefficient.

	== ~~Background~~ ==		== What ==
	Spring's pathfinder uses a 2d grid and is somewhat limited in functionality. A partial/full rewrite should be introduced to add support for navigating using more than 8 primary directions and selectively ignore certain unit types for performance reasons.		Spring's pathfinder uses a 2d grid and is somewhat limited in functionality. A partial/full rewrite should be introduced to add support for navigating using more than 8 primary directions and selectively ignore certain unit types for performance reasons.

Line 18:		Line 18:
	== Difficulty ==		== Difficulty ==
	Estimated: hard		Estimated: hard

			== Technical details ==

	The pathfinder is one of the better encapsulated subsystems in spring; generally, there will only be minor changes required in the rest of the engine, if any. There's a lot of algorithmic work to do under the hood, though:		The pathfinder is one of the better encapsulated subsystems in spring; generally, there will only be minor changes required in the rest of the engine, if any. There's a lot of algorithmic work to do under the hood, though:

Brain damage: standardizing requirements format

2010-03-12T15:06:09Z

standardizing requirements format

← Older revision		Revision as of 16:06, 12 March 2010
Line 12:		Line 12:

	== Required skills ==		== Required skills ==
	* ~~knowledge~~ of graphs and pathfinding (particularly navigation graphs)		* Knowledge of graphs and pathfinding (particularly navigation graphs)
	* C++ ~~and~~ Lua/C ~~api~~		* Knowledge of C++
			* Knowledge of Lua API/C bindings

	== Difficulty ==		== Difficulty ==

Imbaczek at 21:49, 11 March 2010

2010-03-11T21:49:16Z

← Older revision		Revision as of 22:49, 11 March 2010
Line 17:		Line 17:
	== Difficulty ==		== Difficulty ==
	Estimated: hard		Estimated: hard

			The pathfinder is one of the better encapsulated subsystems in spring; generally, there will only be minor changes required in the rest of the engine, if any. There's a lot of algorithmic work to do under the hood, though:
			* Cooperative pathfinding exists in a very scant form and could be greatly improved
			* Navigation mesh could be introduced for better paths and faster searches - at the cost of generating the mesh and updating it online due to terrain modification

	== Possible Mentor(s) ==		== Possible Mentor(s) ==

Brain damage: New page: = GSoC idea: Smarter pathfinder = == Why == Current pathfinder is rather inflexible and inefficient. == Background == Spring's pathfinder uses a 2d grid and is somewhat limited in functi...

2010-03-11T21:25:12Z

New page: = GSoC idea: Smarter pathfinder = == Why == Current pathfinder is rather inflexible and inefficient. == Background == Spring's pathfinder uses a 2d grid and is somewhat limited in functi...

New page

= GSoC idea: Smarter pathfinder =

== Why ==
Current pathfinder is rather inflexible and inefficient.

== Background ==
Spring's pathfinder uses a 2d grid and is somewhat limited in functionality. A partial/full rewrite should be introduced to add support for navigating using more than 8 primary directions and selectively ignore certain unit types for performance reasons.

Spring's Lua API should be extended to allow game developers to push new nodes/links and be able to alter or delete existing ones. (for pathfinder-aware tunnels/teleporting/etc.)

Preferably this all should also be faster then the current system, or a compelling argument/experiment should be made that shows there can not be a faster system with the same features.

== Required skills ==
* knowledge of graphs and pathfinding (particularly navigation graphs)
* C++ and Lua/C api

== Difficulty ==
Estimated: hard

== Possible Mentor(s) ==

[http://www.example.com FORUMLINK]

[[Google_Summer_of_Code_2010]]