Jump to content

AI SEAD Flight Does not attack


Recommended Posts

If a flight is setup to attack an SA10 SAM site, the flight follows flight path ignoring set flight heights and fails to attack the site. Have tried this with F16c blk 52 and F18 lot 20 to no avail.

 

Test mission and track attached!

 

Thanks in advance

 

In latest OpenBeta patch as of 19/11/19

SEAD AI Test.trk

AI SEAD test.miz

Rig: MSI Mag X570 Tomahawk| AMD 5600 | 32 GB DDR3 | M2 NVME Gen4 1TB SSD | Samsung EVo 850 2TB, 500 & 256 GB SSD | Gigabyte AORUS GTX 1080Ti | Samsung 24" (1920x1200) |

2 x Iiyama 22" T2250MTS touch screen (1920x1080) | 2 x 6.4" LCD | Cougar MFDs | Thrustmaster Warthog | CH Pro Pedals | Windows 10

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I cannot look at the mission now, but try at the starting waypoint (WP 0):

 

 

Set Option : Reaction to Threat - Evade Fire

 

 

Also consider Restrict Jettison active

 

 

Default Reaction to Threat will have the AI try to hide from SAM's when in their radar range, so this is probably what your F-16's are doing. Evade fire will have the AI ignore threats unless they shoot at them.

 

 

Restrict jettison will keep the AI from ditching droptanks and AGM's when fired on.

 

 

Note that the HARM without PB mode isn't very capable against the SA-10. I suggest AGM-154 if you're not using them.

Awaiting: DCS F-15C

Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files

 

Link to comment
Share on other sites

Hi Exorcet

 

The test mission was setup as follows:

 

Set Options :

ROE = Weapon Free

Reaction to Threat = PASSIVE DEFENCE

Chaff - Flare = USE WHEN FLYING IN SAM WEZ

ECM Using = USE IF DETECTED OR LOCK BY RADAR

 

About 64 Miles from target SA10 WP action set to:

Attack Group = SA10 group

 

I have now tried options as you suggested, AI Flight behaviour same and ignores restrict Jettison option as well! Also tried F18 with AGM88s and AGM154s, same behaviour.

 

Thanks for the suggestions though!


Edited by nebuluski

Rig: MSI Mag X570 Tomahawk| AMD 5600 | 32 GB DDR3 | M2 NVME Gen4 1TB SSD | Samsung EVo 850 2TB, 500 & 256 GB SSD | Gigabyte AORUS GTX 1080Ti | Samsung 24" (1920x1200) |

2 x Iiyama 22" T2250MTS touch screen (1920x1080) | 2 x 6.4" LCD | Cougar MFDs | Thrustmaster Warthog | CH Pro Pedals | Windows 10

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

So if the SA10 is changed to an SA2 the flights do attack but at about 15 miles and from an altitude of about 4000 feet. So the AI SEAD flight is not flying at the altitudes set in the ME! Which appears to be a bug! Unless of course it is a feature.

 

Considering the AGM88 has a range greater than this and especially at higher altitudes.

Rig: MSI Mag X570 Tomahawk| AMD 5600 | 32 GB DDR3 | M2 NVME Gen4 1TB SSD | Samsung EVo 850 2TB, 500 & 256 GB SSD | Gigabyte AORUS GTX 1080Ti | Samsung 24" (1920x1200) |

2 x Iiyama 22" T2250MTS touch screen (1920x1080) | 2 x 6.4" LCD | Cougar MFDs | Thrustmaster Warthog | CH Pro Pedals | Windows 10

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I got it to work. Changes:

 

 

-Delete the default SEAD task (always delete default task unless you want it specifically)

-Gave flight more space to form up (if you don't do this the lead will stay low waiting for wingman)

-Reaction to Threat changed to Evade Fire

 

 

The F-16's climbed to about 25000 ft, shot their HARM's, and defeated the SA-10.

 

 

EDIT

 

 

I also want to point out, the default AI tasks start at WP0. Your F-16's takeoff close to the SA-10's large radar radius. I feel like compounding the problem was the AI going to task at WP0 because they detected the SA-10. This made them skip waypoints 1 and/or 2 possibly and not gain the options set or the attack group tasks. You can place options at WP0. I usually do this. Tasks and Enroute Tasks I usually place after WP0.

AI SEAD test 2.miz

AI SEAD Test.zip


Edited by Exorcet

Awaiting: DCS F-15C

Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files

 

Link to comment
Share on other sites

Cheers that was it just needed to push the steer points out as you say for the wingman to join up. Its quite finicky to get them to continue to climb though. They also insisted on diving when entering weapons engagement area/zone, the way around this was to replace ROE = WEAPONS FREE at an early steer point with ROE = DESIGNATED TARGET ONLY at the attack steer point.


Edited by nebuluski

Rig: MSI Mag X570 Tomahawk| AMD 5600 | 32 GB DDR3 | M2 NVME Gen4 1TB SSD | Samsung EVo 850 2TB, 500 & 256 GB SSD | Gigabyte AORUS GTX 1080Ti | Samsung 24" (1920x1200) |

2 x Iiyama 22" T2250MTS touch screen (1920x1080) | 2 x 6.4" LCD | Cougar MFDs | Thrustmaster Warthog | CH Pro Pedals | Windows 10

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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