Lim
May 22, 2024, 5:18pm
1
Hello. I’m using 5.1.1. RichAI + RecastGraph
Is there a reason to fix the y position to 0 when doing FindWalls?
Because of this, errors occur when measuring distances, making the Wall Dist value useless.
Thank you.
void FindWalls (int nodeIndex, List<Vector3> wallBuffer, Vector3 position, float range) {
if (range <= 0) return;
bool negAbort = false;
bool posAbort = false;
range *= range;
position.y = 0;
Hi
That does indeed seem very sketchy.
I have fixed it locally now, and the fix will be included in the next update.
However, for the most part the FollowerEntity component is now recommended instead of the RichAI component. Try it out. It’s more robust in many ways.
1 Like
Lim
May 29, 2024, 5:33pm
3
Thank you for the answer.
I am hesitant to use FollowEntity because of this issue.
Hi, I’m using version 5.1.1.
Unlike RichAI, FollowerEntity does not properly follow the penalty in RecastGraph.
The blue area has a penalty of 0, while the rest of the area has a penalty of 10000.
I created a road mesh separately and tagged it with RecastMeshObj.
Why FollowerEntity does not move along the road?
[fe.case]
[rich.case]
I would appreciate it if you could review it.
1 Like