Re: [Flightgear-devel] About last cvs changes
On Tuesday 11 December 2001 6:39 am, you wrote: Martin Olveyra writes: 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) 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. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] About last cvs changes
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. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] About last cvs changes
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. So for instance if you want to run the YASim c310 with no panel but the hud activated (the config file might specify the panel active, but no hud) you can run fgfs --aircraft=c310-yasim --disable-panel --enable-hud Sorry for the confusion on this, as I said, we were figuring it out as we went along. 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
Re: [Flightgear-devel] About last cvs changes
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. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] About last cvs changes
On 2001.12.11 02:32 Curtis L. Olson wrote: Andy Ross writes: Martin Olveyra wrote: 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. I just picked up this change, too. :) The fix is simple. In all the xxx-set.xml files in your Aircraft directory, remove the sim/sim tags that enclose the rest of the data. This placement is done automatically by the loader now. I assume these changes are already in the queue for the base package. I believe these changes were committed this morning. No, they don't. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] About last cvs changes
On Tuesday 11 December 2001 12:06 am, you wrote: 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. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Sync again, the aircrasft files were missing the sim tag ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] About last cvs changes
On Tuesday 11 December 2001 12:29 am, you wrote: Martin Olveyra wrote: 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. I just picked up this change, too. :) The fix is simple. In all the xxx-set.xml files in your Aircraft directory, remove the sim/sim tags that enclose the rest of the data. This placement is done automatically by the loader now. but. but. I assume these changes are already in the queue for the base package. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] About last cvs changes
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
Re: [Flightgear-devel] About last cvs changes
On 2001.12.11 04:00 John Check wrote: On Tuesday 11 December 2001 12:06 am, you wrote: 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. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Sync again, the aircrasft files were missing the sim tag Don't! The right way is without the sim!! What a day!! :-P ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] About last cvs changes
John Check wrote: Andy Ross wrote: I assume these changes are already in the queue for the base package. but. but. Sorry, my fault. I had a sticky date tag in my base package. No, I can't for the life of me remember why. Of all of CVS's quirks, this is the worst; doing a cvs update in a directory with non-branch tags REALLY should generate a warning that you're not doing what you thought you were doing. Maybe I should get off my butt and fix that... Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
