Difference between revisions of "SW Hyperspace Travel Times"
Line 53: | Line 53: | ||
|-style="background:ghostwhite;" | |-style="background:ghostwhite;" | ||
| Opposing Quadrant || [[Image:Difficulty-die.png|18px]][[Image:Difficulty-die.png|18px]][[Image:Difficulty-die.png|18px]][[Image:Difficulty-die.png|18px]] || 18 turns || 504 hours (3 weeks) || 9 | | Opposing Quadrant || [[Image:Difficulty-die.png|18px]][[Image:Difficulty-die.png|18px]][[Image:Difficulty-die.png|18px]][[Image:Difficulty-die.png|18px]] || 18 turns || 504 hours (3 weeks) || 9 | ||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
* '''Time to Calculate:''' The actual time it takes to make the calculations can vary depending on the distance involved, running and rerunning travel scenarios based on the galactic astroscape as contained in the navcomp. The further the distance, the longer this cascade of projected routes takes. | * '''Time to Calculate:''' The actual time it takes to make the calculations can vary depending on the distance involved, running and rerunning travel scenarios based on the galactic astroscape as contained in the navcomp. The further the distance, the longer this cascade of projected routes takes. | ||
Line 67: | Line 63: | ||
===Results=== | ===Results=== | ||
One [[Image:Success-result.png|18px]] is required to accomplish the task in the base time, arriving 10 minutes flight from the target destination,. Other results can be spent as follows: | One [[Image:Success-result.png|18px]] is required to accomplish the task in the base time, arriving 10 minutes flight from the target destination,. Other results can be spent as follows: | ||
− | |||
{| border="0" cellpadding="5" align="center" width="600 px" style="text-align: left;" | {| border="0" cellpadding="5" align="center" width="600 px" style="text-align: left;" | ||
|-style="background:black; color:white" | |-style="background:black; color:white" | ||
Line 90: | Line 85: | ||
| [[Image:Despair-result.png|18px|center]][[Image:Despair-result.png|18px|center]] || • One of the drop-outs is disastrous: the ship drops out of hyperspace too late and impacts with some part of a planet or phenomenon - even appearing in a simple atmosphere can be disastrous. The ship suffers a Critical Hit at +30 to the roll. | | [[Image:Despair-result.png|18px|center]][[Image:Despair-result.png|18px|center]] || • One of the drop-outs is disastrous: the ship drops out of hyperspace too late and impacts with some part of a planet or phenomenon - even appearing in a simple atmosphere can be disastrous. The ship suffers a Critical Hit at +30 to the roll. | ||
|} | |} | ||
+ | ==Hyperspace Routes== | ||
+ | Astrogation along one of the main hyperspace routes is very different from calculating hyperspace travel vectors along minor or even entirely new routes. Hyperspace interaction has a cumulative effect - the more vessels travel along a given route in hyperspace, the smoother and even faster that travel becomes. The five hyperspace routes of the known galaxy are so often traveled that they have dramatically smoothed the process of both calculation and travel along them. | ||
− | + | Generally speaking, astrogators perform one set of calculations to get to a major hyperspace route, another to calculate their travel along it, and then a third set from their drop-out point along the route to wherever their final destination lies. This turns what might normally be a long and arduous cross-galactic journey into a series of much more reasonable jaunts. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 15:40, 31 January 2017
Astrogation
Intellect (Astrogation)
Astrogation involves the use of a navcomputer to plot a hyperspace course. The calculations involved are insanely complicated, and require an up-to-date set of charts.
- The distance being traveled sets the Difficulty, time to calculate, and base duration of the trip (and number of jumps taken during the trip).
- The Astrometrics Record: Ships docking in a space port are permitted an exchange of astrometrics data with the spaceport systems, downloading their information to the port (giving the port up to date data on where they've been) in exchange for uploading the port's compiled astrometics information. The downside of this, of course, is that this registers (by transponder identity) each ship's arrival and previous travels with the spaceport in question.
Modifiers
Modifier Descriptions
- Astrometrics Out of Date: For each step that a ship's astrometrics record is out of date, upgrade the Difficulty of the astrogation check once. Not having an up-to-date record makes it harder to perform accurate calculations to avoid the hazards of hyperspace travel. These penalties are negated by receiving an updated set of astrometrics, most commonly done at a spaceport.
- High Stress during Calculations: Any high stress situation makes it easier to make mistakes, upgrading the Difficulty of the check.
- Hyperspace Routes: Destinations and starting points that are along hyperspace routes make the calculations easier - those points in space are more judiciously recorded, after all. Conversely, those that are far from any established routes are less likely to have all variables accounted for.
- Ship Damage: Astrogation calculations including risk assessments for bringing a ship near a hyperspace phenomenon. Undamaged ships can take risks that a navcomputer might rule are too risky for a damaged ship to take, making the calculations more difficult.
- Arrival Points: Where the astrogator wishes to emerge from hyperspace relative to their destination can make the calculations more or less difficult.
- Edge of system: The ship arrives at the edge of the system in question. This can take 1d10 hours to reach the destination or so, but making a system's-edge jump can be a good way to approach stealthily and/or with ample time to run full scans on the system as a whole.
- An hour out: The ship arrives quite a distance away (often closer to the planet's nearest neighbor than the planet itself). The destination is some distance out, with plenty of time to scan the arrival point.
- Ten minutes out: No Modifiers. The ship arrives ten minutes from the destination point.
- Five minutes out: The world is clearly visible, though a short distance away.
- Lunary orbit: The ship arrives within easy sight of the planet in question, right around the lunary sphere (area where most moons orbit a planet).
- In orbit: The ship arrives at the edge of the planet's gravity well, and is immediately coasted into its orbit. Pilot must make a Piloting check, (Dif 3) or take 3 System Strain.
- In atmosphere: A dangerous and unpredictable trick, this puts the ship into the atmosphere of the planet in question, effectively aiming for hyperspace breach inside of the world's gravity shadow. Upon arrival, the ship takes 1 System Strain for every Silhouette level it has, and the pilot must make a Pilot check (with a Difficulty equal to his vessel's Silhouette -1) to avoid taking an immediate Critical Hit.
Difficulty
- Time to Calculate: The actual time it takes to make the calculations can vary depending on the distance involved, running and rerunning travel scenarios based on the galactic astroscape as contained in the navcomp. The further the distance, the longer this cascade of projected routes takes.
- Trip Duration: This is the time the travel from origin point to destination takes along the calculated route. This duration assumes travel via little-known or even entirely new routes. Travel along hyperspace routes can significantly reduce this time.
- Number of Jumps: Even when a relatively safe route has been calculated, the drift of celestial bodies or other deep space phenomena frequently cause ships to be pulled out of hyperspace by their navcomps, preventing collisions and interactions that might destroy the vessel.
- Such instances are usually in uninhabited or remote systems, or in deep space between systems, as data for such locations rarely shows up on astrometrics, making it harder to account for them in calculations.
- When a ship drops out of hyperspace, it frequently takes a short time (2d10 + 10 minutes) in sublight speed to realign past whatever it was that caused the drop-out and to get back on track.
- Such encounters are usually uneventful, providing a quick look at a rarely-visited or even entirely undiscovered system before a leap back to hyperspace, but those moments of maneuvering have also been the cause of significant danger for vessels, as pirates, slavers, mynocks or other dangers spring in that moment. The phenomena that cause the drop-out can also prove a danger that needs to be escaped, as well.
Results
One is required to accomplish the task in the base time, arriving 10 minutes flight from the target destination,. Other results can be spent as follows:
Hyperspace Routes
Astrogation along one of the main hyperspace routes is very different from calculating hyperspace travel vectors along minor or even entirely new routes. Hyperspace interaction has a cumulative effect - the more vessels travel along a given route in hyperspace, the smoother and even faster that travel becomes. The five hyperspace routes of the known galaxy are so often traveled that they have dramatically smoothed the process of both calculation and travel along them.
Generally speaking, astrogators perform one set of calculations to get to a major hyperspace route, another to calculate their travel along it, and then a third set from their drop-out point along the route to wherever their final destination lies. This turns what might normally be a long and arduous cross-galactic journey into a series of much more reasonable jaunts.