Re: Integrating PcSteer and Recast&Detour

Hello Again All,
I have figured out offline, thanks to Vincent and Jorrit, how to use the
app (for anyone interested - Cally was hiding in the darkness at the same
starting point as the camera/player.)

However, I am still struggling to get to grips with the current state of
celPcSteer, celPcPathFinding and celHNavStruct. I have tried to collate
some of my ideas in this blog post:

http://www.crystalspace3d.org/blog/samd/2012/07/27/further_raamp_d_updates_and_concern_rega

If anyone has any comments regarding this I would be greatly appreciative.
It seems to me that a significant refactor of these plugins is needed due
to the duplication of functionality.

Kind regards,
Sam.

On Tue, Jul 24, 2012 at 3:56 PM, Sam Devlin <[email protected]> wrote:

> Hello All,
> I am trying now to let PcSteer use the functionality of Recast&Detour as
> part of my GSoC project. As I understand it the one example provided in CEL
> of PcSteer's use is appsteering (please let me know if there are more.) I
> understand that this app allows me to get the small woman model to either
> come to my current location, follow/pursue me around the level or flee from
> my current location. However, I cannot find her at any time when running
> the application to see if this is working correctly. Where does she start?
> And has my removal of lines 51-53:
>
>   /*iCelMapFile* entitiesfile = region->CreateMapFile ();
>   entitiesfile->SetPath ("/cellib/lev");
>   entitiesfile->SetFile ("walktut_entities");*/
>
> Affected this apps correct functionality? The above being neccesary to
> work around the bug I reported earlier in the summer. I am hoping to
> overcome this so that I can use this app to test the changes I am about to
> make.
>
> My understanding currently of the code is that I should need to only
> modify celPcSteer::Move (). By this time a destination is known and this
> could be used by R&D to construct and follow a path. Should I make my
> changes to allow both the current method and a R&D method if  a navmesh is
> available or should I work under the assumption that from now on navmeshes
> will always be used with PcSteer?
>
> Also I have noticed PcPathFinder, it seems to be a high level path finding
> property class much like CelHPath only with the ability to execute flee,
> pursue, etc. Are both neccesarry? Should PcPathFinder need to be modified
> as part of the integration of PcSteer and R&D or will using the navmesh at
> the level of PcSteer's move be sufficient as this will in turn be called by
> PcPathFinder?
>
> Kind regards,
> Sam.
>
>
>

------------------------------------------------------------------------------
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