Pathfinding/Alpha release notes - Revision history

Rand Linden at 22:34, 2 March 2012

2012-03-02T22:34:37Z

← Older revision		Revision as of 15:34, 2 March 2012
Line 2:		Line 2:
	Welcome to the home page for the open alpha testing for Linden Lab's Pathfinding project! Thank you for your interest in pathfinding and for taking the time to help us test.		Welcome to the home page for the open alpha testing for Linden Lab's Pathfinding project! Thank you for your interest in pathfinding and for taking the time to help us test.

	==~~= Pathfinding testing tips =~~==		== Restrictions ==
			The initial release of the pathfinding LSL is available only on the [[Aditi]] test grid on the following regions:
			* [secondlife://Aditi/secondlife/PathTest1/131/101/23 secondlife://Aditi/secondlife/PathTest1/131/101/23]
			* [secondlife://Aditi/secondlife/PathTest2/100/170/26 secondlife://Aditi/secondlife/PathTest2/100/170/26]
			* [secondlife://Aditi/secondlife/PathTest3/103/127/23 secondlife://Aditi/secondlife/PathTest3/103/127/23]
			* [secondlife://Aditi/secondlife/PathTest4/127/194/29 secondlife://Aditi/secondlife/PathTest4/127/194/29]

	* This project is still in alpha stage and subject to change. We are making the LSL calls public early so we can get feedback and pinpoint as many issues as possible before release. Expect some bugs and instability.

	* We recommend that you remove all HUDs and scripted attachments before entering the pathfinding areas. There are currently several attachment-related bugs.		{{KBcaution\|Remove all HUDs and scripted attachments before entering the pathfinding areas. There are currently several attachment-related bugs.}}

	* Please help us make a better product by filing bugs and ~~feature requests in the PATHBUG JIRA here : https://jira.secondlife.com/browse/PATHBUG~~		== How to report bugs and suggest features ==

	* In order to ~~collect more valuable testing data,~~ the ~~pathfinding enabled regions are currently running a debug server build~~. ~~This will substantially impact server performance~~.		Use JIRA to report bugs and suggest features in the PATHBUG JIRA project: https://jira.secondlife.com/browse/PATHBUG

	* Pathfinding enabled objects will not work (and may cause errors) if taken outside of the pathfinding test regions.		{{KBnote\|Viewer tools are planned for a future Viewer release. }}

	* We have set all objects to be returned after an hour to help maintain a cleaner testing environment for all.		==Testing tips ==

	* Please do not rez more than 10 pathfinding ~~enabled objects at a time, due~~ to the ~~heavy cost of scripts on a debug server build~~. ~~Once~~ pathfinding is released, you can expect to have a reasonably large number of pathfinding objects without impacting server performance (we've tested several hundred pathfinding enabled characters within a region with no noticeable slow down).		The pathfinding project is still in alpha stage and subject to change. We are making the LSL calls public early to get feedback and pinpoint as many issues as possible before release. Expect some bugs and instability.
			The most helpful feedback at this stage are bug reports and specific suggestions regarding the API for the existing pathfinding functions.

	* If you are experiencing significant lag / fps problems, ~~try one of~~ the ~~other 4~~ pathfinding ~~enabled testing regions~~.		Because we want to get these features to Residents as soon as possible, it is not in scope to make major functionality changes before the product release (for example, adding volumetric pathfinding or the ability to pursue multiple avatars at once). That said, we may continue to add more pathfinding features in the future and welcome both near-term and long-term suggestions for improvement.

	* The pathfinding viewer tools will greatly aid in visualizing the nav-mesh and debugging issues with pathfinding enabled characters. We expect to make a project viewer with these tools available within a month.		Also:
			* Be respectful of other residents while testing.
			* Have fun!

	* Because the viewer tools are not yet available, resident testers will not be able to regenerate the region nav-~~mesh for the time being. This means that if you place a staircase in world, for example, characters will view it as an obstacle rather than a pathable object.~~		=== Pathfinding-enabled objects ===

	* The most helpful kinds feedback at this stage are bug reports and ~~specific suggestions regarding~~ the ~~API for the existing~~ pathfinding ~~functions~~.		Pathfinding-enabled objects will not work (and may cause errors) if taken outside of the pathfinding test regions.

	* Because we want to ~~get these features~~ to residents as soon as possible, it is not in scope to make major functionality changes before the product release (eg : adding volumetric pathfinding or the ability to pursue multiple avatars at once). That said, we may continue to add more pathfinding features down the road and welcome both near-term and long-term suggestions for ~~improvement~~.		We have set all objects to be returned after an hour to help maintain a cleaner testing environment for all.

	* Be respectful of ~~other residents while testing~~.		Please do not rez more than 10 pathfinding enabled objects at a time, due to the heavy cost of scripts on a debug server build. Once pathfinding is released, you can expect to have a reasonably large number of pathfinding objects without impacting server performance (we've tested several hundred pathfinding enabled characters within a region with no noticeable slow down).

	* Have fun!

	~~== Restrictions ==~~
	~~The initial release of the~~ pathfinding ~~LSL~~ is ~~available only on the [[Aditi]] test grid on the following regions:~~
	* [secondlife://Aditi/secondlife/PathTest1/131/101/23 secondlife://Aditi/secondlife/PathTest1/131/101/23]
	* [secondlife://Aditi/secondlife/PathTest2/100/170/26 secondlife://Aditi/secondlife/PathTest2/100/170/26]
	* [secondlife://Aditi/secondlife/PathTest3/103/127/23 secondlife://Aditi/secondlife/PathTest3/103/127/23]
	* [secondlife://Aditi/secondlife/PathTest4/127/194/29 secondlife://Aditi/secondlife/PathTest4/127/194/29]

	~~== How~~ to ~~report bugs and suggest features ==~~

	~~{{KBnote\|Viewer tools~~ are ~~planned for beta release~~. This ~~Viewer is not currently available~~.}}		=== Performance ===
			To collect more valuable testing data, the pathfinding-enabled regions are running a debug server build. This will substantially impact server performance.
			If you experience significant lag / FPS problems, try a different pathfinding test regions.

	~~Please use Jira to report bugs~~ and ~~suggest features~~.		=== Viewer tools ===
			The [[Pathfinding Tools in the Second Life Viewer\|Viewer pathfinding tools]] will greatly aid in visualizing the nav-mesh and debugging issues with pathfinding-enabled characters. A project viewer with these tools will be available soon.

	~~{{Comment\|TBD~~.}}		Because the Viewer tools are not yet available, Resident testers will not be able to regenerate the region nav-mesh for the time being. This means that if you place a staircase in world, for example, characters will view it as an obstacle rather than a pathable object.

Rand Linden at 22:24, 2 March 2012

2012-03-02T22:24:42Z

@@ Line 1: / Line 1: @@
 {{Pathfinding Nav}}
-Viewer tools are planned for beta release.  This Viewer is not currently available.
+Welcome to the home page for the open alpha testing for Linden Lab's Pathfinding project!  Thank you for your interest in pathfinding and for taking the time to help us test.
 == Restrictions ==
@@ Line 10: / Line 40: @@
 == How to report bugs and suggest features ==
 Please use Jira to report bugs and suggest features.
 {{Comment|TBD.}}

Rand Linden at 19:44, 2 March 2012

2012-03-02T19:44:50Z

← Older revision		Revision as of 12:44, 2 March 2012
Line 1:		Line 1:
	{{Pathfinding ~~alpha~~}}		{{Pathfinding Nav}}
	Viewer tools are planned for beta release. This Viewer is not currently available.		Viewer tools are planned for beta release. This Viewer is not currently available.

Jeremy Linden at 16:56, 16 February 2012

2012-02-16T16:56:10Z

← Older revision		Revision as of 09:56, 16 February 2012
Line 1:		Line 1:
			{{Pathfinding alpha}}
	Viewer tools are planned for beta release. This Viewer is not currently available.		Viewer tools are planned for beta release. This Viewer is not currently available.

	== Restrictions ==		== Restrictions ==
	The initial release of the pathfinding LSL is available only on the [[Aditi]] test grid on the following regions:		The initial release of the pathfinding LSL is available only on the [[Aditi]] test grid on the following regions:
	* ~~{{Comment\|List of regions here.}}~~		* [secondlife://Aditi/secondlife/PathTest1/131/101/23 secondlife://Aditi/secondlife/PathTest1/131/101/23]
			* [secondlife://Aditi/secondlife/PathTest2/100/170/26 secondlife://Aditi/secondlife/PathTest2/100/170/26]
			* [secondlife://Aditi/secondlife/PathTest3/103/127/23 secondlife://Aditi/secondlife/PathTest3/103/127/23]
			* [secondlife://Aditi/secondlife/PathTest4/127/194/29 secondlife://Aditi/secondlife/PathTest4/127/194/29]

	== How to report bugs and suggest features ==		== How to report bugs and suggest features ==

	Please use Jira report bugs and suggest features.		Please use Jira to report bugs and suggest features.

	{{Comment\|TBD.}}		{{Comment\|TBD.}}

Falcon Linden: /* Known issues */

2012-02-16T07:32:41Z

Known issues

← Older revision		Revision as of 00:32, 16 February 2012
Line 10:		Line 10:

	{{Comment\|TBD.}}		{{Comment\|TBD.}}

	~~== Known issues ==~~

	* llExecCharacterCmd(CHARACTER_JUMP_CMD, [height]) only compiles in mono
	* Replacing an existing script doesn't stop behaviour, in the same way as particles and hover text, use [[llExecPathingCmd]](PATH_CMD_STOP, [])
	* Occasionally a script fails with no explanation - no path related elements work but pathing silently fails. Putting the same script contents in another prim works perfectly.
	* Getting occasional “database content cannot be loaded” error when reopening an existing script.



	~~[[Category:Pathfinding]]~~

0mphalos Resident: /* Known issues */

2012-02-16T06:34:25Z

Known issues

← Older revision		Revision as of 23:34, 15 February 2012
Line 13:		Line 13:
	== Known issues ==		== Known issues ==

	*		* llExecCharacterCmd(CHARACTER_JUMP_CMD, [height]) only compiles in mono
	*
	*
	*
	*
	* Replacing an existing script doesn't stop behaviour, in the same way as particles and hover text, use [[llExecPathingCmd]](PATH_CMD_STOP, [])		* Replacing an existing script doesn't stop behaviour, in the same way as particles and hover text, use [[llExecPathingCmd]](PATH_CMD_STOP, [])
	* Occasionally a script fails with no explanation - no path related elements work but pathing silently fails. Putting the same script contents in another prim works perfectly.		* Occasionally a script fails with no explanation - no path related elements work but pathing silently fails. Putting the same script contents in another prim works perfectly.

0mphalos Resident: /* Known issues */

2012-02-16T06:23:08Z

Known issues

← Older revision		Revision as of 23:23, 15 February 2012
Line 13:		Line 13:
	== Known issues ==		== Known issues ==

	* ~~Phantom Prims are seen as barriers.~~		*
	* ~~Water is seen as a barrier/borked.~~		*
	* ~~Saving scripts sometimes doesn't work - post save the character is frozen. Picking up the object with script running and rezzing makes the character activate.~~		*
	* Can't set an offset to the vertical height that the object hovers at, or make it lower so that it appears to hug the ground, or move through the ground. In other works pathing is only script modifiable in X and Y coordinates, not Z, but pathing functions in all three coordinates, albeit with Z hugging the terrain or objects it is passing over.		*
	* ~~When creating a fleeing script, has to be set to flee one AV at a time, ideally needs to be possible to flee everyone.~~		*
	* Replacing an existing script doesn't stop behaviour, in the same way as particles and hover text, use [[llExecPathingCmd]](PATH_CMD_STOP, [])		* Replacing an existing script doesn't stop behaviour, in the same way as particles and hover text, use [[llExecPathingCmd]](PATH_CMD_STOP, [])
	* Occasionally a script fails with no explanation - no path related elements work but pathing silently fails. Putting the same script contents in another prim works perfectly.		* Occasionally a script fails with no explanation - no path related elements work but pathing silently fails. Putting the same script contents in another prim works perfectly.
	* Getting occasional “database content cannot be loaded” error when reopening an existing script.		* Getting occasional “database content cannot be loaded” error when reopening an existing script.
	** Need a reproducible case. Server logs seem to indicate something about full parcels which lead to objects going deeply underground.
	* If a targeted agent flies the agent becomes invisible to path script.
	** This doesn't seem to be always valid: I can be flying near the ground and still be followed. If I fly out of the vertical bounds of the path volume it then loses me.


	[[Category:Pathfinding]]		[[Category:Pathfinding]]

Rand Linden: /* How to report bugs and suggest features */

2012-02-14T22:38:06Z

How to report bugs and suggest features

← Older revision		Revision as of 15:38, 14 February 2012
Line 6:		Line 6:

	== How to report bugs and suggest features ==		== How to report bugs and suggest features ==

			Please use Jira report bugs and suggest features.

	{{Comment\|TBD.}}		{{Comment\|TBD.}}

Rand Linden: /* How to report bugs */

2012-02-14T22:37:39Z

How to report bugs

← Older revision		Revision as of 15:37, 14 February 2012
Line 5:		Line 5:
	* {{Comment\|List of regions here.}}		* {{Comment\|List of regions here.}}

	== How to report bugs ==		== How to report bugs and suggest features ==

	{{Comment\|TBD.}}		{{Comment\|TBD.}}

Rand Linden at 22:37, 14 February 2012

2012-02-14T22:37:29Z

← Older revision		Revision as of 15:37, 14 February 2012
Line 1:		Line 1:
	~~== Requirements ==~~		Viewer tools are planned for beta release. This Viewer is not currently available.

	== Restrictions ==		== Restrictions ==
Line 7:		Line 7:
	== How to report bugs ==		== How to report bugs ==

	TBD.		{{Comment\|TBD.}}

	== Known issues ==		== Known issues ==