Quote:
|
Originally Posted by LuftWolf
I should mention that there is a difference in engagement range for AEGIS vessels if they are able to detect the launch of the missile before it reaches its skimming trajectory or if they have a linking platform.
If their first warning of the incoming missile is the missile in its search phase, then they will engage the missile later than if they knew the missile on launch before it went low or had a link contact for the missile.
To be honest, I'm not exactly sure why this is, but it's not from the ESM detection, which there usually isn't until the missile gets much closer. Perhaps there is a delay in turning on the FC radars? The detection information from DBGViewer is a little confusing on this issue, and I can't figure out why.
Like I said in the readme, the simulation aspects of this will change, but for now, it behaves in a way that feels right, to me anyway, simulating reaction times and everything (even though that is a bit of an accident). :|\
|
OK, got DbgView up and running.
Launched 4 ASM from 20 miles out. E-2, DDG, and FFG all detected at launch.
ASMs enabled 10nm out. ESM contact was made, and missiles were identified hostile. Chaff was fired and a barage of SM-2 were launched. I'm not sure which stage they were fired at. A second volley, however, was required, resulting in one missile getting through.
As far as I can tell, even with Dbg, they are holding fire until the targets are classed hostile, and this does not occur until their seekers enable.