Difference between revisions of "Pathfinding/Alpha release notes"
Jump to navigation
Jump to search
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. |
Revision as of 22:34, 15 February 2012
Viewer tools are planned for beta release. This Viewer is not currently available.
Restrictions
The initial release of the pathfinding LSL is available only on the Aditi test grid on the following regions:
- List of regions here.
How to report bugs and suggest features
Please use Jira report bugs and suggest features.
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.