256x256!!! Anyone trying to path an NPC that far across their game world has serious problems with their game logic! hehehe
I'm really looking forward to being able to throw my implementation out and use the built-in system. Any chance of getting temporary objects working with it too so the navmesh can be dynamically modified.
Have to read the roadmap fatcoder he updated adding dynamic obstacles after adding the last screenshot, and it seems he is done with poly status flags for grass/water etc also.
(This post was last modified: 09-29-2011 06:05 PM by Zervox.)
I haven't tried out the poly status flag stuff in recast, but I assume it can be used to give weight for the agents to follow certain paths over others. For example, if you have a footpath in the game world that goes around a hill. In real life, people are more likely to walk along the footpath to get to their destination rather than just walk up and over the hill, even though the footpath would be longer.
How do you define these poly flags on the terrain for example, and can they be changed dynamically?? For example, if a new footpath appears on the terrain, the agents should give preference to following it, rather than walking across rough ground.
No I believe that is what Recast Convex Volumes are for
status flags from what I know is for settings polys to unwalkable/walkable states without having to rebuild the navmesh.
The problem is that the navmesh is being built from the physical bodies that surround those rocks. Since the physical bodies have a flat top, the navmesh includes that.
I think to solve this problem there needs to be a flag in EE to mark an object as an obstacle, but not walkable. Then EE will need to filter the object's mesh (or physical body in this case) to exclude the flat surfaces that recast would interpert as walkable areas.
This is something that Esenthel would need to implement into EE.
Quote:adding them requires rebuilding path mesh, so it's not intended for adjusting obstacles in every frame, but rather once in a while
I haven't tried this yet, but is there a noticeable pause when it recalculates, or is it done in a background thread or something?
it does by the way have a choice box inside the editor on objects if it is to be included into the navmesh or not, setting it to ignore will not create navmesh ontop of it but will blockout the objects position, eg it will block the area completely and no walkable area on top.
(This post was last modified: 10-03-2011 09:39 AM by Zervox.)
I was able to reproduce the problem in the tutorial. Clicking an inaccessible area causes the agent to get stuck on the rocks.
(10-03-2011 09:36 AM)Zervox Wrote: it does by the way have a choice box inside the editor on objects if it is to be included into the navmesh or not, setting it to ignore will not create navmesh ontop of it but will blockout the objects position, eg it will block the area completely and no walkable area on top.
Ah, I did not know this. I will need to try things out first before commenting.
(10-03-2011 09:21 AM)fatcoder Wrote: I haven't tried this yet, but is there a noticeable pause when it recalculates, or is it done in a background thread or something?
That depends on mesh size and complexity
Sometimes it can be as quick as 0.001s and sometimes as slow as 0.1s
I just tried out the two options for PathMesh that are currently there (Create and Ignore) and they both seem to do the same thing?? Maybe I've done something wrong. See the screen shot below.
he updated adding dynamic obstacles after adding the last screenshot, and it seems he is done with poly status flags for grass/water etc also. 
