IvanK

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.

Agree its way to aggressive I get around 10-15deg of tilt change per press.

With Antenna elevation control mapped to HOTAS push button (RSHF+ ] and RSHF+[ ) The actual degree of change is way to much. No matter how small/quick you press the button the Antenna elevation jumps 10-15 degrees each blip. I should be able to get say 1 deg per blip.

Spent a lot of time chasing and fighting F5E's IRL , I don't recall ever seeing them smoke like they do in DCS in Dry power !

Great little jet but it smokes too Much in dry power.

Brilliant read

"The only thing you enter is the runway heading. No data parameter for ILS course in the PCN" Yep understand and in most ILS installations the ILS localiser is aligned exactly with the runway heading.(In some locations however it is offset)

" it only shows the deviations versus the localizer transmitter. If the dashed line is on the right, it means your position is too much on the left. You could be flying 90° relatively to the runway or on the same heading, that wouldn't change anything because it is only a deviation" Thats interesting so the HUD Localiser line angle doesnt reflect realtive angle to the localiser ? JoJo stated 2 posts up that ILS localser front course can be entered into the PCN. That makes sense to me and I think would probably be part of the procedure.

The Director bars still need to refrence a published fron course or Localiser course. In pretty much every aeroplane I know this Localiser comes from manual pilot entry or Data Base from a selected procedure.

This Vid was in the early days of the FA18 specifically when the FCS software was being tweaked for the Blue Angles aeroplanes. This was Very early FCS software 5.3 Prom where the aeroplane could be a little squrily. In the A/B Hornet you got Yaw tone at 25sec Yaw rate as I recall. If you didn't honour the tone the next thing you saw was a rapid increase in AOA. Now increasing AOA and Yaw sets you up for the roll coupling entry. Later Software effectively makes this so much easier ... a case in point is the later model FA18 software loads allowing the "Pirouette" manoeuver seen at airshows.

No mention in the new manual of CCM modes ... in fact cant find anything on the radar or CCM modes in the latest beta manual ?

I think you are referring to the phenomena know as "Roll Coupling" which is a real issue in many of the earlier fighters. The Mirage III had real issues with this with strict IAS v number of sequential rolls. I believe the MIR2K FBW system should prevent the onset of Roll coupling.

Having flown innumerable GCA's and ILS to minimas I would take a an ILS in preference everytime

For those ground based F18 operators a separate Civil VOR/ILS system is fitted the Navy ILS is removed completely. You dont have both systems though.

"And when the F-18C comes, there will be plenty of oppotunities to train ILS ........" For the record the Navy ILS is not compatible with ground based ILS ... totally different systems

Sadly according to Matts latest video there is no ILS in the DCS F5E. Thats a real shame VOR/ILS is an option IRL just depends on the buyers preference. Be nice if we could get an ILS at a minimum.

You shouldn't use the term "realign or align" in flight to remove or reset the INS position. This procedure is "Updating". you are telling the INS ... look I know you are drifting and your position is slightly off let me show you exactly where you are right now, now start computing again using this new updated position. Aligning and realigning is a completely different procedure usually done on the ground. An INS full alignment takes quite a while ... like 6 or more minutes. A quick alignment can usually be done as well its a lot less accurate but may only take 30secs. Same goes for a stored Heading alignment ... great for Scramble type situations but again inherently less accurate than a full alignment. Think of an Alignment as a complete INS reboot. Some systems can in an emergency perform a very basic alignment in flight but require wings level flight and typically a velocity input In addition the use of external navaids like an ILS to "update" the position is always subject to a degree of quality control (done automatically). In the case of an ILS update it typically only uses the localiser info so will only correct in one axis. In the case of the Mir2K I would assume this would only affect the lateral position of the Synthetic rwy and its Course line.

The F5E/F/N Fire Zone computation is limited to Rmax,Rmin and excess G.(probably only relevant to AIM9B 2G launch limitation) Together with actual range these are displayed by the reticle in miss mode. Even these Rmax and Rmin calculations would be very basic as no G versus Target Aspect information is used. Range rate is however part of the Fire Zone calculation according to the Data flow diagrams in the Navy and USAF manuals. What Fire Zone to use for each Missile type is a manual switch selection. This is selected pre flight and the selection switch is behind the seat. The USN F5N and USAF FE/F weapons delivery manual lists only the Aim9B,E and J as selectable options.