Si quereis le pegamos una translation...
HARM Attack Display (HAD)The HARM Targeting System (HTS) page has received an overhaul. Note also that the HTS pod can be loaded on the
jet from the munitions UI page even if HARMs are not carried as part of the loadout.
The MFD display for using HTS is now called the HARM Attack Display (HAD). The previous HTS page was
embedded into the HARM‘s SMS MFD page. This was incorrect. The HARM SMS page and main MFD menu page
are depicted below.
HARM SMS Page Main MFD pageThe HAD is selected from the main MFD menu by pressing OSB 2 (HAD label). The HAD may be selected in any
mastermode but it can only be operated in A-G mastermode with HTS and AGM-88s loaded.
Selection of the HAD page without AGM-88s loaded will yield a BLANK MFD page. Operation is very similar to the previous HTS page,
but the HAD shares many common display features as the HSD. HAD cursor movement and expanded FOV (OSB 3
or pinky switch) options are similar to the HSD as well. The pilot may select the HAD range (HAD as the SOI) by
slewing the cursors up and down the display to bump range or by pressing OSBs 19 and 20.
The HARM WEZ/Footprint is based on Rmax of the AGM-88 and will increase/decrease in size according to your
speed and altitude. If the HARM WEZ is greater than the selected display range, the lines will be dashed.
Detected emitters are colored as follows:
Yellow = emitter active
Red = emitter tracking
Flashing Red = emitter launching
Green = emitter not active
HARM modesThe AGM-88 HARM can now be employed by using the previously coded HTS (for HTS capable F-16s) or via the
HARM WPN page for HTS or non-HTS capable aircraft. Two modes are available for employment: Position Known
(POS) and HARM As a Sensor (HAS). The third mode, Data Link (DL) is not implemented (at this time).
POS mode: In POS mode, aircraft attitude and target position are passed to the HARM. After launch, the missile flies
to the near reported position of the emitter and then activates its seeker to search for the handed-off threat. POS mode
has 3 flight profiles available:
1) Equations of Motion (EOM): Provides threat specific off-axis capability with a narrow FOV when the
seekerhead is activated.
2) Range Unknown (RUK): Provides threat specific off-axis capability with a wide FOV. Used when target
confidence is low. (Degraded state of EOM).
3) Pre-briefed (PB): Provides location specific, on-axis capability with a wide FOV. PB is used for long range
delivery with high confidence target location.
HOTAS Controls:
Cursor enable – toggles between POS and HAS modes.
TMS Right – Selects first valid threat, a 2nd TMS Right steps to the next threat
TMS Left – Toggles between threat tables
Pinky Switch – POS Mode cycles the POS flight profile; HAS Mode cycles the FOV
TMS Aft – Deselects the currently selected threat
Position Mode HUD SymbologyHAS Mode HAS Mode – ALIC Video After Hand Off
The POS Mode HARM Flight Profiles
There are 3 Position Known (POS) flight profiles: EOM, PB, and RUK (aka Target of Opportunity – TOO). Each
mode control at which point the missile will activate its seeker and what will be the FOV of the seeker. The most
accurate mode is EOM. It will activate the seeker at 5NM from the handed off steerpoint with a 40 deg FOV. This mode should only be used when the location of the emitter is well-known—i.e., emitter position collocated with a steerpoint. In PB mode, the seeker will activate at 15NM from the handed off steerpoint with a 120 deg FOV. This mode should be used when the position of the emitter is relatively close to the steerpoint. In the last mode, RUK, the seeker is activated immediately after launch with a 120 deg FOV. This is mode is used for self-defense as the range is completely unknown.
In HAS mode, the pilot uses the HARM seekerhead to detect threats. Detected threats are displayed left to right in the Detected Threat Status Box (DTSB). The pilot uses the cursor enable to slew the cursors and designate/hand-off a threat to the HARM. After a threat is handed-off to the missile, the display changes to represent missile boresight and the threat video responds to aircraft pitch, roll and azimuth changes. ―RDY‖ is displayed after hand-off is complete.
Operational Notes: HAS search mode will use the currently selected threat table to detect threats. The threats of the current table will appear on the left side of the MFD (next to each OSB). HAS delay timer will now be affected from all threats and not only the ones detected (simulating real system delay for sorting all emissions). HAS search mode will not show more than 10 threats. Search filter page (OSB #4 in the search page) will show the current table‘s threats on the left side. Clicking on the corresponding threat‘s OSB will select/deselect that threat from being detected and will reset the HAS timer and of course affect the search time. HAS FOV (OSB #3 in the search page) will now cycle through all modes – Wide (default), Center, Left and Right. The selected FOV will force the HARM to detect threats accordingly. Wide will search to a certain range (dependent on altitude) in all directions, Center will search at half of that range, Left and Right modes will search only Left/Right sides accordingly. Each time the FOV is changed the HARM timer will reset and all threats will blank (new search parameters). Hand-off time takes 5 seconds and will now affect missile tracking. Missiles fired before the threat was handed-off will probably miss, so wait for the "RDY" text to show-up after hand-off. HAS hand-off page will show up to 4 threats of the same type as the handed-off threat.
Other HAD Page FixesFix for HAD display. It used to flicker sim type symbol markers when there was a JSTAR in the mission. Turns out there were a selection of code bugs around this that date back to SP3. Now the code will update ground emitter target lists without blanking useful data about emitter status that were gathered by your on-board HTS pod. The JSTAR updates are staggered now also so that not every friendly in theater processes the emitter list in the same frame; minor performance improvement not likely noticeable in the grand scheme of things.
Now you should be able to use the EXP1 and EXP2 modes as intended -- the coloration on the symbols should be correct and it should be possible to take and sustain a target lock from the expanded modes. This same fix does both those things and it also fixes a problem with locks not being dropped properly when you did manage to get one in an expanded mode but then the target fell out of view of the HTS package.
HAD page should now more correctly show threats and the modes of operation those threat radars are using. For example, target locks are not erroneously flagged at long ranges and when a SAM system is guiding more than one missile the HAD page will continue the flashing red cue for the duration of the launch event (previously it timed out after 2.5 seconds every time for some reason – unsure why it was coded this way). As a result the HAD page should be more useful.
Note that some SAM systems don't go for lock until you are quite close to their firing criteria so you may not see steady red squares (target lock on to you) before it transitions to flashing red for a launch. It is doing the lock registration but with some systems, the AI locks and fires very quickly. Behavior of the HAD for aggregated units and deaggregated units should also be more uniform now.
Also, target lock is possible with the HAD page after all ownship HARMs have been fired. This extends also to allow you to direct your AI wingmen to attack based on either a lock on your HAD page or hovering over a threat with the HAD page cursor provided the HAD page is the current SOI.
Este sitio utiliza cookies propias y de terceros. Si continúa navegando consideramos que acepta el uso de cookies.
.
