PureBasic Forums - English

Posted: **Tue Aug 19, 2025 10:22 pm**

Hello,

this looks impressive, good job!

I believe the point is stuck because it lands on the line itself and there is a collision 360° no matter in which direction you "shoot". I'd try to keep the "dot" at a minimum distance from the collider lines (dot radius + 0.00000000001). I haven't looked through the entire code, I may not understand it either but I believe this could be the issue.

Posted: **Wed Aug 20, 2025 6:00 am**

thyphoon wrote: Sat Aug 16, 2025 6:03 pm Thans yes ... Not easy ... but i search how to correct it

For a better debuging maybe it is usefull you can add the start-/end points as variables (not mousepointer position).

Posted: **Wed Aug 20, 2025 8:56 am**

benubi wrote: Tue Aug 19, 2025 10:22 pm Hello,

this looks impressive, good job!

I believe the point is stuck because it lands on the line itself and there is a collision 360° no matter in which direction you "shoot". I'd try to keep the "dot" at a minimum distance from the collider lines (dot radius + 0.00000000001). I haven't looked through the entire code, I may not understand it either but I believe this could be the issue.

Yes, I agree with your analysis. As soon as I have a little time, I'll dive back into it to try to resolve this last point.

IceSoft wrote: Wed Aug 20, 2025 6:00 am For a better debuging maybe it is usefull you can add the start-/end points as variables (not mousepointer position).

Yes, I simplified my code a bit to put it here. Because I have somewhat large logs that allow me to analyze each step of the path search.

PureBasic Forums - English

Point'n Click 2D pathFinding

Re: Point'n Click 2D pathFinding

Re: Point'n Click 2D pathFinding

Re: Point'n Click 2D pathFinding