Hi there just a quick troubleshooting question; there were a lot of changes recently, and 5.2.2 explicitly needs to be re-installed with the old versions fully removed. Give that a try? And if you have already/did before upgrading, let us know and I’ll see what can be found on this
In the editor, I typically get around 15-30 errors at once, but there don’t seem to be any visible issues in the game—it appears to be working fine. The errors are thrown by the NPCs, but I haven’t been able to find the root cause. I even made a pointless video…
It’s most likely happening when dynamic obstacles are being moved/added/removed.
If you can reliably replicate it, I would be very interested in a test project so that I can replicate it too.
Investigating the problem: it occurs when I destroy objects (like vases, for example) and call UpdateGraphs to update the area under the object as walkable again.
var guo = new GraphUpdateObject(bounds);
AstarPath.active.UpdateGraphs(guo, 1);
If, after calling UpdateGraphs, I kill some NPCs, the error might happen.
If I don’t call UpdateGraphs (I comment it out), I can destroy as many enemies as I want without errors. Does this help? Because creating an example is not easy.
Found the issue! Some time ago, I tried using Dynamic Obstacles and enabled “Use Navmesh as Obstacles” in the RVO Simulator.
I’m no longer using Dynamic Obstacles, but that setting was still active. It seems that in version 5.2, this flag is causing the bug, even though I don’t have any Dynamic Obstacles anymore.
I have same error too.
It happens when my character tries to build structures.
I haven’t used any Dynamic Obstacles but it shows same error.
I’m using 5.2.3
Thank you for reply.
I really hope it works.
The error seems to occur irregularly and sometimes during gameplay after building the game.
It seems to happen especially during the first playthrough.
Follower Entity with Raycast Graph.
I think it works by unchecking “Use Navmesh as Obstacles”.
But it makes the monsters jitter when they are close together.
If you have a way to replicate the error, I would very much appreciate a test project that shows the issue.
I have not been able to replicate this in my own project.