Improving Pathfinding Quality With New Algorithm

[M_etrics]

send the navmap by turning on debug visualization

[sicknoobie (Marioman73)]

How much longer is the wait until these changes can be used in-game? Would love to test them out in actual live-servers ASAP.

[ColRealPro (Kohl)]

Do you think it will be released by next week maybe? My player bots for tropical royale need this to be able to get out of trapped areas with partial paths, would be nice to have that available to them soon.

[CharSiewGuy (Char)]

Dear @watIsInTheName, this improvement is truly monumental and I would love to see it live in roblox client soon, I am using it here

[Feonixid]

I think one month is a reasonable time to release the update and fix any bugs on an update of this size.

[watIsInTheName]

Please check this thread here . You are facing similar issue.

Pathfinding computes too small of a radius around points

Hi @VoidedBlades , Just to put the summary of what is happening here Pathfinding service restrict the search to certain extent for performance reasons. In this case the only path is to go through the cliff on the left side but since it is beyond the extend of search we dont generate the path. One option to get a path in this case to call findPath on a point to the left so that we generate navmesh and then again call the findPath with the actual start and end. This make sure pathfinding has t…

[watIsInTheName]

This should not be related to new improvements. Based on the error you are getting, it seems in your map you have more than 61 modifiers in the a grid (64 X 64) . Did you make any updates to your game recently. if you could provide a repo case we can help investigate the root cause.

[SummerEquinox]

Has this been re-enabled for all platforms? Noticed my NPCs doing very well today. Thanks for any updates you can provide

[watIsInTheName]

This is still enabled in studio only. We are working to re-enable it for all platforms soon.

[128Cores (Kellie)]

Great! This is a long-awaited and much-needed update.

I also have some feature requests that I think would be great in the future.

• AgentJumpHeight: Taking the custom Humanoid JumpHeight into account instead of default.
• Improved ability to climb TrussPart and other climbable objects.
• Ability to disable NavMesh from generating for objects.
• Etc…

Right now I’m still having problems with pathfinding unable to properly climb TrussParts or climbable objects which I had a workaround of manually overwriting it with my own custom path which is not very ideal.
My NPC has the JumpHeight of 7.2 (70 in JumpPower) there are a lot of areas that the NPC can navigate to but wouldn’t which is a bit weird, to say the least.

Other than that, I think this update is amazing I thought that they might have forgotten about pathfinding by now but I was pleasantly surprised by this post since I’ve been working a lot with NPCs and pathfinding since I started developing on this platform and there wasn’t a lot of needed improvement and fixes done for it.