On Tue, Aug 26, 2008 at 11:23 AM, gerard robin <[EMAIL PROTECTED]> wrote:
> On mar 26 août 2008, gerard robin wrote:
>> On lun 25 août 2008, Jon S. Berndt wrote:
>> > As posted by Dave in the JSBSim mailing list, I firmly agree: determining
>> > carrier location and orientation should not be an FDM specific function.
>> > This needs to be more configurable from the FlightGear side, so any FDM
>> > can take that information and do with it what it needs to do cat/hook
>> > ops.
I might be misunderstanding something here, but currently the generic
groundcache code returns catapults and wires:
// Return the nearest catapult to the given point
// pt in wgs84 coordinates.
double get_cat(double t, const SGVec3d& pt,
SGVec3d end[2], SGVec3d vel[2]);
// Return 1 if the hook intersects with a wire.
// That test is done by checking if the quad spanned by the points pt*
// intersects with the line representing the wire.
// If the wire is caught, the cache will trace this wires endpoints until
// the FDM calls release_wire().
bool caught_wire(double t, const SGVec3d pt[4]);
// Return the location and speed of the wire endpoints.
bool get_wire_ends(double t, SGVec3d end[2], SGVec3d vel[2]);
// Tell the cache code that it does no longer need to care for
// the wire end position.
void release_wire(void);
The FDM only has to use this information. I have done that for the
wires, but I don't understand the catapult model so couldn't do the
cats.
--
Csaba/Jester
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
