FS2000 - Cessna 300-Series RT-385A Navcom radio (Black version).
This navcom was very commonly found in the Cessna 150/152 but most have now been
replaced by more modern Bendix-King avionics. This gauge reacts to the default avionics
bus and lighting buses. The avionics bus must be switched on before the radio will work. 
The radio itself has no night-lighting but the VOR receiver is lit by a small external lamp.

On initialisation the gauge displays the last set comm and nav frequencies. To change
the codes use the + and - cursors below the rotary switches. There is an intermediate 
position between OFF and VOL on the navcom side of the radio; in this position the nav 
morse ident signal is disabled. To hear the morse signal switch the on/off knob to VOL.
Until this switch is set to either silent or morse ident the VOR indicator will show OFF.

The vor receiver has a hotspot in the lower left quadrant that displays a digital heading
readout for setting the needle with greater accuracy. Click on this area to show/hide the
display. The hotspot may show up as a black rectangle but this depends on how your video
display settings are; on some videocards the FS ToD settings need switching to night and 
then back to day before this will activate. The cause of this is unknown.

Both Navcom1 and Navcom2 receivers are included. Navcom2 has the Com radio tapped into
the (non-working) COM_STBY area of FS2K so that when you "twiddle the knobs" something
is seen to be happening on screen. ONLY NAVCOM1 CHANGES THE ATIS FREQUENCY. Also in
FS2K the VOR2 glideslope does not activate. This is a proven FS2K bug as the flag for
the glideslope goes active but the GS signal does not; consequently the VOR2 shows a
permanent GS flag. However, thanks to a fix by Arne Bartels you can now fly a LOC signal
on VOR2 when VOR1 is switched to a VORTAC. Formerly, switching VOR1 away from a LOC signal
when VOR2 was tuned to the same or a different LOC signal would cause VOR2 to stop working.

If FS2K2 proves to have the GS2 signal bug fixed then this archive will be re-released
with the (currently inactive) GS2 needle code activated.

To use the gauge with sound you must put fssound.dll into your \fs2k\modules folder and 
300_switch.wav into your \fs2k\sound folder. If you already have a version of fssound.dll
(you will be asked to confirm the copy) please check that you have the latest one in your 
\modules directory. If the dates and versions are the same then you may abort the copy
if you wish. If you find that the guage does not appear or that the sound does not work
then check your soundcard chipset. If it is based on any Aureal chip (usually Aureal-3D)
then the problem is because Aureal, although very widespread, is not fully Soundblaster 
compatible. Aureal have in fact gone bankrupt because they refused to address this problem.

If you do not like the sound supplied then you may substitute one of your own 
but it must have the name "300_switch.wav" to be recognised by the gauge. Be aware though that 
this change will affect all of the 300 Series radios as they all use the same switch sound.

The extraction syntax for this gauge is 

Navcom1

dfd_nc385b!vor_gs, XXX, XXX, XXX				//VOR
dfd_nc385b!navcom385, XXX, XXX, XXX			//Radio

Navcom2

dfd_nc385b2!vor_ngs, XXX, XXX, XXX			//VOR
dfd_nc385b2!navcom385-2, XXX, XXX, XXX	//Radio


Original bitmaps were supplied by Charles Grimes and minor mods applied by
Dragonflight Design.

Copyright 2001 Dai Griffiths Dragonflight Design.

You may not make money with this gauge in any way whatsoever but you may freely
distribute this gauge with any panel you design that is exclusively freeware.
You are also free to upload this gauge to any other FS site that does not charge
a fee for access or for downloads.
