Brigade XO wrote:What is the passive range of the missile's sensors for target acquisition? Passive range when the the power for the missiles wedge is not running? Also in the ballistic phase, are they going to be receiving targeting updates or is there no practical communication that can get to them?
I don't see why they wouldn't be scanning in any portion of the flight, ballistic or powered, or stop receiving telemetry at all. The missiles don't power down completely. They shut down the wedge, but the electronics inside are still powered. The missile has enough power in its capacitors to relight the third stage of the wedge, after all. And besides, when the warhead fires, it's dropped the wedge, so it has to have sensor technology that is independent of the wedge
What is the active sensor range? I presume that when the final stage lights off, the missiles targeting sensors also come back....but are they "active" meaning sending out something to get a return like you do with radar or are they passive- so they don't scream their locations such that CMs and energy weapons can track and home in on them?
Active targetting sensors from over 35 million km out? A three-stage MDM flies 29.2 million km in the first 6 minutes and 36.5 in the final three. That means the missile is actually closer to the launching ship than it is to its target, if it is going to need a ballistic phase. If it can receive useful telemetry up to 50 million km out from the launching ship, it can do that during the entire ballistic phase.
I suppose there's some technology that only works in the presence of an active wedge or impeller ring. For example, if FTL gravitic sensors are tied to those, then the missile flies blind in the gravitic spectrum during the ballistic phase. It would still have EM spectrum sensors, but those are limited to light-speed. I don't think the speed itself is the issue, but it may correlate to sensing accuracy. That is, an FTL gravitic sensor can resolve at 62 light-seconds what an EM light-speed sensor can resolve at most at 1 light-second away. That would be the difference between true targets and a tiny dot for the entire enemy's formation.
I still don't think it should miss a fleet of 100 ships moving in formation from 2 light-minutes away. So they are going to come crashing down on the enemy. The only question is whether they target the ships that they were meant to target, or whether they expend themselves on the screen and on decoys.
If Apollo isn't involved with FTL, at what point do the RMN missiles outrun the ability of the launching ships to send them practical targeting information and have to depend on the on-board sensors? Because if you have Apollo, the FTL command missiles and particularly one or more Ghost Rider drones further down range and on the targets, the missiles are getting essentialy real-time updating.
As we saw in both Spindle and Beowulf, a great deal of the Apollo brood's capability is the ACM itself: dedicating 11.1% of your birds to computing exclusively and networking them together in a distributed mesh. The FTL is a near after-thought in that case. The launching ship may have bigger processing capabilities and better sensors, but it's also much further away and thus has a lower resolution. I suspect that the FTL component alone wouldn't have accounted for much.
We've been told that accuracy at long ranges was a problem. We've also seen frantic reprogramming of missile waves' ECM and ECCM based on the data acquired from prior waves (Hypatia). Those are definitely limited by range and light-speed. If you're shooting at an enemy 3 light-minutes out, the signal from that attack takes 3 minutes to reach you and another 3 minutes to reach the closest missile that is about to attack. That 6-minute delay is the interval between salvos that can be reprogrammed with feedback.