I use the module “Simple Path” that utilizes the pathfinding service. The problem being is that each time the service is called and computed with, the game freezes and a couple of seconds later, crashes the studio. Memory cannot be read due to the crash and my PC’s memory does not rise. This issue only happens in my place that I am currently working on, but is not public.
A private message is associated with this bug report
I see you included a private message as well. Not sure if its related but I also experience studio crashing with usage of path finding service; Play solo crashes on PathfindingService usage
You should use the ROBLOX pathfinding here: Character Pathfinding | Documentation - Roblox Creator Hub
The engineers dont take feedback from user made modules. So please use the Engine version
Not really. The code could be running too fast. or its on endless loop
The OP said his game freezes so that most be because of infinite loop or the script timeout
I just tested the pathfinding, it works and its not crashing.
Pathfinding has issues on other things like not computing path properly and making npcs agents on wall corners but i didnt get any crash
That
thats why i told him to use the roblox pathfinding script from the API and not a plugin from a player
Ok, but that is a workaround. That doesn’t invalidate my point, this is still a bug with the Engine, however obscure. Your Navigation Mesh bug is obscure as well, I don’t think anyone has reported it or found out about it before you, but would you still not want it fixed, because it affects you?
My bug is a bug that is within the engine because of nav generation issue and its something i have no control on, not a code issue.
The OP probably did a code issue or the plugin author did a code issue that causes it to crash. its not within the engine as my pathfinding script not crashing at all at strongest it stops working but crash never happen to me.
If OP copy pastes the official ROBLOX tutorial pathfinding code on an empty baseplate and the path crashes or/and getting hit by walls/ not moving etc then that would worth a bug report.
Right, but the issue still would have occurred even if SimplePath was used to (at some point) call Path:ComputeAsync, because that’s all SimplePath does. Make it easier to use PathfindingService. It uses PathfindingService.
My point is, at the end of the day, this is still a bug with the Engine, regardless of how it was triggered. The Engine should never crash, period. No exceptions. A bug is a bug.
SimplePath is a plugin, we dont know how the developer author coded it, he might have added loops, other conditions or probably infinite call on waypoints. if its a plugin that is not entirely made by roblox, that most likely uses old and deprecated code. But ok, do as what suits you well
I’ve read the code. It is not a plugin. It is a module. It uses PathfindingService. It is open-source. It does not use an infinite loop.
The private message is just the file to my place so the staff can reproduce the crash.