John Check writes: > > Right -- the problem with the include approach is that preferences > > gets precedence over the aircraft config file, rather than the other > > way around. I think we're going to have to go with a different > > approach. > > > > > > All the best, > > > > > > David > > Yes but if we migrate aircraft specific stuff out of preferences it's not a > problem.
It's not that simple -- there's a very good chance that you'll want to set other properties to non-default values as well. For example, X15-set.xml should probably set a non-0 starting altitude and speed for the X-15, and some models might want to start pointing straight up (i.e. a rocket). Here's what we want: 1. Load preferences.xml. 2. Load the default aircraft file (based on the /sim/aircraft property), overriding values from preferences.xml. 3. Parse command-line options. The --aircraft option should both set the /sim/aircraft property *and* immediately load the appropriate aircraft file, so that order of precedence on the command-line is preserved. With these simple steps, everything should behave intuitively. If I type fgfs --prop:/sim/model/path=xxx --aircraft=c310 I'll get the default 3D model for the C-310, since the aircraft file was specified later; on the other hand, if I type fgfs --aircraft=c310 --prop:/sim/model/path=xxx I'll get the xxx 3D model for the C-310, since the model-path property was specified later. All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
