> Martin. > P.S.: I _really_ believe it would be wise to separate FDM and FCS using a > clean interface - but this is different from the above ;-)
In JSBSim it already is. There appears to be a misconception that the FDM and FCS are inappropriately linked together. In JSBSim the atmosphere, rotational and translational dynamics, ground reactions, aerodynamic forces, mass properties, flight control system, propulsion, trimming, initialization, etc. are all separate models/entities. Together they comprise everything one needs to simulate an aircraft non-visually. This is one thing JSBSim is designed to do - to simulate aircraft in batch mode or to be the flight model "guts" for a visual simulator. We keep the FCS code pieces in a separate directory from the rest of the JSBSim FDM code. The FCS class manages a set of FCS building blocks. These building blocks can get the values of parameters they need from a single call to a retrieval mechanism, GetParameter(). Given this "mission goal" for the JSBSim class hierarchy, we are doing exactly what we set out to do, and in a wise way, I submit. Jon Jon Berndt Coordinator, JSBSim Project http://jsbsim.sf.net Enter BUG REPORTS at http://sf.net/tracker/?atid=119399&group_id=19399 Enter FEATURE REQUESTS at http://sf.net/tracker/?atid=369399&group_id=19399 _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
