I've introduced an aliasing arrangement into $FG_ROOT/Aircraft/, so that we can use simpler identifiers, and so that JSBSim isn't treated differently from other FDMs. Here's an example:
--aircraft=c172 is now an alias for --aircraft=c172r which is an alias for --aircraft=c172r-jsbsim If, in the future, we happened to prefer the UIUC or YASim c172r as the default, we could simply change --aircraft=c172r to be an alias to --aircraft=c172r-yasim etc. This change depends on my patch to SimGear this morning to allow the 'include' attribute on the root element of an XML config file. You'll have to update to the latest SimGear CVS and make sure FlightGear is relinked with it. The main user-visible benefit is shorter names, like fgfs --aircraft=dc3 or fgfs --aircraft=sopwithCamel This also means that we can create new *-set.xml files by subtyping existing ones. For example, if someone made a DC-3 model for JSBSim, we could subclass the YASim config file like this: <?xml version="1.0"?> <PropertyList include="dc3-yasim-set.xml"> <sim> <description>DC-3 (JSBSim).</description> <flight-model archive="y">jsb</flight-model> </sim> </PropertyList> All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel