VKing

1) Cannot enter 30 MHz. The pilot cannot enter 30.000(0) into the UFC. Anything over 30.000 works, like 30.0001 and 30.001. 30.000 can be entered as preset using the mission editor, and this will work. 2) Decimal representation under 100 MHz The radio appears to mandate 6 digits frequencies at all times, which means frequencies lower than 100 MHz have four decimal places instead of three. 3) Any kHz value can be entered I'm not entirely sure if this is a bug, since I don't know the details of the radio, but in DCS, you can enter any value in the kHz field. So e.g. 123.456, 99.9999, and 30.0001 are valid frequency entries in the UFC. Harrier_Radio_Freq_entry_bug.trk

I'm pretty sure that if you turn your radar altimeter to zero, you turn it off. So no radar signal is given at all, which is an invalid signal for HUD display purposes, and it returns to barometric.

Since none of the switches in the diagram mention the HMD, yet section 2.21.8 explicitly says: "VTR selector switches located on the forward and aft CVRS Control panels allow selection of HMD video recording.", I assume the panel changed when the HMD system was installed.

You're trying to enter coordinates in degrees and decimal minutes into an interface that takes degrees, minutes, and seconds. It doesn't accept the entry because you entered 86 seconds, which doesn't make sense since a minute is 60 seconds. E: To convert you need to multiply the decimal fraction by 60 to get the amount of seconds, so in your video, you would multiply .863 minutes * 60 = 51.78 seconds. So to enter the coordinate in the video, you would type 24°24'52''N, 55°17'35''E.

The only thing I can find is that AN/AWB is the code for "Airborne Armament Bombing Equipment", and that the AWB-3 is apparently used (although I don't know whether exclusively) in the Canadian F-188 Hornet.

I've had this as well, and it was because the gun was selected in the SMS before switching to NAV mode.

On page 160, there are two boxes saying "COMM1/2 Preset channel selected. M: Manual. E: Emergency Guard (243.000)". The left one is pointing to the channel display for COMM1, showing M, the other is pointed to the channel selector knob for COMM2. (The label for COMM2 channel selector is pointing to the COMM2 channel display, which is showing 1). The guard channel in the Hornet is labelled "G", not "E", and there are many options other than E(G) and M (although those aren't really useful, but it could be nice to explain them).

:thumbup: You missed the Ground Track/TAS typo on page 165, which is now page 167.

Good stuff. Page 15, cockpit: The Flight Control System RESET switch is mislabelled "ECS (Environmental Control System) Reset Switch". Page 156, Radio intro: Reference to Harrier in the text. Page 159, autopilot: The picture taken from the NATOPS mentions the basic autopilot enabled by On/Off button, but it's not mentioned in the text. Pages 164-165, HSI: True airspeed on the left side of ownship symbol is mislabelled as ground track.

It's [NO BUG] because there's no bug (the bracketed part is added by ED). The gun in the hornet has the correct 4000rpm rate of fire in LO and 6000rpm in HI. They sound the same but the rate of fire is different. It takes 5.7 seconds to empty the gun in HI, and 8.7 seconds in LO.

I understand the Tunguska uses command guidance for its missiles and has an optical tracking system, allowing it to fire without giving RWR indication of a radar lock. However, it appears to be able to do so even through clouds and 100% cloud cover, where, I believe, it would have to use its tracking radar in order to guide missiles. Tracks attached doing the same test in the F-15 and F-18, showing the 2S6 firing missiles without a radar lock through ~650 feet of 100% overcast. Tunguska_SACLOS_thru_clouds.trk Tunguska_SACLOS_thru_clouds_F-15.trk