Battle of Manticore

n7axw wrote:However it's done, Bachfish was on half pay for forty years. He might be an admiral, but I would imagine that activating him could be a complicated issue since he would have no inservice experience since War Maiden.

Don

I'm certian a "smart" Bupers wouldn't bring him back and throw him directly into combat commanding a BatCruRon, no matter what was his record or who were his patrons. I can see him being brought back first into an admin position (freeing up another Flag officer) to get his sealegs and allow Bupers to analyze his performance and current capabilities. Then a move into a planning position or a fleet staff position to integrate the current tech and tactics before being moved back into indepentant command.

With all the reserves being brought back, I'm sure there is a training program specifically to introduce the new, transformative techs (most of which wasn't fleetwide even at the end of the first war) and the tactics it allows.

Theemile wrote:

n7axw wrote:However it's done, Bachfish was on half pay for forty years. He might be an admiral, but I would imagine that activating him could be a complicated issue since he would have no inservice experience since War Maiden.
Don

I'm certian a "smart" Bupers wouldn't bring him back and throw him directly into combat commanding a BatCruRon, no matter what was his record or who were his patrons. I can see him being brought back first into an admin position (freeing up another Flag officer) to get his sealegs and allow Bupers to analyze his performance and current capabilities. Then a move into a planning position or a fleet staff position to integrate the current tech and tactics before being moved back into independent command.
...

If Backfisch is back in uniform, how about the fleet base command in Silesia under Mark Sarnow? The Star Empire has a good record of using flag officers for diplomacy; I would think he has pretty good "street credit" with the nearby Andermani at Saschen, and can hold an ONI/BuPlan admiral's slot in Silesia.

fallsfromtrees wrote:Lets do a little arithmetic here. 150Mkm is 500 light seconds, and for the FTL is about 8 seconds one way or a command loop of 16 seconds. I'm not sure that the Apollo system was designed to handle that large a command loop delay - yes the light speed systems would, as that corresponds to a range of about 2.4 Mkm, but Apollo maybe/maybe not.

It was pretty clearly stated to be a signal strength issue. You can see this back in HotQ, when you only have so far you can detect FTL transmissions. For that matter, you can only see a wedge to a certain range, as the signal fades into background it gets harder to detect.

kzt wrote:

fallsfromtrees wrote:Lets do a little arithmetic here. 150Mkm is 500 light seconds, and for the FTL is about 8 seconds one way or a command loop of 16 seconds. I'm not sure that the Apollo system was designed to handle that large a command loop delay - yes the light speed systems would, as that corresponds to a range of about 2.4 Mkm, but Apollo maybe/maybe not.

It was pretty clearly stated to be a signal strength issue. You can see this back in HotQ, when you only have so far you can detect FTL transmissions. For that matter, you can only see a wedge to a certain range, as the signal fades into background it gets harder to detect.

Yes but the actual transmission radius given for the first generation drones was 4 light hours, and 150 Mkm is about 8 1/3 light minutes, well under the transmission radius of the drones. Even if the Apollo missile only had 1/10 of the capability of the FIRST generation RD, it would still be 24 light minutes, 3 times the distance required.

fallsfromtrees wrote:Lets do a little arithmetic here. 150Mkm is 500 light seconds, and for the FTL is about 8 seconds one way or a command loop of 16 seconds. I'm not sure that the Apollo system was designed to handle that large a command loop delay - yes the light speed systems would, as that corresponds to a range of about 2.4 Mkm, but Apollo maybe/maybe not.

kzt wrote:It was pretty clearly stated to be a signal strength issue. You can see this back in HotQ, when you only have so far you can detect FTL transmissions. For that matter, you can only see a wedge to a certain range, as the signal fades into background it gets harder to detect.

fallsfromtrees wrote:Yes but the actual transmission radius given for the first generation drones was 4 light hours, and 150 Mkm is about 8 1/3 light minutes, well under the transmission radius of the drones. Even if the Apollo missile only had 1/10 of the capability of the FIRST generation RD, it would still be 24 light minutes, 3 times the distance required.

Those early drones had pulses measured in seconds - current drones have to have a pulse rate >1/2 a megahertz to allow video transmition. It could be that (like radio) as the pulse frequencies have gone up, the output power has gone down (per pulse), limiting their useful distance.

Also, originally drones and ships used their drive nodes to create the pulses. As the pulse rate went up, a purpose built phased array was installed to create the pulses - obviously, this would be much less powerful than a ship's entire wedge at making the grav pulses, but allowed much higher bandwidth than the Honorverse equivalent of ELF radios.

So yeah, without beating to death the whole control channel issue again, yeah. Certainly seems to model what was going on.