search

swordlegend / recastnavigation

Automatically exported from code.google.com/p/recastnavigation
zlib License
0 stars 0 forks source link

Erea Annotations #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Allow to specify certain areas using volumes with certain flags when
building navmesh using Recast. These area will be baked into the navmesh
and the flags are available at runtime in Detour which enables to alter the
queries to include/exclude the areas with specific flags.

The initial implementation should include following area painting schemes:
- Extruded polygonal volume based painting (for marking doors, hazards,
spawn areas, etc)
- Walk-height based painting (for stance based painting)

Original issue reported on code.google.com by memono...@gmail.com on 26 Aug 2009 at 12:08

GoogleCodeExporter commented 9 years ago

Original comment by memono...@gmail.com on 4 Sep 2009 at 6:48

GoogleCodeExporter commented 9 years ago 
Certain parts of my navmesh will be water-surface & only certain units can swim.

Would this enhancement allow me to handle that situation? If so, it certainly 
has my 
vote (although I see it's already in progress - good!)

Original comment by seaninaf...@gmail.com on 7 Nov 2009 at 12:48

GoogleCodeExporter commented 9 years ago 
Is there any reason why we wouldn't be able to mark the voxels in the 
rcHeightField
with the flags and have that data retained through the process? I can specify 
much of
the per voxel area information such as crouch, water, etc areas that would save 
the
step of having to manually place regions.

Original comment by jswig...@gmail.com on 8 Feb 2010 at 2:56

GoogleCodeExporter commented 9 years ago 
Short answer no, it is planned feature. Long answer: firstly, I have to test 
how much
extra hit it will be to add some more data to the span structure. Secondly, I 
have to
try and decide what will happen when spans are merged. I try to get the path 
cost out
of the way first.

Original comment by memono...@gmail.com on 8 Feb 2010 at 8:24

GoogleCodeExporter commented 9 years ago 
I did a quick test to add more data to the rcSpan. The impact on performance is 
quite
negligible, but the heighfield data will take about 30% more (8 vs 12 bytes per
span). I will do some tests to see if I can trade off vertical accuracy instead.

Original comment by memono...@gmail.com on 9 Feb 2010 at 5:35

GoogleCodeExporter commented 9 years ago 
Most of the area functionality is in version R125. I separated per triangle and
stance based annotations as separate tasks.

Original comment by memono...@gmail.com on 12 Feb 2010 at 2:47