SAM won't fire

[Supernova-III]

This mission shows that the "Buk" SAM doesn't fire at jets that are inside the engagement zone. The placement is fine, but it just doesn't work. Same about S-300 -- it fires only when you fly within 30nm range. 

Buk test.miz

UPD:I made an even more absurd setup - AD is sleeping: sam doesn't work.miz

Edited October 12 by Supernova-III

[CatPaw]

Try adding 2 or more launchers for the SA-6. I Had the same issue making my own missions. Adding more launchers fixed it for some reason. 

if they are in the same group only one of the launchers will operate and the rest will just sit idle.

 

Edited October 11 by CatPaw
Clarity

[Supernova-III]

8 hours ago, CatPaw said:

Try adding 2 or more launchers for the SA-6. I Had the same issue making my own missions. Adding more launchers fixed it for some reason. 

if they are in the same group only one of the launchers will operate and the rest will just sit idle.

 

Added 3 more launchers. Didn't help

[Supernova-III]

I mean, it doesn't make any sense. How to make SAM working?null

[Ironhand]

It matters whether the target is approaching, crossing, or receding when talking about a SAM's engagement zone. Most of the time, the target aircraft were crossing at the outside edge of the zone. So, although it prepared to launch, it didn't because they remained just outside the missile's max range for their altitude and aspect. Changing the aircraft's approach a bit, yielded a launch when the ranged closed to approximately 38 km.

Mission attached. I had altered the SAM unit placements but that really made no difference. All that needed to change was to reroute the target aircraft a bit.

EDIT: Just added TRK file (BUK-Test-Mach) showing how much sooner the BUK launches, if the target is traveling faster--M1.3 rather than .5 or .6.

Supernove-III_Buk test-Ironhamd.mizBUK-Test-Mach.trk

Edited October 14 by Ironhand
Correct misspelling after adding TRK file