Re: [Jsbsim-devel] Multiple property tree problem/soution

[gerard r. <gh...@gm...>]

On dimanche 28 juin 2009, Jon S. Berndt wrote:

>
> FlightGear would not know the difference - this is not a FlightGear
> capability. Multiple FDMs would be managed and run using JSBSim features.
> There is no difference between a single FDM and multi-FDM with JSBSim as
> far as FlightGear is concerned. The base aircraft will always be the base
> property tree - the first property tree. Let's say that the aircraft is the
> B-52 carrying the X-15. In the B-52 there may be a switch that tells a
> JSBSim system to drop the X-15. At that point, the X-15 would begin flying
> (the integration of the X-15 Equations of Motion would start). Obviously,
> there would need to be a way to link up a 3D model with a specific child
> flight model, but I don't expect that would be a major issue.
>
> I expect that for the near term (and I use the word "near" as a joke, since
> this multi-body capability has been in-work for many years), I expect
> FlightGear would not use this multi-body capability. I think it would be
> mostly a JSBSim batch mode feature. I'd like to see it used for multi-stage
> rockets, too, for instance.
>
> The challenge is to make sure that FlightGear is not adversely affected by
> the inclusion of this capability. I think Ron's suggested fix does that.
>
> Jon
>

Jon,
Thanks for that explanation.

That will be a great feature, i hope it will be available soon, and 
that "near" won't be  only a joke but a reality :).

The challenge regarding the integration within FlighGear  is an other "story" 
since today, like i said before,  we get some mistmatch  when FG is working 
with several instances of JSBSim.

Regards


-- 
Gérard
http://pagesperso-orange.fr/GRTux/

J'ai décidé d'être heureux parce que c'est bon pour la santé. 
Voltaire