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.
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.
yes i have a roof, i hope you fix it soon
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
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.
Wow cool, now it really works, thank you
No more “Clicking, add pathfinding links” Simulator 
, Now we just need
AgentTakeShortestPath Parameter
Glad you patched this bug out, it was pretty major. Thanks for working on the issue!
I am wondering how we can tell if the waypoint is for climbing or not though. Since there is no PathWaypointAction for Climbing.
@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.
The trusses seem to break the navigation mesh on certain occasions.
Here is the link to the post I’ve made on it:
I can provide the repro in a private message.
This came out literally 8 hours after I completed a 3 week caffeine induced insomnia nightmare bug riddled god mode programming session where I made NPCs climb trusses perfectly.
At this point I had created a monolithic borderline self aware piece of unholy mess that worked for some strange reason.
Needless to say I started crying when I read the news that climbing was now one parameter away from normal path finding… My tears were from a peculiar mix of pure joy and utter resentment. How could Roblox so nonchalantly add a feature like this after all my hard work? But also, thank you, THANK YOU so very much for letting me delete my abominable hornet’s nest of spaghetti madness.
So… I deleted my golem of doom, my totem of curse. Good riddance, I thought, the wake will be a rave party!!!
… only to find out 2 month later that the truss climing flag to pathfinder that Roblox now supplies is a total piece of garbage. When I trace the path out by drawing balls at each path waypoint it looks like a toddler on drugs tried to draw the dots of a dalmation while riding a roller coster. (please see screenshot below).
So now I am scrambling to resurrect my nemeis again, the undying witch of pandora, the whirlwind of fire.
Please dear Roblox, fix this, lest my sanity will be a thing of the past.
This happens on terrain as well where there are random floating waypoints.
Hi,
I’m sorry to hear that you encountered issues, we are working diligently to fix the bug as soon as possible.
In the meantime, could you please sent me a repro for this issue? Then I can figure out the problem easier.
We truly appreciate you bringing this to our attention and your patience while we work to resolve this.
Hi,
Thank you for reporting. Could you send me the repo for the random floating waypoints on terrain? It will be a great help for us to fix the issue.
