Jump to content

llGetStaticPath - extra waypoints?


animats
 Share

You are about to reply to a thread that has been inactive for 1836 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

I've been trying out LLGetStaticPath. For a simple path that requires going around one obstacle, I get waypoints like this:

[21:18] Pathfinding tester 2.12: 13 waypoints.
[21:18] Pathfinding tester 2.12: At waypoint <205.58090, 48.88295, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <205.58090, 48.88295, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <204.54800, 47.47806, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <204.18300, 47.26727, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <204.07500, 47.25528, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <204.04240, 47.25165, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <203.98440, 47.24844, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <203.89060, 47.24844, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <203.89060, 47.24844, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <203.72520, 47.24844, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <195.75780, 47.24844, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <195.47040, 47.33411, 35.14844>
[21:18] Pathfinding tester 2.12: At waypoint <195.22380, 47.49541, 35.14844>
[21:18] Pathfinding tester 2.12: At destination.

Only four three waypoints are needed, not 13. In the list returned by the planner, there are several duplicate and some collinear waypoints.

For a straight line path on a flat surface, I get:

[21:24] Pathfinding tester 2.12: 4 waypoints.
[21:24] Pathfinding tester 2.12: At waypoint <192.87290, 49.03352, 35.14844>
[21:24] Pathfinding tester 2.12: At waypoint <192.87290, 49.03352, 35.14844>
[21:24] Pathfinding tester 2.12: At waypoint <192.65000, 46.02066, 35.14844>
[21:24] Pathfinding tester 2.12: At waypoint <192.53060, 44.40686, 35.14844>
[21:24] Pathfinding tester 2.12: At destination.

There should have been two waypoints, the start and the destination.

I wonder if this is the source of some of the "ditzing" in pathfinding. Zero-length segments provide no indication of what direction to face. Anyone else using that LSL call?

  • Like 1
Link to comment
Share on other sites

The first duplicate is from my code, but the others are real. I've been testing in a sandbox.

Path planning is generally pretty good. My overall impression of pathfinding is that it has most of the right stuff, but there are a number of bugs which interact to make it unusuable.

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 1836 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...