On Fri, 2007-02-02 at 13:15 -0700, [EMAIL PROTECTED] wrote:
> Melchior wrote:
> >Now Dave sent me a patch which puts a generic kap140.nas into
> >$FG_ROOT/Aircraft/Instruments/, and I guess now is the time
> >to finally decide where such optional Nasal instrument (or
> >other) addons should go:
>
> There is a logic to using $FG_ROOT/Aircraft/Instruments/ that has
> not been mentioned.
> This file is only the interface via properties to a number of other files
> that are key to implementing the KAP140 in its various forms.
> The AC dependent xml configuration file is in
> $FG_ROOT/Aircraft/"ACname"/Systems
>
> The -set.xml file must point to either
> $FG_ROOT/Instruments/KAP140TwoAxis.xml, or
> $FG_ROOT/Instruments/KAP140TwoAxisAlt.xml
> depending on which model of the KAP140 is desired.
Actually the -panel file points to these, the -set files point to the AC
dependent xml configuration file in $FG_ROOT/Aircraft/"ACname"/Systems.
And, in fact, the generic panel in Generic/Panels points to the
KAP140TwoAxis.xml instrument as well.
:~/src/FlightGear-0.9-cvs/data/Aircraft$ grep KAP140 [!Instruments]*/*.xml
SenecaII/SenecaII-base.xml:
<path>Aircraft/c172p/Systems/KAP140.xml</path>
c172p/c172p-set.xml: <path>Aircraft/c172p/Systems/KAP140.xml</path>
c182/c182-set.xml: <path>Aircraft/c182/Systems/KAP140.xml</path>
c182rg/c182rg-set.xml: <path>Aircraft/c182/Systems/KAP140.xml</path>
pa24-250/pa24-250-set.xml: <path>Aircraft/c172p/Systems/KAP140.xml</path>
:~/src/FlightGear-0.9-cvs/data/Aircraft$ grep KAP140Two */Panel*/*.xml
Generic/Panels/generic-vfr-panel.xml: <instrument
include="../../Instruments/KAP140TwoAxis.xml">
c172p/Panels/c172-vfr-panel.xml: <instrument
include="../../Instruments/KAP140TwoAxis.xml">
c182/Panels/c182s-3d-panel.xml: <instrument
include="../../Instruments/KAP140TwoAxisAlt.xml">
c182rg/Panels/c182rg-3d-panel.xml: <instrument
include="../../Instruments/KAP140TwoAxisAlt.xml">
pa24-250/Panel/radio-panel.xml: <instrument
include="../../Instruments/KAP140TwoAxisAlt.xml">
> All the KAP140s so far are 2d instruments.
OSG's pick animation makes it trivial to create 3d instruments, in fact
I would like to replace most if not all the c182rg's intruments with 3d
versions in the near future. I've already done a transponder and
started on the nav/com radios. A 3d kap140 is on my list, too.
> The thought was by putting kap140.nas in the same
> place as the required generic xml files, it would be
> easier for someone to implement this autopilot in other
> AC.
Agreed, but $FG_ROOT/Instruments/KAP140TwoAxis.xml or
$FG_ROOT/Instruments/KAP140TwoAxisAlt.xml are not required once I (or
someone else) does a 3d KAP140 display.
> Today, 6 AC versions use this one file:
> pa24-250, c172p, c172p-2dpanel, c182, c182rg, and
> IIRCC a 2dpanel c182.
>
> I believe that the radio stack entries for all these AC reside
> in $FG_ROOT/Aircraft/Instruments
Yes, today that is true. Clickable 3d instruments were very hard before
OSG brought the pick animation. Now they are almost trivial. A 3d
instrument is easier to do now than a 2d one.
I for one would like to reserve the Instruments/ and Instruments-3d/
folders strictly for cockpit displays. Nasal scrips that drive the
property tree and configuration xml files need to go someplace else.
whether that is Aircraft/Generic or we create Aircraft/Nasal and
Aircraft/Systems folders. The place for blackboxes in in the avionics
bay not in the cockpit next to the display heads.
V/r
Ron
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
