Hulkbust44

Can you restate the question?

Yep, HARM, ALR-67, and ASPJ all work together. To the point there is an caution on the RWR display for when it can't talk to the HARMs. We're still missing things like TOO range known vs unknow and TGT designations. Also A/A sensor contribution, MN FILE, actual PB capability...

Not necessarily STEP, but rather the TUC logic.

It should just be when it's uncaged.

"missing evidence"? Take a look at any A/S combat report from 91', last I checked it was the most employed weapon.

TDC depress would only be used for designation in INR. It is automatic in SCENE and AUTO. EDIT: missed the LITENING specification. Area and point track are automatic designation.

If you don't need the survivability features of the harpoons, i.e surface skim flight and popup logic, you could use a SLAM or SLAM-ER with aircraft guidance.

Then the question is, why did the system in DCS fail? I performed a max performance recovery and still couldn't avoid the CFIT. The system assumes recovery will be less than a max pull to the max available G anyway, so there should be no way the CFIT should've happened unless the calculations were wrong somewhere. "...the TAWS-with-DTED mode and provides protection against varying terrain ahead of the aircraft." Check NFM-00 2.17.4.1

From NFM-000, the TAWS warnings have the highest priority sounding 3-6db over any current warnings. As shown in the track, I heard the altitude woop woop warning, but did not hear the TAWS recovery command warning, only saw the arrow. TAWS_RADLT.trk

As you will see in the track, the recovery cues for the non sea-level terrain is triggered way to late making the commanded CFIT recovery impossible. It seems that the dive recovery phase trajectory is not being calculated correctly with the system assuming the terrain after the calculated future impact point is at the same altitude. I.e. not accounting for upslope terrain, thus the warnings are triggered too late. TAWS.trk

It's one of the TRACE theses, integration of tactical imagery maybe?

Yes, you can do a tacan fix, overfly does not work yet IIRC. The INS simulation is lacking, no DL fix, flyover fix, radar fix, no PVU etc.

Really? Is this not common sense? The other track data such as range is there, If there was not supposed to be data there, the field wouldn't exist in the first place... on it's way

Going to complain about the HUD designation reticle too? Never get a HUD failure where you'd need to do a INS fix later would you? BU should have some other functions, but it's great for seeing the presets.

Title. Unable to enter civil GUARD of 121.500, or any freq for that matter. GUARD.trk

Don't forget ROE/IFF and CAS,

As it is now, the radar sensitivity indicator value is hardcoded to "7" (values should be 1 to 9) This is a very important cue to tell the pilot how the radar is expected to perform in the current conditions. The value is an indication of how much the radar has needed to adjust filters to achieve positive target detection. (too high sensitivity could result in false targets) A "1" would be where the most filtration is required and thus a target needs a strong return echo to reach the detectability threshold. The closer a target, the stronger it's return, so the detectability range is reduced. This could be a worst case scenario when the radar is receiving a lot of ground clutter and there is strong radar jamming in the area. A "9" would be your best case scenario with med-high altitude and minimal ground clutter do to elevation angle. This is a very important thing to have in DCS, especially with the severe look down penalties.

Without radar contribution, when you TUC a PPLI on the AZ/EL the Vc is 0. The is clearly a bug as the Vc is not zero, and the Vc would be known as we have range data. noVc.trk

@BIGNEWY What information is missing? I can provide evidence of everything from HARM MSI data priority logic, to HARM manual new threat data filing for A/A.

It's half the Attk format scale

"AUTO" Is a target designation and tracking mode for the ATFLIR. TDC depress is not, and can not be correct.

On the SA format with a TUC of a non PPLI track, the legends on OSBs 1-4 should display the PLID menu automatically. There should be no "PLID" button. The HOS, FRD, UNK PLID *options* (with the current one boxed) should be displayed when the TUC is a non PPLI. In addition, PB 1 should have the SCMIT (self-commit) legend. (shows commit on network) If the TUC is a PPLI track, the options should be C2 (request command by the platform TUC'd), DONR (selects track to be a donor), and MEMB (selects track to be a flight member) PM for sources inbound no_autoplid.trk

The purpose of the STEP cursor on the SA format is to occlude the data not associated with the selected track, making it easier to see in a cluttered environment. In DCS there is no blanking of the data under the STEP cursor kind of defeating the purpose. No track needed here, you can see that the STEP box is not hiding anything. PM with source coming. null

The max SA format non-decentred scale selection is 160. This should go up to 320. 5, 10, 20, 40, 80, 160, 320 With a de-centred (DCNTR) display the scales should be 7.5, 15, 30, 60, 120, 240, 480 NM (ranges in NM from own-ship to top of display) DCNTR in DCS is doubling the current scale infront of the aircraft, and moving own-ship symbol to the bottom. This is wrong. DCNTR should be displaying 3/4 of the display infront of own-ship, and 1/4 behind it. Source: 2003 change of 600-100 @BIGNEWY PM inbound scl.trk

With the Sparrow mode selected and a valid radar target, pressing cage uncage for <0.8 seconds should command FACQ just as with the SCS. Pressing cage/uncage for >0.8 seconds toggles AIM-7 LOFT. PM inbound aim7cage.trk