Re: [Flightgear-devel] generic-instruments.xml and a second DME device
On Thursday 23 March 2006 08:31, Ron Jensen wrote: > It works for the Concorde in 0.9.9, I just checked. It has an aircraft > specific Concorde-instruments.xml containing (among other things) Thanks Ron! I discovered my mistake after looking at the Concorde config for an hour. The instrumentation config file has to be included inside the tags otherwise the tag is just treated as a property. So there is a need for two sections in a set file. One inside the sim section and one outside the sim section. > TACAN is every bit as generic as DME or VOR. Every military aircraft > produced since about 1950 has had a TACAN set installed. Sure, it's generic to military aircraft but does that mean that all civilian aircraft in FG should have TACAN as well? Why aircaft like the j3cub must have tacan, KT-70, wxradar, mk-viii by default is beyond my reasoning capabilities. :) And why are two nav radios and comms radios set up in the generic config and not two dme devices? There are far more aircraft with dual DME devices than there are aircraft with TACAN capabilities. And then there is the mk-viii which should never have been added to the generic config since it's used on a very small percentage of aircraft. Regards Paul --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] generic-instruments.xml and a second DME device
ons, 22,.03.2006 kl. 20.41 +0200, skrev Paul Surgeon: > After some debating in IRC ... > > Can we please add a second DME device to Generic/generic-instruments.xml? > > i.e. > > dme > 1 > > > It is ***NOT*** possible to create extra devices within an aircraft's local > config files. I've tried it and it does NOT work. > All you end up with are some properties but nothing that drives them. An aircraft's local instrumentation config file is just a replacement that overrides Generic/generic-instruments.xml, so in principle, if it does not work with the local config file it wouldn't work any better in generic.instruments.xml. Remember that you also have to supply power to your new DME, and that the serviceable property should be set to "true". > If the tacan, KT-70, wxradar, mk-viii which are not generic can live in > generic-instruments.xml then I see no argument against a second dme > instrument living in there too especially if that's the only place to do it. When I created the generic-instruments.xml file I included whatever existed hardcoded at the time. Since then new instruments have been added. It would be preferable if every aircraft had its own customized instrumentation config file (and systems config file). -- Roy Vegard Ovesen --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] generic-instruments.xml and a second DME device
On Wed, 2006-03-22 at 20:41 +0200, Paul Surgeon wrote: > After some debating in IRC ... > > Can we please add a second DME device to Generic/generic-instruments.xml? > > i.e. > > dme > 1 > > > It is ***NOT*** possible to create extra devices within an aircraft's local > config files. I've tried it and it does NOT work. > All you end up with are some properties but nothing that drives them. It works for the Concorde in 0.9.9, I just checked. It has an aircraft specific Concorde-instruments.xml containing (among other things) dme 0 dme 1 and loads it from the concorde-set file with : Aircraft/Concorde/Systems/Concorde-instrumentation.xml Then uses it in Aircraft/Concorde/Panels/Instruments/concorde-dme.xml > The majority of large airliners have a DME device per NAV radio and don't > feature DME switching between NAV 1 and NAV 2 like a lot of the smaller > aircraft nav systems have. > At the moment it's impossible to have two DME distances displayed in a > cockpit. > > If the tacan, KT-70, wxradar, mk-viii which are not generic can live in > generic-instruments.xml then I see no argument against a second dme > instrument living in there too especially if that's the only place to do it. TACAN is every bit as generic as DME or VOR. Every military aircraft produced since about 1950 has had a TACAN set installed. > Thanks > Paul > --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] generic-instruments.xml and a second DME device
After some debating in IRC ... Can we please add a second DME device to Generic/generic-instruments.xml? i.e. dme 1 It is ***NOT*** possible to create extra devices within an aircraft's local config files. I've tried it and it does NOT work. All you end up with are some properties but nothing that drives them. The majority of large airliners have a DME device per NAV radio and don't feature DME switching between NAV 1 and NAV 2 like a lot of the smaller aircraft nav systems have. At the moment it's impossible to have two DME distances displayed in a cockpit. If the tacan, KT-70, wxradar, mk-viii which are not generic can live in generic-instruments.xml then I see no argument against a second dme instrument living in there too especially if that's the only place to do it. Thanks Paul --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel