Re: Merging of CEL AI branch in CEL trunk

On Thu, Aug 23, 2012 at 4:22 PM, Christian Van Brussel <
[email protected]> wrote:

> On Thu, 2012-08-23 at 11:01 +0100, Sam Devlin wrote:
> > I agree, whilst there are minor differences between the two (one sets
> > two markers the other sets an agent to walk between the two) it does
> > seem redundant to have both. Especially as appsteering also has an
> > example of an agent moving along a path generated by a navmesh. I
> > think appnavmeshtest should be kept for generating navmeshes and
> > testing the construction of paths, for this a marker at both ends
> > would suffice and arguably be clearer than having an agent moving
> > around. Furthermore appnavmeshtest does not (if I remember correctly)
> > use the deprecated behaviours/behaviour layer that apppathfindingtest
> > does.
>
> Another idea would be to finalize the iPreProcess interface (see
> http://crystalspace3d.org/trac/CS/wiki/Tools%20plugins), then put the
> generation tool of the navmesh as a pre-process, and use it from either
> a (generic) command line tool and/or the cseditor/AresEd.
>
> In all cases, appsteering can probably be removed as you mention it.
>

Why does appsteering need to go?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Crystal-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-develop