FEATURE: Engagement range polygons
thebgpikester opened this issue · 2 comments
International and maritime borders often define when a SAM engages rather than a certain lethality distance. It's especially difficult to handle coastal SAM's that are engaging beyond the 12nm maritime range. I'd like to see a polygon zone as an overall engagement zone first, then the sam lethal range after.
I am planing on advanced Go Live Options for the IADS, see:
https://github.com/walder/Skynet-IADS/projects/1#card-41230405
This should also allow mission designers to include a polygon zone. However once the SAM is live, it will just shoot at whatever it feels like. This is due to the limited functionality of the scripting engine.
Are you using Skynet in a mission?
Yes. That template of the entire Syrian map you liked :)
This is how it occurred to me to be useful. The specific SAM's come on and go off according to - where the plane is found to be by the EWR's.
So, what I'm suggesting is that not only do SAM's check for closest, but also check after wards if the target is in Polygon Zone every detection cycle.
The reason should be obvious when you look at a map....An SA-10 has great range, but if the SA10 is the nearest to the plane and the other criteria are met, it will happily fire at planes in other coutries. What you want is for the SAM's to only consider their own border territories when going live.