Jonathan_S wrote:Finally reading this thread and chiming in, as I got the book from the library a couple days ago and just finished it.
Welcome to the joys of joining a months-old discussion... happened to me a month ago.
I agree that Galton should have had recon drones equipped with graser heads. (Even if they were just their Beta drones; with very stealthy impeller drives). Not only because of the endurance issue you mentioned for Galton having pulled off Oyster Bay, but also we're explicitly told that to scale them down into Cataphract Galton's designers had to reduce the power of the graser.
Oh, endurance. Here's another question: do the Hastas have the endurance that Oyster Bay did take? Manticore knows exactly what transition was the prelude to the attack and the attack itself down to the millisecond. That was about two months apart.
If the Hastas don't have that endurance, then either they had to be carried by stealth ships that weren't seen on Galton or they weren't the weapons used in the attack.
I expect that when the analysists back at the various navies' Admiralties or R&D divisions start comparing the data from the fighting at Galton with the sensor readings Manticore got from Oyster Bay that they'll pretty quickly spot that reduced power level, and resulting lower than expected damage.
Another good point and a VERY telling one. The RMN has very precise measurements of the power levels of both events. One could argue that the prototype weapons deployed for OB were massively overpowered and thus not something that could be done in a volume fashion, but I don't buy it. They worked just fine when firing and they had lasted several months while in transit.
One more thing now: the MAlign did ship graserheads from Galton (presumably, to a blackhole) just so that there was a record of weapons being delivered in time to be used in Oyster Bay... but the specs on those weapons that were shipped won't match what got used. There will be no doubt that the documentation found in Galton has been doctored.
There were a few other things that jumped out at me. I didn't like the scene where the name Bolthole was almost shared with the Ghost Hunters. First it was pretty damned sloppy to start to use that name outside of the most cleared circles; but second because they compounded the error by needlessly giving away that the alliance R&D was collocated with an major industrial base/shipyard in a secret system (by saying that the hypothesized secret system with the MAlign/Other Guy's industrial base and shipyard was their counterpart to the partly named location, "Bo-", where alliance R&D was located) If they'd kept that to themselves all the Ghost Hunters (and hence the League) would know is the GA has an big R&D center that someone started referring to as "Bo-".
I didn't like it when I read the book, but now that you've mentioned it and with a month of hindsight, it occurs to me that it may not have been sloppy, but intentional. The GA intelligence services knew about Bolthole by name, for a long time before even Tourville came calling and delivered a bunch of ships with dedication plaques saying "Built at Bolthole, 1919 PD." They knew that because those ships were being built somewhere that they couldn't find. Anyone in the Solarian League intelligence services who cared to pay attention to the war, even retroactively, would know that too. And the Ghost Hunters definitely fit in to this category.
I don't think the name "Bolthole" is classified. Like codenames, they don't give much information if accidentally leaked, but they do allow those who do know about it to know what they're talking about. Of course, someone can pretend to be in the information classification loop by knowing the appropriate codenames...
What that conversation did was to confirm that such a research centre did exist and the GA won't be telling the Sollies, even the good friends from the Ghost Hunters, where that is just yet.
And finally I was bothered by the short system sensor detection range that was used as the basis for the high speed scouting run. Honor says that the Manticoran system sensors can pick up a hyper transit at 2.5 lightweeks and so the scouts trying to confirm El Dorado (Galton) will aim to drop out at 3 lightweeks.
But multiple previous books (SftS, MoH, and SoV) show that the Manticoran system can detect even sneaky low energy transits at light months! And in fact the Sharks sneaking in for Oyster Bay were detected at one light-month, and the DesDiv 265.2 “the Silver Cepheids" showed up and closely searched that area a light-month from Manticore. (It's just that the spider drive let them clear the area without being tracked; whereas it's implied that a wedge, presumably even a low power stealthed one, would have been seen or tracked)
And all it would have taken to fix this is to extend the internal timeline of the book. Rather than planning to hit El Dorado within a few months, stretch it out to, say, a year. That doesn't have to make the book any longer, just change some dates to allow more time for the survey to drop out further away and a longer wait for the Ghost Riders to make their closer pass.
I made the same comment before, though I don't know on which thread.
We know the time it took for the hyper emergence footprint to travel to Manticore's sensor net: 12 hours. Given it was on the alpha band, that's a 31 light-day transit. Now, maybe I'm mis-remembering and 12 hours is not the time for the signal, but the time until the ready-Ddron appeared. But the destroyers wouldn't have travelled in the alpha band all the way. I've just quickly calculated for the bands from Alpha to Epsilon and, assuming a 15-minute delay between transitions both going up and down ((2n-1) * 15 min total, where n is the band number) and assuming the squadron was ready to go, Gamma provides the optimum travel time compared to distance covered: they'd cover 25.95 light-days. If it's a half-hour between transitions, then Beta is better, covering 23.94 light-days.
Either way, any numbers I run come up with more than 3 light-weeks.