Jonathan_S wrote:penny wrote:Also, after loitering, getting a g-torp back up to speed shouldn't take that much energy, IMO. It is already a slow missile. Almost as slow as an LD. I imagine a g-torp reaches its max acceleration very early after launch, so a restart after loitering shouldn't require any significant power, nor would there be a rush to get back up to speed.
It reaches it's max accel shortly after launch (it's capable of "few hundred gravities’ acceleration"). But it's so low an accel it'd spend a lot of time accelerating up to whatever max speed is used for an attack run.
And if you want it to slow down so it can loiter in a given area
it has to spend exactly as long slowing down. Spend 2 hours working up to about 21,000 KPS and you'll need to spend
another 2 hours to cancel out all that velocity it built up in the original acceleration.
So I partially agree with tlb. I don't think they'd have design a g-torp with enough extra energy to allow it to run its drive for over twice as long as a normal attack profile. They'd have given it
some margin to allow the drive to be brought back up for maneuvering if making very long range shots, but we're likely talking 10-15% extra time.
However since the drive can freely restart, and incorporate ballistic segments in its flight profile - the smart "AI" onboard should give plenty of flexibility to let a captain allocate the limited energy budge in more interesting ways than a continuous powered shot from whatever their design range was.
(Trading off energy lost to capacitor leakage rate against lower peak velocities from running the drive less.
So they should be free to:
* use 90% of its run time to build up velocity, and save 10% for terminal maneuvering.
* Or drop that down to, say, 80 or 85% run time and use the extra power saved by 5%-10% less engine runtime to cover the leakage drain during a nice long ballistic coast (and still have 10% left for terminal maneuvering).
* Or if they wanted to use, say 35% of its run time, then have a nice long coast, another 35% to slow down to loiter speed, have the extra power saved by using 20% less runtime to cover leakage drain during coast & loitering (and still have 10% left for terminal maneuvering)
And you can partially compensate for the lower max velocity by simply sneaking closer so the g-torp doesn't have as far to go after launch.
Note: You might also want a slow terminal speed if you need to get at a target that could be protected by the wedge block-ships seen at Beowulf.
You need your velocity low enough that the g-torps few hundred gravities of accel can pick its way through the gaps between the wedges (which might require a couple of near 90 degree turns to dogleg your way through -- and if you've too much velocity you hit the back wedge before you can change your vector enough to miss it). So you might want the flexibility to slow down even if you're not planning to loiter before attacking.
With this kind of flexibility a loiter attack wouldn't need to be a specific design goal -- and might still be somewhat possible anyway.