"Random" bugs/issues when the agent radius is greater than 0

[AnuraDev]

So in general it's more a question what does cause them? where do i need to look in/pay attention etc, i ask cause obviously you have more insight into this. i create the mesh manually (and make sure the edges are connected), is triangle winding important? but as i stated if agent size is zero (so the extra stuff is dropped effectively) it runs well, at least i didn't encounter issues so far. one of the symptomes is what it begins to select non optimal paths but still kind a solves it (but with exceptions), looks like some edges/triangles are rejected even they should be fine.
and yea if it would work "without bugs" would be a really great library as basis, thanks for posting/sharing!

[SandSnip3r]

Are you creating your own triangulation? Or are using the triangle library included?

I think it depends on a certain winding order, but I cannot find a concrete example in the code right now.

Yeah. I agree with you and I apologize. I spent a pretty significant amount of time on this library and never managed to get it to a stable point where it was crash-free. I would have liked to have got it to a point where I was confident that it would not give errors, but I didn't quite get there. I think as long as the radius is smaller than the smallest triangle edge, I am highly confident that it will work. However, when the radius becomes large relative to smaller triangles, pathfinding can fail.

I still occasionally use this library in my MMORPG bot, so I am motivated to fix issues. Maybe if you have a concrete (and ideally minimal reproducer), I could look into it?

[AnuraDev]

yes my own i push data directly into containers which are used by the algorithm. i basically stitch recast navmesh tiles into a single one. connectivity/uniqueness is correct but if winding is important then yes thats the problem.

I think as long as the radius is smaller than the smallest triangle edge, I am highly confident that it will work. However, when the radius becomes large relative to smaller triangles, pathfinding can fail.

yea i thought about similar but often it's not the case for "long" triangles, so tldr you need a more expensive check i guess?

there are many different cases where it can fail i guess.

i can give you my constructor for TriangleLibNavmesh which operates on recast/detour navmeshes (currently for unreal engine) and do it yourself will be simpler/better the main task of my constructor as i stated is to stitch tiles (but it's not optimized etc just made it work)

here is the code it will require a lil bit of cleanup (minor) and should work cause i stripped this lib from most stuff so it would integrate friction free. ahhh i used TArray and similar to have less boilerplate code. but honestly it would be the simplest to test it in unreal cause you can create very complex navmeshes easily (having instant visual feedback) ok i will pack everything. so it's almost drag and drop in C++ unreal project and setuping paths to source. and calling the functions from somewhere. if you need some clarification let me know.

Mesh.zip

i also modified createCircleConsciousLine to have lesser radius check it created issues all the time (due to float/double precision)

for which mmorpg? >u>