penny wrote:Anyway, thanks for the post! I had been meaning to ask what exactly causes the ripples in the HV. And I didn't know whether wedges cause a flare. Which is a moot point inside a black hole upon its local frame of reference. And the LD, surrounded by its black hole, would not be speeding through the system causing a gravitational 'wake.' It will tip toe like a typical Arachnid does. The black hole that surrounds the LD will gobble up any grav waves and light in its local frame of reference. Anything outside the LDs frame of reference is irrelevant. It reminds me of what a cowboy does when he erases his footprints in the sand.
BTW, is there a limit of the minimal amount of acceleration when exiting hyper? An LD should be able to coast in? Wait! How does a ship enter n-space? By simply shutting off the hyper generator? If so, an LD does not have to have any velocity.
Technically we only know that certain artificial gravity sources (wedges, sails, and grav-coms) create the ripple, allowing them to be seen and tracked FTL. We don't know whether natural sources do.
My personal suspicion is that it is the change in gravity, the changing curve in spacetime, that bends the alpha wall and creates ripples. Most natural object probably don't have a fast or powerful enough change in their gravity to cause much (if any) signal. If my thought is true even a super Jupiter wouldn't cause much of an FTL signal because the curve of spacetime around it, while 'steep' isn't changing quickly.
A wedge is both powerful, and acceleration, so constantly changing the curve of local spacetime. If all that supposition is correct then creating a large black hole would cause a very powerful ripple -- as it'd create a strong and nearly instant new curve in spacetime (and if you unmade it somehome moments later that would likely cause another large signal as spacetime rapidly reverts to where it ways)
But anyway, on to your main question. Ships don't have to be accelerating at all when they transition - they don't even need to have velocity on them. The quote about the Sharks from a day to so back said they'd slowed to as close as they could to zero velocity before translating out of hyper.
Now, we're told that it is gentler and a little safer to translate into hyper while under acceleration. But there's no need to. You could be lying doggo with just your hyper generator active and translate out before your drive even warmed up and came online.
Now entering or exiting hyper causes energy bleed - you lose a bunch of your velocity crossing the barrier (exact amount differs by hyper band -- check the speed by hyper band chart for details). The books imply that a lower velocity translation makes a smaller flare -- and my assumption is that that's largely because less velocity got turned into energy that needs to be bled off. So if you're being stealthy you'd make your translation at slow as you can -- like the Sharks did. And while you'd probably have your wedge us, so you could quickly accelerate if you run into some unhappy surprise upon emergence, if you're being stealthy it'll be at about as low power as it can be (so reducing the drive's signal once you finish translating)
But if you're not trying to be especially stealthy, or you aren't waiting for a convoy scout to check the system out before the rest of the convoy emerges, you usually wouldn't waste the time to slow massively down before translating -- because letting the energy bleed do it for you saves time (even it if makes a bigger flare)
And to enter n-space you need to actively use your hyper generator to crack the alpha wall downwards. Simply turning it off does nothing. Otherwise Wayfarer wouldn't have been able to deploy shuttles and LACs in the Selker Rift in Silesia -- those all lack hyper generators. Also remember when Victor and Anton were delayed getting back from Mesa by the hyper-generator failure.
Torch of Freedom wrote:Less than an hour after they made their upward alpha translation, Andrew Artlett was completely and totally vindicated.
Mainly because they'd just made an unscheduled—and most unpleasant—downward translation.
"Congratulations, you stupid goofballs. The hyper generator is now officially defunct. We're damned lucky it lasted long enough for the failsafes to throw us back into n-space before the stabilizer went.
There were some discussions around that and as I recall (not taking the time to try to go find them) RFC said that if the failsafes detect a hyper generator is about to fail they have to make a split second decision based, mostly, on how close the hyperlog say they are to an inhabited system. If you're within, say, a month's sublight trip they'll trigger the emergency hyper translation (as happened to the
Hali Sowle). But if you're far away from inhabited systems then dumping you lightyears from safe harbor would just be a slow way of killing you -- so it makes the other choice and shuts it down stranding you in hyper. You then are stuck navigating to a system that can help and hoping to catch the attention of passing traffic who is willing to carry a message to the system authorities and/or rescue service saying you need assistance as you can't exit hyper!!