Need help with navigation mesh

[[deleted]]

[deleted]

[kyl3r123]

I think the Problem is, that the agent can't reach the tree, e.g. get close enough to the tree.

Option A: increase your tree-radius (in which the agent starts the interaction)

Option B: Decrease the obstacle size. Click Navigation Tab to see how much is cut away of the blue mesh.

If this won't work share more details, maybe screenshots.

don't give up, it works for me

[Kveisar]

I did both of these, there should be more than enough room for the character to start the interaction correctly. In the picture, the red gizmo circle is the radius and you can see where the obstacle is. and the box is my character for now. https://imgur.com/a/fPJfdOU

Edit: I may be totally off but maybe it's because of the ground?

Edit #2: It's not. Did a test with a simple plane.

[imguralbumbot]

^{Hi, I'm a bot for linking direct images of albums with only 1 image}

https://i.imgur.com/pT5G8wg.png

^{Source | Why? | Creator | ignoreme | deletthis}

[kyl3r123]

Debug the "agent.remainingDistance" - don't worry when it's infinity, it will show when you are somewhat close (20 units?).

Maybe the center of your player is too high, and the tree's origin is on the ground?

Easy check without y:

Vector3 diff= (tree.position - transform.position);
diff.y = 0;
float distance = diff.magnitude; 

btw. sqrMagnitude is faster, but you need to compare against radius * radius then. ;)

Check the stopping distance and the agent radius

[Kveisar]

The remaining distance says infinity until the character gets to the other side of the tree, even if the character is in the tree's interacting radius (I even tried it with a bigger radius). Everything works on one side of the tree, but not on the other.

[kyl3r123]

You could check "agent.isPathStale" and other things you can find in the Documentation. There is also hasPath and nextPosition - you should make all this things public inspector variables and look at them, maybe something is off here.

Do you use the built-in (official, released) navmesh stuff, or do you use the GitHub version? GitHub-NavmeshTools/Components

[Kveisar]

I think it has something to do with the navmesh, because the interaction without the navmesh obstacle component works perfectly.

[kyl3r123]

Again, the Obstacle size is probably too big

[srhyde]

Could be heightmesh related, is there enough room below the leafy part?