Pathfinding now supports Climbable Trusses

[Nekoparaiten (Ajax)]

The trusses seem to break the navigation mesh on certain occasions.
Here is the link to the post I’ve made on it:

Broken Navigation Mesh

In one of my maps for my game, I’ve noticed that the AI zombies tend to not be able to pathfind to the top through the ladders. Here’s an image of it: [image] I went ahead to investigate by turning on the visuals on the navigation mesh, and here is the issue: [image] [image] The navigation mesh here is flat out wrong and broken, which caused that area to be untraversable. The only fix to this is deleting mandatory parts to the point that area is virtually broken just for the AI to be able…

I can provide the repro in a private message.

[vevstolen]

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.

[SubtotalAnt8185]

@vevstolen

image683×594 207 KB

This happens on terrain as well where there are random floating waypoints.

[oldmannt]

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.

[oldmannt]

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.

[SubtotalAnt8185]

There isn’t really a repro place for this since it happens randomly and abnormally. However, the last time I checked the problem was much worse and you just get waypoints that are a few studs higher than where they should be:

Also, while experimenting with this I did find an issue with pathfinding. If the target is slightly below the navigation mesh, the waypoints will position to the lower point instead of rounding to the upper point:
robloxapp-20230110-2002145.wmv (3.1 MB)

Here is the place I was using for tests:
pathfindingRepro.rbxl (440.5 KB)

[sicknoobie (Marioman73)]

Just found out NPCs don’t appear to use trusses to climb down, resulting in them climbing to places where they get stuck (since pathfinding service avoids falling off cliffs). Hoping this functionality gets added soon.

ALSO there’s a major problem with the navmesh in enclosed spaces with truss parts as seen here:

Edit: It isn’t just that watch tower either, it can be recreated kinda easily:

[Guest_503642 (Guest)]

This is also happening to me too. They seem to work effectively and fine, But it’s kinda annoying at times.

[vevstolen]

Hi! I am not sure what “repro” means?

[052008cooljp (IAmCoolJP)]

I am pretty sure a repro is a roblox place file. They usually need these in specific cases when they can’t reproduce an issue by themselves I think.

[oldmannt]

yes, thank you for explaining.

[Guest_503642 (Guest)]

Also, Since pathfinding is getting better, Would it be better if roblox can let us add our own navigation mesh for pathfinding, Would make it easier without adding pathfinding modifiers.

[Lucatacos2213 (Lucatacos)]

They are a memory leak in PathFinding
Devforum post: PathFinding service leaks memory until it crashes the server
I’m reporting here in case

[cloakedyoshi]

OH! Someone else with this issue! The changes to trusses broke one of my pre-existing structures and navmeshes.

I filed a bug report with a repro model here:

Pathfinding changes to trusses made my previously-fine navigation mesh nonsensical

Reproduction Steps Load the attached .rbxm (included in the private message) into an empty place, ensure that there is no baseplate below the structure Enable “Show Navigation Mesh” in Studio Settings Observe that the navigation mesh of the facility’s floor makes no sense, NPCs will not properly path in this building Delete or move the truss beams that are above the roof Observe that the navigation mesh is corrected, NPCs now path as intended [image] The nonsensical navigation mesh [image] …

[sicknoobie (Marioman73)]

Oh my gosh thank you for making a bug report for this! I can barely figure it out and when I do I usually don’t get a response from the bug report team.

[oldmannt]

We release a fix for this issue, could you double check if it works?
If it doesn’t work would you mind pm me a rbxl file that can reproduce the issue.

[oldmannt]

This broken navigation mesh issue has been fixed.

[oldmannt]

Hi, could you double check if this issue fixed.

[Guest_503642 (Guest)]

It’s indeed fixed now! No issues anymore.