I've recently noticed a bug as I was working on my campaign. I don't know if it is a known bug, as I've been away for a while. I'm concerned that it may cross over to the C# Aurora, so I thought I'd report it.
This is the situation: Race A is defending a planet against a missile attack from Race B. Race B's missiles are size 5. Race A detects the incoming missiles at approximately 40,000,000 kilometers on thermal sensors. Race A's best planet-based anti-missile sensor has a maximum detection range of 37,000,000 kilometers, but of course, since size 5 missiles are much smaller than 50 tons (resolution 1), the incoming missiles don't get detected by active sensors until they are around 4,000,000 kilometers away. Once they've been detected by active sensors Race A's planet based missile defenses can begin launching AMM's. All good so far.
The glitch, if it is one, comes after the leading edge of the incoming missile wave is detected by the planet-based sensors. Race A's PDC's will begin launching against the closest of Race B's missiles, as they should, but then they will go on to launch against all other missiles within their programed engagement range, whether the missiles have been detected by active sensors or just thermal sensors.
This is certainly a help to the defense, as they immediately gain defense-in-depth, but given the defenses were unable to engage the incoming missiles until the leading edge of the missile stream was detected on active sensors, why then can the rest of the missiles be engaged whether they've been detected on actives or thermal?
Kurt