Implementation Notes:

Some of the units require a few properties to be pre-defined. See the file "Systems/init-instrumentation.xml" for a typical case.

The KN-62a, KT-76c, and KX-155 require Nasal support. See the appropriate files in the Nasal directory, included with this package. Make sure the Nasal files are imported in your <aircraft>-set.xml file.

Make sure your aircraft is importing the appropriate instrumentation functions in your instrumentation.xml or equivalent file. The possible required inclusions are:

<adf>
  <name>adf</name>
  <number>0</number>
</adf>

<nav-radio>
  <name>nav</name>
  <number>0</number>
</nav-radio>

<nav-radio>
  <name>nav</name>
  <number>1</number>
</nav-radio>

<dme>
  <name>dme</name>
  <number>0</number>
</dme>

<transponder>
  <name>transponder</name>
  <number>0</number>
  <mode-c-altitude>/instrumentation/encoder/mode-c-alt-ft</mode-c-altitude>
</transponder>


Most of the units rely on clickable hotspot panels for functionality since the buttons are often small or knobs may overlay each other, making pick animations problematic. So most functions will not have pick animations. If you want to rely on pick animations over hotspots, refer to the hotspot files for the necessary command bindings. These files are identified by the word 'panel' in the file name, in the "Models" directory.

See my Velocity or Optica for examples of implementations.

Gary "Buckaroo" Neely
