From: Somewhere deep in appalachian valley in PA
Practicing "Pealing the Onion" tutorial scenario.
1) I have 2 radar and 2 SAM targets for my 2 F-18s, each with 2 HARM and 2 cluster bmob. all radars and SAMs are fixed.
First, I wish to make first F18 to use cluster bomb on radar 1, then launch 2 harm missiles against SAM 1.
Second, I wish to make second F18 to use cluster bomb on radar 2, then launch 2 harm missiles against SAM 2.
To do this, first I set "SEAD patrol" including total 4 targets in the zone. When they take off, I used manual target command to allocate weapons to each target. I first allocated clusters to radar target, then I allocated HARMs to SAMs.
However, unlike my plan, both airplanes launched HARMs to SAMs first. Then, due to lack of fuel, they abort the mission and head back to base... Radars were placed close to friendly base than SAMs. So, if they'd hit radar first, they could hit both targets. I thought the strike order from manual target command will override the target allocation order by "SEAD patrol" but it seems it is not...
So I tried "Land Strike" mission this time. But it was the same. They both prioritized SAM first (with HARM) then head back to base due to lack of fuel...
It seems that my attempt to automate strike, with my target priority, is not working. So... should I need to micromanage both F18s in this case? Launch each F18 without mission, use F3 to guide their path and target the radar with cluster bomb and wait until they hit, then target the SAM with HARM?
Are there any automated way to conduct this kind of ground strike procedure? Because, in the future if the strike package become bigger, it wouldn't be possible to micromanage all strike planes like that...
2) SLAM strike against SAMs from F18.
As far as I know, SLAM does not need the terminal guidance. It needs datalink from launcher plane for GPS, but terminal is thermal(IR) guidance, right?
I have 4 F18s, let them loiter behind SAM range using AAW patrol from 36000 ft. Then I select one F18, ordered him "manually engage target" to one SAM battery using 2 SLAMs.
The plane lowered the altitude very low, which was good and tactical, and then he launched 2 SLAMs. After datalink, I thought F18 would turn his head to opposite side of SAM. However, even after datalink is over, he fly to the SAM and fly over it. Later he shot down by MANPAD. To prevent this, I had to use F3 to manually turn this head to opposite direction.
How can I make him automatically turn after SLAM's datalink is over? Do I need to choose "crank and drag"? (For this particular scenario, it seems that scenario designer locked the option as crank only)
3) In general, what is the best way to perform SEAD/DEAD before strike target? Do you micromanage every SEAD/DEAD? Or land strike mission? Or SEAD patrol or anti-ground patrol?
< Message edited by exsonic01 -- 3/17/2020 4:31:22 AM >