Yes this is where it gets complicated. There are modes that are obviously relevant to mere flight dynamics, such as attitude hold, heading select, wings level, terrain following, etc. -- and even these use *sensor* inputs as opposed to actual FDM aircraft state data. The other modes that are tied more firmly to instrument/navigation/ILS etc. are of no interest to JSBSim. So, the answer might be to allow a split. Unless I am mistaken, it seems that ought not to be impossible.
I can't think of a reason why that wouldn't be straightforward and doable.
This question arises for several reasons, one of which is that I might want to model "non-standard" craft (I'll leave it at that for the moment). I want to control it in a specified way without worry that the flight will be affected in ways that I am unaware of -- that is, I'd like complete control (and *know* that I have complete control).
I think it would be totally up to the aircraft designer how they want to impliment the FG autopilot vs the JSBSim autopilot or some mix of the two. The FG side is completely reconfigurable on a per-aircraft basis.
Regards,
Curt. -- Curtis Olson Intelligent Vehicles Lab FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
