SharkHunter wrote:Distinctively the opposite of what I am thinking of. The necessity of putting the counter missiles between oncoming attack missiles combined with defending ships under maneuver make deploying a large enough globe of CMs at super-extended distances unwieldy if not impossible.
I'd want the "slow CM's" forming a disk as close to the ship's 'walls and unprotected spaces as I could possibly launch them in sequence, because an attack missile has maybe 1/10th of a second at high fractions of C before it's out of range. Keep in mind the ship knows where it is inside the wall and wedge, the attack missiles don't, so it doesn't require 100% coverage, just "attack angle coverage".
Either you have FTL RD's or you do not.
If you have FTL RD's you know how many incoming and exactly where the missiles are in real time. Well 62X c "real-time", or close enough as one gets. Therefore all CM's launched have homing solutions. Depending on what interval you place your FTL relay RD's to CM's, the time delay varies accordingly.
What is TRUE is that the further out one wishes to interdict the missiles, the total number of FTL RD's becomes a burden. Then again, you do not need an even globe. It is after all why you have scout FTL RD's. You know the threat axis. We know at 5000g, an RD can move ~6.5Mkm at a "typical" launch distance of 6minutes of flight. MDM's have 9minutes of flight, so you noticed I rounded down just for ease of manipulating numbers for a "rough" number.
Time required for an offensive missile to move 6.5Mkm laterally depends entirely upon ones assumptions of its throat opening angle. RFC has stated that the throat sensors must hold lock, must be pointed, at ships at all times. From wedge geometry pearls, a ships throat opening is about 60 degrees(+-30deg) and changes via differing acceleration states. Who knows what a missiles wedge angle is. Could be huge, or tiny in comparison. If 30 Degrees ability to create lateral distance of 6.5Mkm, an MDM would have to turn back toward its target ~160s, out.
You will note MDM's have 3 stages of 180s and I only used 2 stages of 180s of "time" for the RD's to react. This aligns perfectly with the calculated 30 degree change of vector of 160s. At a 160s out, this distance is equivalent to 30Mkm. Somehow I highly doubt they will even bother with CM's this long legged. The CM's effectively would have to be the same size as a DDM!
In short, RD's at only 5000g's, RMN RD's can accelerate faster than this but lose stealth, can easily shadow any delta dodge vector from the MDM. Therefore any long legged, even DDM, long legged CM's can be homed onto MDM's via FTL RD's
In short: You do not need a gigantic globe of RD's. You need a swarm of RD's at distinct intervals so the data transmitted to the CM's is only ~1s old, 2s old, etc depending on interval banding of the RD's talking to CM's in question. At 1s or 2s old "info", Cm's have very high interception rates.
***** Lets play SOLON *****
Ships hyper in on your rear 30,000,000km. Your ships only have a few RD's back there. They start rolling pods for a nice FAT salvo.
Takes em a ~4minutes(4*60/12*6)=120pods.
Flight time ~6minutes.
When they hyper in you see total number of point sources, you immediately launch RD's. They have 10,000gs accel without stealth, 5000g with stealth. How far out do they get? Will start by using the 4 minutes + 1st stage of MDM, or at current tech 1/2 drive time required to kill your ships.
D(5000g) = 1/2*5000*10*(4*60+180)^2
D(5000g) = 4.4Mkm
D(10,000g) = 8.8Mkm
Have time to spare, so in reality is around 6Mkm and 11Mkm respectively.
If pods are all tractored in across the hyper wall, wait for light speed data of your enemy(2min)
Drops to 2(60)+180 = 300s
D5000g = 2.25Mkm
Refine: as additional flight time remains. +280 = 400s
D5000g = 4Mkm
In short: Can have FTL RD CM vector information for current generation CM's at maximum range +++ even for a hyper in behind scenario like Solon.
*** Note I specifically rounded all numbers down that would help increase the FTL RD's ROP(radius of Operations) ***Simply using existing FTL RD's to broadcast using their light speed transmitters as CM vector middlemen is imminently feasible and practical under even harsh "surprise" situations like Solon. The only question is: Can ships carry enough RD's. Broadcasting vector information does not require didlee in bandwidth. One RD could effectively cover a sphere one light second in diameter for thousands of CM's with MDM vector data updates multiple times a second. Of course as soon as they do broadcast, they also become targets. Need overlapping redundancy, keeping the MDM's from knowing where data is coming from.
Lets do an RD count if 1 RD = 1 spherical ls.
Above, just got done analyzing that RD's can simply shadow MDM's. Thus a solid cone is not needed. Rather
RD #'s = (distance/Interval)*MDM/RDperMDM*Redundancy
Lets just say RDperMDM is 1RD/1000MDM, This is absurdly low, but hey, DW has monstorous computers, so why not purposely throw out basic radio bandwidth physics as well...
Interval = 1ls so oldest data is 1s old, so distance between RD's is 2ls, 600,000km.
Total number of shells required for current CM's is 3.75Mkm/600,000km = 6 shells.
So, if under 1000 missiles incoming, require 6 RD's for at worst, 1s old data and no redundancy.
This is easily doable.