Inaccurate A* Pathfinding Scan!

Question

Hi, I've been trying to implement A* pathfinding but it is having trouble in accurately scanning the colliders in my scene. The background should be entirely filled with blue squares but it is not due to some issues with the tile colliders. The pathfinding component is using 2D physics and the diameter for the circles is set to 1. However, it doesn't seem to produce better results if I decrease the number to 0.99 or 0.98. alt text

Below is the image of the platforms and its colliders. They have been set to the ground layer and are the only objects in the scene on the ground layer. I'm at my wit's end with this and would appreciate any and all help!

alt text

Answer 1

Answer by Cratuss96 · Dec 27, 2020 at 02:47 AM

its because of the composite colider. The Composite collider has a verrrrrrryyyyy small offset of (5e-07). Thats why it often messes up float numbers. If you deactivate the composite then it should work fine. btw i love that you use the same tileset "kings and pigs" as i do

1 · Share

Answer 2

Answer by MarshCZA · Mar 04, 2020 at 02:55 PM

As a sanity check have you tried a much smaller diameter, like 0.1?

0 Show 1 · Share

Endogeny · Mar 04, 2020 at 03:07 PM 0

Share

Anything below a diameter of 9.8 just doesn't register any obstacles :( thanks anyways

Answer 3

Answer by Spaceshark123 · Jun 23, 2021 at 01:57 PM

@Endogeny I have had this problem personally with my tilemap and composite collider and the fix for it is to change the composite collider geometry type to polygons and regenerate the A Star navmesh scan.

Hope this helps! ,@Endogeny I have had this problem personally with my tilemap and composite collider and the fix for it is to change the composite collider geometry type to polygons and regenerate the A Star navmesh scan.

Hope this helps!

0 · Share

Inaccurate A* Pathfinding Scan!

3 Replies

Your answer

Update about the future of Unity Answers

Follow this Question

Related Questions