No problem, I appreciate you looking into it. Please keep me updated on when this is fixed!
1 Like
Good to see they still update pathfinding, great work.
i can finally make a good ai. This is honestly the best pathfinding feature since pathfinding modifiers
have you tried Increasing the agent radius a little. In the test it is only 1 and the radius that would clear the diagonals is slightly under 1.12
It’s a small difference but could stop them getting caught on edges like this.
on another place, exactly the same script works, it does not work on a map that is surrounded by walls
did i reply to the wrong one? sorry if I did, I was talking about the second video posted where they got stuck approaching it from the side.
The other issue actually appears to be if there is any CanCollide = true part above the truss.
and surrounding walls are just a red herring in that one. Still sure it is not intended behavior though 
when I raised a ladder on my map above the walls, it started to work correctly for me, so it seems to me that this is because of the walls
In your case, is there a roof on the wall?
The known issue is if there is a obstacle(CanCollide=true) above the truss then the agent doesn’t climb the truss.
I tested with the truss surrounded by walls without a roof, it works.
3 Likes
The other issue actually appears to be if there is any CanCollide = true part above the truss.
Right, it’s a known issue. we’re working on it.
2 Likes
yes i have a roof, i hope you fix it soon
1 Like
Does this mean agent radius is fixed? For the longest time pathfinding has completely ignored agent radius and it has flat out not worked, a staff member told me it would be updated in January with some new pathfinding overhauls but you guys seem to be adding new agent params now?
Reference bug post here even mentioning this new post: PathfindingService doesn't always use agent params; makes service unusable for large characters
2 Likes
The agent radius isn’t fixed. We do a obstacle checking on the climbing path base on the agent radius.
@Agent_4004 @sicknoobie This bug “TrussClimbing doesn’t work in enclose space” has been fixed.
2 Likes
Wow cool, now it really works, thank you
1 Like
No more “Clicking, add pathfinding links” Simulator 
, Now we just need
AgentTakeShortestPath Parameter
1 Like
Glad you patched this bug out, it was pretty major. Thanks for working on the issue!
1 Like
I am wondering how we can tell if the waypoint is for climbing or not though. Since there is no PathWaypointAction for Climbing.
2 Likes
@oldmannt If you could make a feature request that adds PathWaypointActions for Climbing, use of Pathfinding Modifier (its label name AND the modifier instance), use of pathfinding link (its label name AND the link instance) that would be super appreciated. (I can’t do it myself for some reason)
Thank you for suggestion.
For now you can check the label for the waypoint, if the the label is “Climb” then this waypoint it’s for truss climbing. Does it work for you?
Ah yes this does appear to work. Labels aren’t super well documented on the API reference (It doesn’t mention the Climb label in PathWaypoint | Roblox Creator Documentation) so I had no idea this existed. I would still like a way for a waypoint to return the instance of the pathfinding modifier or pathfinding link it’s using though.
2 Likes