|
Zathred -> Intelligent SAM Operator Example 3: Something Nasty Coming This Way (11/24/2019 1:12:40 PM)
|
Intelligent SAM Operator Example 3: Something Nasty Coming This Way
This is the final posting in this series of examples about using LUA to provide non-player SAM operators with more intelligent AI behaviour:
Example 1: https://www.matrixgames.com/forums/tm.asp?m=4716062
Example 2: https://www.matrixgames.com/forums/tm.asp?m=4716975
The example extends example 2 to add the following AI logic:
- When a missile is detected within the SA-12 MEZ the course heading of the missile is compared to the bearing of the SA-12. If the missile heading is within a 30 degree cone centred on the SA-12 then it is assumed the SA-12 is the target and it shuts down active radar. If the missile heading is outside of this limit then it is assumed the target is not the SA-12 and it remains active and engages the missile contact subject to the normal engagement conditions.
- A group has been created using the SA-15 which adds an SA-22 Pantsir short-range SAM/AA unit. The SA-15 doctrine changes are extended to the group allowing multiple units to be controlled with a single LUA ScenEdit_SetEMCOM() call.
Note there are specific changes to the doctrine for the SA-12 from example 2 to implement this behaviour:
- The “Ignore EMCON while under attack” is set to YES.
- The WRA is set to enable the use of the SA-12 missiles against incoming guided weapons.
- The HOLD doctrine for Air contacts is now used in the Lua code to supress use of the SA-12 missiles when the Grill Pan FCR is shut down.
Example Scenario
In the test scenario we send a BLUE flight of x2 A-6 Intruders into the RED air defence zone and launch an AGM-45 Shrike at the Bill Board radar which the SA-12 will attempt to shoot down. We then fire Shrikes at the SA-12 itself which in response shuts down and lets the SA-15/22 engage the Shrikes at close range.
1. Load the scenario in the Scenario Editor so you can see what’s going on behind the scenes.
2. Enter as BLUE and pause the sim.
3. Select the A-6 flight (Flight 267) and plot a course so the A6s end up by the coast about 20m miles directly south of the Bill Board radar within Shrike range.
4. Switch to RED and select the SA-12 unit. Note that the radar is currently set as inactive in the EMCON doctrine and the Sensors window shows the radar is inactive. The SA-15 group radars are also inactive as is the OECM on the Krasuha ELINT.
5. Unpause the SIM.
As the A-6 flight enters the “SA-12 Zone” exclusion zone it is marked as Unfriendly by the zone rules. There is no change to the EMCON status of the SA-12, SA-15 group and Krasuha units.
Shortly after the flight moves within 45nm of the SA-12 unit the “SA-12 Range Check” event action will switch the SA-12 Grill pan FCR radar to active mode and the Krasuha OECM to active. At this time the SA-15 group radars are still inactive.
- Wait until the A6s are due south and within Shrike AGM range of the Bill Board Radar.
- Pause the sim and manually (shift-F1) fire a single Shrike at the Bill Board Radar.
- Switch to RED and unpause the sim.
Shortly after the incoming Shrike is detected by the RED side the SA-12 will attempt to destroy the Shrike.
Once the initial Shrike is destroyed or hits its target fire all the remaining Shrikes at the SA-12 itself. As in example 2, the SA-12 will shut down and let the SA15/22 units attempt to shoot down the incoming missiles. If a missile gets through it usually misses the SA-12 by over 1000ft due to the inactive radar preventing the Shrikes from guiding to the target.
Notes
Collective responsibility is OFF for both sides to prevent units being automatically marked as hostile and then being fired upon.
We deliberately set the SA-12 Air doctrine to HOLD to prevent it from firing SAMs when the FCR is passive due to the known defect which allows missile firing and guidance without the FCR radar: https://www.matrixgames.com/forums/tm.asp?m=4719666
|
|
|
|
