Jump to content

AGM-65D Mavs still won't ripple if they are on LAU-88


dezzled

Recommended Posts

Yeah, a couple issues are present. The missile step button is still cycling through every single missile instead of the two stations. That means that any tracking missile on a LAU is going to take backseat to another missile on the same LAU during the transition. But even with one AGM-65D on each LAU-88A/A in EO VIS stepping between the two missiles causes the unselected missile to be commanded back to boresight and drop track which obviously makes paired launches impossible.

The primary missile on each LAU should not be set at boresight but instead slaved to target. Stepping to the next station should not involve the missile slewing down from a central aiming to the target, it should already be there. In addition if one missile is tracking, stepping to another station should not interrupt its track. This applies to EO PRE VIS and BORE. The missiles once "slave broken" remain independent until AG is recycled or they are given an explicit return to bore command.

  • Like 1
Link to comment
Share on other sites

12 hours ago, dezzled said:

It only works for the LAU-117.

This is correct as per DCS F-16C Viper manual (page 297):

"Ripple Fire Up to two Mavericks can be queued with separate targets for a ripple fire (a.k.a. “quick-draw”) attack. When more than one Maverick is tracking a target, two 10-mr LOS circles will appear on the HUD, labeled “1” and “2”. The AGM-65s must be loaded on LAU-117 pylons for ripple fire to be available."

I will search is that same in RL.

Best regards,

falconbr

 

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

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