Stairs not right with Recast Graph scan

Beginner Questions
#1

QQ截图20211018163537
QQ截图202110181635371006×734 375 KB

QQ截图20211018163612
QQ截图20211018163612534×868 47.7 KB

Hello, I’m using Recast Graph and notice that it doesn’t look right with stairs either the models stairs or probuilder stairs. The generated data get beneath the surface of upper floor and stairs near the middle of them. And when agent move near this area they get stuck.

https://drive.google.com/file/d/11fHRgZMcIXXZL1oA_iXiqjWNakomV-Zz/view?usp=sharing
I’ve tried to change the parameters of Recast Graph, set Max Border Edge Length to 0.1, and Max Edge Error to 0. I looks more approximated to the real geometry, but still not matching correctly. And there are too many clustered triangles of the data which I don’t know if it’s a good practice. So what can I do to match the Recast scan result best with stairs geometry?

https://drive.google.com/file/d/1w-PdtEp12DGq4mikBbgCcrbkJeOYa_Hq/view?usp=sharing
As a comparison I use the unity navmesh to bake the result, see the generated mesh data is overlapping the stairs a little, it’s fine as when my AI agents move with CharacterController gravity would let them snap to the surface of stairs geometry.

#2

Hi

The navmesh doesn’t care that much about y coordinates, actually. This is the expected result. The included movement scripts all use physics for positioning themselves on the ground, so if the navmesh is not perfectly accurate along the y-axis, it shouldn’t matter that much.
However, if you add more detail to the scene, the navmesh will get more accurate along the y-axis too since it will add more triangles.

#3

Hi.
You’re right, I just find it nothing with the navmesh. It’s probably about the RVO Controller I use.
I’ve record a short clip about how it appears.
One zombie has RVOController and the other has no.
The one who has RVO will get stuck near the edge, and when RVO disabled it will continue to move.

It collides with everything by default and I set it to Default Agent then it works right
It works good now , but I’m still wondering why the avoidance would get effected by level geometry.

#4

Hi

This might have been fixed in the latest update. You could try that out and see how it goes.

1 Like