Registrado: 17 Jun 2007
Mensajes: 29
|
10/09/2011 20:33:45
|
|
Sacado de de la paginas 75 a 78 del manual falcon BMS
AMRAAM Dynamic Launch Zone (DLZ) Updates
The appearance and terminology of the AMRAAM DLZ has changed if the M2-style AMRAAM DLZ option is selected. The following is a summary:
Raero – Raero (Range Aerodynamic) (small triangle) represents the maximum kinematic range of the AMRAAM and is the longest possible shot that a pilot can take and have a chance of hitting the target. It assumes the target will not maneuver and that the missile is perfect. It currently does not take optimum loft conditions into account (which should further increase range).
Ropt – Ropt (Range Optimum) (small circle) represents the maximum launch range with some buffer to offset any target turns. It is 85% of Raero. It currently does not assume the shooter will achieve optimum steering and pitch.
Rpi – Rpi (Range Probability of Intercept) is 75% of Raero and is a range that has a higher probability of hitting the target.
Rtr – Rtr (Range Turn and Run) replaces Rmax2 and represents the maximum range shot assuming that the target performs a turn-and-run maneuver at launch. Technical calculations are described on pg 106.
Rmin – Rmin replaces Rmin1 and Rmin2 and represents the minimum launch range. It is based on Rmin1 calculations.
AMRAAM Loft Solution Cue – A loft cue was added to aid the pilot achieve a lofted shot. It is above the Raero caret on the HUD and MFD and consists of a one or two-digit number representing the appropriate climb angle. When the DLZ target range cue reaches Raero the loft angle provides the conditions required to achieve an Raero shot (target range between Raero and Ropt) or an Ropt shot (target range between Ropt and Rpi). For either shot, center the Attack Steering Cue (ASC) in azimuth relative to the Allowable Steering Error Circle (ASEC) and execute a smooth pull-up to the indicated loft angle placing the ASC in the center of the ASEC. The loft solution cue counts down (every 5 degrees) from the total required angle as the pilot pitches the aircraft up to the MMC-specified loft angle. When the angle is reached, the cue will read ―0‖ (zero) degrees to indicate that the pitch has been achieved. The loft cue is removed when the target range is less than Rpi. The loft cue does not take into account aircraft AOA while the display of the ASC does. This can result in a situation where the ASC is in the center of the ASEC (dot in the hole), but the loft solution cue is indicating a required loft angle. The greater the AOA is the greater the difference between thepositioning of the ASC and the display of the required loft angle. The pilot should center the dot in the hole in this case. In addition there is a two digit value above the target closure value which represents a Digital Maneuvering Cue (DMC). This is an angle value sort of representing how much turn a target would have to make to significantly degrade probability of achieving a missile intercept.
AIM-120 Boresight Reticle – When the selected AIM-120 sighting option is Bore, or the selected sighting is Slave and there is no bugged target, the AIM-120 boresight reticle (262mr diameter circle) is displayed on the HUD (the Bore reticle is not displayed on the MFD).
AIM-120 Missile Diamond – The missile diamond flashes when the target is in range (Raero or less).
Allowable Steering Error Circle (ASEC) – The ASEC is a variable diameter circle displayed on the HUD and MFD when an AIM-120 is the selected weapon, sighting option is Slave, and a bugged target exists. The weapon status must be RDY or SIM (Master ARM in ARM or SIM) in order for the ASEC/ASC and DLZ to appear. If there is no bugged target, the AIM-120 Boresight reticle will be displayed. The ASEC is an aid for positioning the attack steering cue in order to take the best shot possible based on the steering. At target ranges from outside Raero to Ropt, the ASEC is its smallest size, 11mr radius. At Ropt, the ASEC begins to grow in size until target range reaches Rpi where it reaches its maximum size (the ASEC represents 45 degrees of allowable steering error at Rpi). From Rpi to mid-point Rtr, the ASEC remains its largest size, at which point it begins to shrink again until it reaches minimum size at Rmin. The ASEC flashes when the target range is within the maneuver zone. The ASEC‘s variable radius varies from 11mr to 56mr with a slaved target. For a bore shot, the radius is static at 131mr (262mr diameter). The ASEC on the MFD is identical in function.
Attack Steering Cue (ASC) – The ASC (8 mr diameter circle in the HUD, 10 pixel radius circle on the MFD) provides several types of steering: horizontal aircraft steering, a blend of aircraft and missile steering, optimal missile steering (with horizontal and vertical missile steering), or Rmin steering (shortest LOS to the target). The type of steering provided is a function of range to the target. Horizontal aircraft steering is provided against targets beyond 1.2 X Raero (where Raero is the maximum kinematic range of the missile) and is based on the limits of the ASEC and a 45 degress LOS to target limit. Blended aircraft and missile steering is provided for target ranges between 1.2 Raero and Raero. Inside Raero, the steering provides optimal horizontal and vertical missile steering. Once inside mid-point Rtr (half-way in the maneuver zone), the ASC provides Rmin steering. The pilot follows the ASC cue by rolling until the cue is on the HUD centerline above the center position of the ASEC and then pulls the aircraft (if commanded) to put the ASC in the center of the ASEC. When the target range is greater than Raero, a limit cross (X) is displayed inside the ASC to indicate that an AIM-120 shot does not exist even if the pilot performed a loft maneuver. The limit cross will also be displayed when the required lead angle exceeds 60 degrees, even if the target is nominally in range. Neither the ASEC nor ASC are displayed on the HUD in DGFT mode.
The following diagram sums ASC/ASEC relationship to the DLZ and the type of steering provided.
A/F Pole Cues – A-Pole (ownship to target range when AMRAAM goes active with MPRF) and F-Pole (ownship to target range at missile impact) ranges were added to the DLZ. A-Pole or F-Pole range indications, for the missile on the rail, were added to the DLZ below the Target Range Cue caret and Closure Rate indication. Indications are in NM with an M suffix for A-Pole (A is not used to avoid confusion with AMRAAM active indications) and an F suffix for F-Pole.
A-Pole or F-Pole range indications for the missile in-flight are added immediately below the DLZ. Post-launch cues are relative to winning Missile-Of-Interest (MOI, the missile aimed at the bugged target with the longest time remaining until impact) for the current bugged target. Changing the bug in TTS or TWS will provide A/F pole cues for the MOI for each if missiles are in flight to both.
Time remaining indication for the in-flight MOI is still displayed in the second field below the DLZ. This can show one of several prefixes: "A" (time to HPRF), "M" (time to MPRF), "T" (time to intercept) or "L" (time to termination; basically missile time of flight remaining). Note that this timer is more persistent than before. It‘s dynamic for bugged target and a winning MOI. For a winning missile where you lost track or snipped, the count becomes a simple stop watch. One note of caution: it‘s not a bug that the timer doesn't count down in linear fashion for a bugged target with an active DL missile. The time to intercept is calculated dynamically and takes target maneuver into account so it‘s perfectly reasonable for that count to increase even in some cases.
Missile datalink has been fixed to allow you to support up to six missiles in flight. These may be fired on up to two targets (TTS) or up to six targets (TWS). You can get A/F pole and time remaining data for all six missiles if you have six in flight and provided that their intended targets are still present on the FCR as track files.
HUD, HMS and FCR displays all include updated A/F pole cues.
The radar model for AMRAAMs now includes HPRF (Husky) mode for favorable target geometries. The missile will activate the seeker well before the normal MPRF (Pitbull) range and attempt to track. HPRF is better at tracking high aspect targets with high closing range rate. Datalink guidance will continue up to MPRF unless the pilot commands a snip (drops the radar track) before that time. During HPRF with host DL guidance, the missile will use the best tracking solution available (either seeker or host DL guidance). HPRF and MPRF activation are now entirely based on range to target (used to be time-to-run based). Ranges coded are rough guesses for the AIM-120B. Other (active radar) missiles will need specific dat file edits (the AA-12 has been done already).
The variables are:
AspectSelectorSize – HPRF requires target aspect to be within this many degrees of 180.
HuskyMinClosure – HPRF will not activate unless range rate is higher than this threshold
HighAspectBomberHusky – Select LARGE target (AIM120 SMS page) to use this as HPRF range gate
HighAspectFighterHusky – Select MED or UNKN target (AIM120 SMS page) to use this as HPRF range gate
BomberPitbull – Select LARGE target (AIM120 SMS page) to use this as MPRF range gate
FighterPitbull – Select MED or UNKN target (AIM120 SMS page) to use this as MPRF range gate
Note: you can select SMALL in the SMS page. Doing so doesn't make a lot of sense in Falcon4 since this is apparently intended for targeting small RCS targets although it might be useful against helicopters. If you do choose small, MPRF ranges are reduced by around a third compared to MED.
Bug fixes relative to older versions of BMS in this general area: fixed bogus clearing of target when you flip between override modes or SMS changes from one missile type to another while you have a bugged target – now the lock is maintained. There is also a fix for datalink – previously last slammer was never provided with any datalink guidance making it significantly worse in performance compared to a missile fired with more of the same (slammer) type left on the rail.
AMRAAM DLZ Transitions
1) Unexpanded AMRAAM DLZ Scale: When the current target range is greater than 125% of Raero , the AMRAAM DLZ is displayed on the HUD in an unexpanded configuration. On the HUD the upper and lower range scale tics are displayed at their static locations and the radar range scale digital readout is displayed above the upper range scale tic. The remaining AMRAAM DLZ parameters (target range caret, Raero , Ropt , Rpi , Rtr , and Rmin ) are positioned relative to the upper range scale tic which represents the current radar range scale value and the lower tic that represents zero range.
2) Expanded AMRAAM DLZ Scale: The AMRAAM DLZ transitions to the expanded scale when the target range is less than or equal to 125% of Raero. The upper and lower range scale tics and the radar range scale are removed from the HUD when the DLZ transitions to the expanded scale. The upper boundary of the expanded range scale on the HUD is dynamic and represents 125% of Raero. All DLZ parameters are positioned proportionally to the value of the range scale. However, as target range decreases below 125% of Raero, the Raero triangle is always displayed at 80% of the DLZ scale range.
Me parece que el fallo del que hablas lo han arreglado. 
|
CONECTAR
-
REGÍSTRATE
MERISTATION
BLOGS
MERCADILLO
MERITV
)
) permiten guiar a varios misiles a la vez, por lo menos a 4. En FF puedes comprobar en los manuales de FF4 y FF5 (p. 168) como ha cambiado la situacion y lo que no se podía hacer en FF4, ahora se puede cambiando el "ID" de cada misil (canal del data link) antes de lanzarlo. Cuando leí esto me pareció una mecánica un poco rebuscada, y efectivamente he encontrado a 