SEAD a/c continue attacking dead radars

[BDukes]

Some of the firing issues on precise location I think might be related to RoE.

It also forces a little recon to be done. Whether satellite or other means. In scenarios I build for myself, I never use autodetect for combat units. There are a lot of unintended consequences that can happen.

Flicking autodetect on and off is the most common suggestion if you don't want to use satellites.

I put a report in on the autodetect thing. The autodetect routine is separate from the normal detection pipeline, and there is at least one case where it may not be called when actively editing and testing something in the same session. You've got to save and then restart the scenario or reinitiate the autodetect function by flicking it on and off.

Think having a priority function/UI similar to the strike missions would probably help. An attack non-emitting targets WRA might help too.

Mike

[thewood1]

There used to be a number of autodetect issues starting back with CMNAO. Most of the ones I saw have been eventually addressed ad hoc. The entire autodetect process should probably get a good once over. One thing I'd like to see is even if autodetect is enabled, show how its showing up in the contact list of a unit.

[boogabooga]

In my opinion this is not a matter of AI, but a matter of Radars and SAMs have the same WRA classification and having the radars on the same unit as the launchers.

In SEAD missions there are BOL launched HARMs against the "pre planned" possition of SAM sites. SEAD means supression, and for supression you'll need to fire HARMS to prevent radars to emit. In a SEAD mission as state you don't want to kill the radar, you want to supress it in order to open a time window for the strike package not be engaged for the enemy, and for that you need HARMS on air.

This is what the current CMO manual says about the SEAD mission on page 216:

SEADMission216.PNG (324.48 KiB) Viewed 344 times

Search and engage targets emitting radar. That's it. Nothing about prevention, suppression, or automatic BOL.

All I want is for the AI to do what it says on the tin. The player can handle the other stuff themselves or script it in.

I'm not arguing that the other stuff is not a thing, it's just in the domain where the human player plays and not for the mission-level AI.

If that really is the case, then is there a way to make a SEAD patrol so that a/c do not waste missiles on targets whose radars have been destroyed? Because as it is, SEAD missions are useless if there are multiple SAMs to deal with.

I'm afraid the best way is deactivating the mission once the radars are destroyed.

Actually, you could toggle the SAM site to be a decoy once you think that the FC radar is destroyed. I'm finding that to be an effective way to restore the desired behavior.

[thewood1]

Other than the issue with autodetect, it seems to do that.