IvanK

1. ADF is only usable for UHF DFing. So you would meed a UHF NDB in the tuneable range of the radio. Alternatively it can be used to "DF" a radio transmission on the tuned frequency. It cant be used like a conventional NDB/ADF combination.

Just had to give it a try :)

During ejection Northrop seat turns into ACESII seat :) (Just Ejection Graphic animation I think)

nope happening at meduim altitude with direct Line of Sight to the TACAN station

Thanks Eddie but I have been inside 25nm of the TACAN station. Will try turning dwn the TACAN Volume to see if it changes.

I don't see anything with the Landing lights they don't extend with Switch selected on and gear down.

Ah the joys of Manual depressed sight bombing ... sight handling is an art. In training you will notice where the Target sits reference things like the canopy rail. This then allows you to achieve a consistent dive angle regardless of your Base distance out. Of course you can only get so close as you need to allow for turn radius as well (Minimum Attack Perimeter MAP). So whilst on base establishing the correct relative position of the target sets you up to establish a reasonably accurate dive angle. A smooth roll in using Lift vector pointed to just above the target (dont dish the roll in) also helps in establishing the planned dive angle. On roll out you need to establish the correct Initial Pipper Placement (IPP calculated before flight) below the target. (The Flight Path is actually held at a point just past the target known as the Aim Of Point ... without a VV that is kind of nebulous ... that's why the IPP is so important). On Roll out note your dive angle (ADI/AH) ... if its not the planned dive angle then decide on a release altitude adjustment. If Steep then release slightly earlier than planned, if shallow then release slightly lower than planned (fingers in ears). Yugging to achieve the planned dive angle wont work ! ... accept the dive angle you achieve and adjust release height. Then as you travel down the dive try to hold the Flight Path on the Aim of Point just past the target. As you proceed down the pipper will drift up on to the target .... make smooth tiny bank corrections to dribble the reticle on to the target. Also monitoring altitude and IAS build up. You need to achieve pipper on AT the planned release altitude AT the planned release speed with the flight path on the Aim of point. Get them all right and a decent bomb will be the result. get any one of the wrong and bombs can go anywhere. As per dive angle corrections Airspeed errors can be compensated for by minor changes to release altitude. Though be super careful releasing low as you might bust the Frag envelope, run out of turning room and hit the ground, or release below the minimum height for fuse arming.

Something is wrong IMO on the logic behind the display of Ground clutter on the radar. Given the Antenna should be Earth/horizon stabilized, Pitch attitude changes (within limits) should not change the radar scan coverage. However if you vary pitch attitude with radar say 30deg up you can easily get ground clutter appearing at relatively low pitch attitudes.

Google found this :) http://forums.eagle.ru/showthread.php?p=2534793 As to only putting in TACAN's at real world locations, I don't think the ones we see in Georgia are real world ones.

I get a hissing sound in the cockpit that seems to come and go at random. It sounds almost as if the Squelch on the radio has been lifted. Cant see any pattern in it. Also if you go to external Fly by mode (F3) then jump back in the cockpit cockpit sounds are muted for quite a while. they eventually come back to normal.

not seeing this External transfer seems to be working normally for me. I started with 3 External tanks. Selected Inboard pylons initially. Roared around in AB. Left needle sat on 2000lbs, right needle on 2400lbs. after a while ext tanks empty light illuminated with light on caution panel. Left needle started dropping. Cancelled the light. Selected inboard pylons OFF and Cl on. Left Needle rose back up to 2000lbs. After a while EXT tanks empty light came on and left needle started dropping again. Turned off Cl then auto balance. So to me everything is working as it should.

Agree. I am using Crosswind pedals. For Rudder axis I use a Dead zone of 8 and a curve 30. NWS feels pretty right to me with what I recall IRL last century.

KUBAN/CRIMEA MAPS With more modules being released that incorporate realistic TACAN use could we get more TACAN stations on the map ? Ideally for all airfields. Ideally being hard coded for the map provides standardization for all users. PORTABLE TACAN These exisit and can be transported in by transport aircraft and set up fairly quickly (like in 24hrs). With this in mind it would be nice to have as a Mission object to allow Mission builders to drop in TACAN units on a need basis.

image of Swiss F5F rear seat combined Mach/ASI showing Mach number in flight :) From this source: http://www.blick.ch/news/schweiz/exklusiv-360-fotos-aus-dem-cockpit-der-patrouille-suisse-so-haben-sie-die-schweiz-noch-nie-gesehen-id2991534.html

+1 Agree

After a bit of sleuthing I came up with this diagram of the Mach number scale in the AVU-8 combined ASI/Mach instrument. the AVU-8 is I believe the specific instrument fitted to the F5E ref USAF TO/Flight manual T.O. 1F-5E-1 This diagram clearly shows that the Mach scale is in 0.05Mach increments with Mach number numerals at each 0.1M. Scale reads from Mach 0.5 to Mach 2.2 The source document for this manual can be obtained here: https://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&source=web&cd=16&ved=0ahUKEwiim-iWlovOAhVJX5QKHSMDAyU4ChAWCDQwBQ&url=http%3A%2F%2Feveryspec.com%2FMIL-PRF%2FMIL-PRF-010000-29999%2Fdownload.php%3Fspec%3DMIL-PRF-27197D.042355.pdf&usg=AFQjCNELmcXEapsV4D84cKudN4Bu4idpow&sig2=Z0BDnQpRj5UthumYG4_ukw&cad=rja

Looking at the Mach scale on the combined ASI/Mach meter the Mach scale only has 2 subsonic references 0.5M and 1.0 Mach.Looking at the DCS F15 its the same. I don't think this correct I would have thought the Mach scale would be graduated in 0.05M increments with Mach number text at each 0.1M increment like in the image below. Looking at DCS F15 and F5 instruments they are scaled at 0.1M in the supersonic range, just not in the subsonic range.

Gun Mode 2 (GA2) is designed for easy maneuvering targets ... pretty much standard LCOSS with all the usual tracking/settling times to get a valid solution. Ftr v Ftr you are better using GA1 which is in effect a snapshot sight. Regardless of Gunsight selected mode selecting Dogfight Guns (DG) will put you in GA1 with boresight radar lock out to 5600ft range. (the sight head switch will remain on whatever its selected on). Hitting Return to search will then take you back to whatever mode you have selected on the sight. so IMO unless you are trying to gun a relatively non maneuvering target you are always better off in GA1.

DCS issue happened after previous update, something to do with Vr support messing with TrackIr status.

I ended resolving this. Normally I avoid straight out DX button assignment and use CH scripting. Anyway for this I just assigned it inside DCS as a DX button and now all is good.

Identical chart it would seem for the NAVY F5N source F5N NATOPS manual. Duckbill nose might help a little compared to conical nose.

As I understand it the F5E ADF system is a UHF system so will only work with dedicated UHF NDB systems ....ones that have Mhz freq not Khz freq. UHF NDB's are far and few between. It wont work the usual NDB's in DCS that use Khz. Another typical RL use is in a SAR type scenario. Assume the downed pilot is transmitting on his survival beacon on 243.0mhz. You would tune your UHF to 243.0mhz select DF then on the NAV control panel set it to DF. When the downed pilot transmits the HSI bearing needle should point to the pilot, but only whilst he is transmitting. You can actually triangulate a source by flying a constant heading and taking a series of running fixes :)

ADF is UHF DF only... so wont work with normal NDB's

Indeed very small FOV but its also harmonised to the top of the reticle. In MSL mode the pipper reticle indicates missile boresight corrected for wing flex. If I uncage the AIM9 (RSHFT+M) and hold the button pressed the missile fire command isnt read. Seems that pressing and hold the cage button stops the missile fire command from being read ? Not sure if this is bug or a HOTAS scripting problem using CH stuff. Seems as long as one button is held depressed no other commands are read. On Launch Left Missile drops down off the rail before acceleration. Right missile jumps up off the rail before accelerating. These AIM9s just eat flares every time.... Instant Mission Intercept the Bear.

Agree with Tweet the float in the flare is way to excessive. Seems to me the reduction in induced Drag as you enter ground effect is overdone.