Pathfinding Keeps getting stuck on tree and rocks

[Minecrablox]

Hello,

I have been sitting for hours trying to figure out why would my monster keep getting stuck into rocks and trees when there are Pathfinding Modifiers in each of the MeshParts. Here is the part where it get stuck several times:

Here is my AgentParams:

local lurker_agentParams = {
	AgentRadius = 6,
	AgentCanJump = true,
	AgentCanClimb = true,
	Costs = {
		avoid = 10.0,
		collectables = 5.0,
		wall = 10.0
	}
}

All of the Costs are named 100% according to the labels.

For the work of the PathFinding, I use this module:
https://create.roblox.com/marketplace/asset/6744337775/SimplePath-Pathfinding-Module

Any sort of advice would be appreciated. Thank you.

[eatabler0ck (eatablerock)]

Question. What is the RenderFidelity on these mesh parts? That may effect collisions.

[Minecrablox]

So, the RenderFidelity is on Precise. Any idea what that may do?

[eatabler0ck (eatablerock)]

How about CollisionFidelity? What is that set to? If not already, try setting it to PreciseConvexDecompition.

[Minecrablox]

I have tried setting to that setting, but the monster still runs into the rock like a clumsy goat. Are the agent params an issue though?

[eatabler0ck (eatablerock)]

Have you already tried using PathfindingModifiers?

[Minecrablox]

Used those in all of the rocks and tree trunks. Here is a rock one:

The label is wall, which matches the Costs.

[eatabler0ck (eatablerock)]

Interesting, maybe try increasing the cost values?

[Minecrablox]

All modifiers were tested PassThrough on both booleans.

[Minecrablox]

I have once increased to math.huge, then as high as up to 50.0. Anything wrong with them? Because the monster still manages to get stuck going in a loop near a tree.

[eatabler0ck (eatablerock)]

What happens when you set CollisionFidelity to Box? Have you tried it, and if so, what happened?

[Minecrablox]

Still manages to run into the rocks. I do not know if the problem could either be related to the meshes, the params, or the SimplePath module itself. But if you did look at it, is there something thats wacky?

[eatabler0ck (eatablerock)]

In that case, it might be the module that is the issue.

Im sorry, but I have no clue what else it could be.

[eatabler0ck (eatablerock)]

If the monster doesnt have to jump, maybe set the CanJump to false.

Thats the only thing I could think to do.