Jump to content

Recommended Posts

Posted (edited)

During squadron testing, we have discovered 2 bugs with the F-18 FLOOD mode:

 

1. FLOOD mode does not work until 5nm. This is incorrect according to the manual, which states a 10nm max range on FLOOD in terms of the missile guiding. If you launch outside 5nm, the missile will fly straight off the rail until the distance between the 2 fighters is around 5nm, at which point it begins FLOOD guidance. Inside 5nm, the missile guides as normal with one exception; even with the LOFT switch set to NORM, the missile still lofts off the rail, though it quickly corrects and impacts.

 

2. Even more problematic, however, is that the F/A-18 FLOOD does not give proper RWR warnings to the target aircraft. Although the missile may not be able to see the reflected returns past 10nm (RN it is 5nm), the RWR is able to "see" these signals further than the missile due to the radio waves having to travel only one direction. However, this isnt the case in DCS. In DCS currently, FLOOD shots outside 5nm, until the 5nm mark, give absolutely no RWR warning (nails, spike, or otherwise) even if the target aircraft is inside the FLOOD circle and within the stated 10nm range. Once the range hits 5nm, the result depends on the RWR; F-15 RWR only gives search nails even after hitting 5nm, and the F-16/18 RWRs will show an SARH launch as normal; however, the missile is already just seconds from impact. If the AIM-7 is supposed to detect reflected radar signals out to 10nm, there is absolutely no reason the RWR shouldn't be able to detect this PDI flood out to 10nm at the very least.

Shots inside 5nm have similar behavior to the last case above; F-15 RWR only gives search nails even while the missile is guiding, while the F-16/18 RWR behave as expected, giving RWR warning off the rail.

 

For 1, the expected behavior per the manual is that FLOOD should guide missiles out to 10nm, not just 5.

For 2, the expected behavior is that from at least 10nm the RWR should give at the very minimum a spike, and not nails only inside 5nm (F-15 RWR), or launch warning only inside 5nm (F-16/18 RWR).

 

Attached are 2 tracks: the track labeled (shooter) is from the PoV of the F-18 shooting the AIM-7s; the track labeled (target) is my PoV as the defender. The shots, in order, are

F-18 FLOOD vs F-16 RWR at 10nm,

F-18 FLOOD vs F-16 RWR at 5nm,

F-18 FLOOD  vs F-18 RWR at 10nm,

F-18 FLOOD vs F-18 RWR at 5nm,

F-18 FLOOD vs F-15 RWR at 10nm,

F-18 FLOOD vs F-15 RWR at 5nm.

 

 

F-18 FLOOD (shooter).trk

F-18 FLOOD (target).trk

Edited by dundun92

Eagle Enthusiast, Fresco Fan. Patiently waiting for the F-15E. Clicky F-15C when?

HP Z400 Workstation

Intel Xeon W3680 (i7-980X) OC'd to 4.0 GHz, EVGA GTX 1060 6GB SSC Gaming, 24 GB DDR3 RAM, 500GB Crucial MX500 SSD. Thrustmaster T16000M FCS HOTAS, DIY opentrack head-tracking. I upload DCS videos here https://www.youtube.com/channel/UC0-7L3Z5nJ-QUX5M7Dh1pGg

 

  • 2 weeks later...
Posted

The RWR should actually go off for anyone within the coverage area of the FLOOD cone, not just the target. This is true also for other types of guidances, but especially true for a mode such as FLOOD. I hope that this gets implemented correctly to avoid magic sensors.

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...