I get a lot of these errors too, although I hadn’t realised it was related to the proximity of the nav edge. Here’s an example of mine (using AIPathAlignedToSurface):
ArgumentOutOfRangeException: Argument is out of range.
Parameter name: index
System.Collections.Generic.List`1[System.Int32].get_Item (Int32 index) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Collections.Generic/List.cs:633)
Pathfinding.AIPathAlignedToSurface.InterpolateNormal (RaycastHit hit) (at Assets/AstarPathfindingProject/Behaviors/AIPathAlignedToSurface.cs:48)
Pathfinding.AIPathAlignedToSurface.UpdateMovementPlane () (at Assets/AstarPathfindingProject/Behaviors/AIPathAlignedToSurface.cs:64)
Pathfinding.AIPathAlignedToSurface.Update () (at Assets/AstarPathfindingProject/Behaviors/AIPathAlignedToSurface.cs:14)
Interesting. I haven’t been able to replicate either of those errors. Would it be possible for you to share a test scene with me in which it is possible to replicate it easily?
Today I find out that one of the errors is related to the RVO system and the other to the “Funnel Simplification” option in the “Rich AI” script.
I hope this information might be useful.
I made a simple test scene to show the exceptions. I have not yet heard from Aron about this, not even whether he could reproduce the exceptions. I’d appreciate someone else on this thread trying my test and confirming that they too also see the exceptions (it happens when the player object warps from the cave to the surface in scene1).
Do you have an example scene I could try out @Toto. I haven’t been able to replicate that exception.
I have managed to fix the exception that @Snouto talks about, but it is unfortunately completely unrelated.
Sorry for the bump, but I’ve encountered the issue in 4.2.2 and did a bit of debugging.
Apparently the villain is RichPath.cs:337 (in this version), where the penalty is calculated. result[result.Count-1] != nodes[mn] throws the exception because result is empty.
It seems to occur semi-randomly in my scene, but always when startPoint and endPoint of SimplifyPath were close to each other (i.e. Vector3.Distance(startPoint, endPoint): 9.440894E-06). The location happens to be close to the edge of the graph, although I am not certain if that’s any indicator. It doesn’t seem to matter what path I am using; in the example I was trying to move from (-7.2, 0.1, 2.0) to (-7.3, 0.0, 6.0). I believe it always occurs at the end of the path, after the agent has reached the destination.
For example, this is the place of the agent when the exception was thrown. The distance between the destination and the agent was (0, 0.05, 0); for some reason the agent is floating that much above the ground and I’m not quite sure why.
I’ve added a log line to dump the important-ish values:
There’s just one RVO controller in the scene right now, along with a recast graph and some navmesh cuts (the square in the picture is one of those). I’m not sure if I can isolate this scene I have here into a simple test case, but maybe those hints can help?
Heya, just adding to the pile that I’ve also been encountering this issue! I can see about making a test scene if it’d help with isolating the issue. To add onto MisterBawks notes on the issue, I added a try/catch and it seems to trigger it when accessing the List parameter at the end of the function with the list access of “result[result.Count-1]”. No clue how that would be out of range at least from just looking at the function itself, maybe something with the multithreading?
Also at least for me turning off multithreading seems to have solved it? So most likely that list is having elements removed in another thread which is causing the exception.
