On 2001.12.11 03:05 Martin Olveyra wrote: > On 2001.12.11 02:17 Curtis L. Olson wrote: > > Martin Olveyra writes: > > > This is the cvs log message I want to refer to: > > > --------------------------------------------------- > > > Log Message: > > > Small tweaks to initialization sequence and logic so we can default > to > > > a top level aircraft def file (c172-set.xml) > > > > > > preferences.xml or --aircraft= or any other property setting > mechanism > > can > > > be used to set the property "/sim/aircraft". After all options and > > config > > > files are parsed, the contents of /sim/aircraft is expanded into a > > > *-set.xml > > > file and loaded. > > > ---------------------------------------------------- > > > I synced to the last CVS Flightgear source and base. > > > Then I changed the value of the tag <aircraft> to c310, so to load > for > > > defect the cessna 310 instead of the 172. > > > Then, run fgfs --fdm=jsb (my favourite flight model. I also noticed > > that > > > the default flight model has setted back to larcsim) > > > But, the change in the <aircraft> tag value doesn't take effect. The > > c172 > > > is loaded instead. > > > > We made a couple changes in quick succession (hopefully learning from > > our, well my mistakes, as I went along.) > > > > The /sim/aircraft property has been eliminated. > > > > preferences.xml <include>'s the default aircraft (c172-set.xml). If > > you specify --aircraft=xyz, the corresponding config file is loaded > > and the properties it refers to are set immediately. So any > > subsequent command line options will override what came out of the > > aircraft config file. > > > I understand know the origin of the problem. > > So, the /sim/aircraft property has been eliminated but the <aircraft> tag > in the cvs version of preferences.xml is still there, with the value > c172. > Also, in the same file I see the tag <sim > include="Aircraft/c172-yasim-set.xml">, and not c172-set.xml, as you say. > Also, it is really a good idea to delete the tag <panel> in preferences.xml, because the panel is setted via xxx-set.xml files (and preferences.xml has precedence) With all theese changes, I finally was able to run fgfs without command line parameters and start with the desired aircraft (and its right settings) by changing only the include tag in preferences.xml
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
