rcBuildRegions broken into several steps

[GoogleCodeExporter]

Would it be possible to break rcBuildRegions into several steps that the client 
can call individually? Much like the rest of the Recast build process is broken 
down into bite sized chunks. rcBuildRegions takes a reasonable amount of time 
compared to the other steps (it's still fast! :), and looking at the code it 
seems that it could be broken into several steps. This would enable me to 
abandon the Recast build process for a frame when the allocated build budget 
has expired. I have done this for all the currently available steps.

Thanks,
Neil

Original issue reported on code.google.com by armstron...@gmail.com on 10 Jun 2010 at 11:11

[GoogleCodeExporter]

We discussed the possibility to use the rcBuildRegionsMonotone() for this, 
which has smaller overhead over the rcBuildRegions() (faster, no need to 
calculate distance field). Did you have any success with that?

The monotone region builder works fine with smallish tiles, but it tends to 
generate sliver polys which hurt A* quite badly if you have large tile size.

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

[GoogleCodeExporter]

Neil, is this still an issue?

Original comment by memono...@gmail.com on 29 Oct 2010 at 9:35

[GoogleCodeExporter]

Unfortunately I haven't had chance to test the monotone version - however, I 
run  Recast on a separate thread so it's not such an issue any more. I am happy 
for you to close this Issue...

Original comment by armstron...@gmail.com on 29 Oct 2010 at 9:49

[GoogleCodeExporter]

Ok.

Original comment by memono...@gmail.com on 29 Oct 2010 at 10:00

• Changed state: Done

[GoogleCodeExporter]

Hi, I finally have time to experiment with this.

Just to clarify, if I use rcBuildRegionsMonotone, then rcBuildDistanceField is 
unnecessary?

Original comment by armstron...@gmail.com on 22 Nov 2010 at 11:42

[GoogleCodeExporter]

Correct.

Original comment by memono...@gmail.com on 22 Nov 2010 at 11:54