Talk:Jump Drive

From Traveller Wiki - Science-Fiction Adventure in the Far future
Jump to navigation Jump to search

Links (2020)[edit]

  1. On the Nature of Jumpspace
  2. Spenser TR's Random event tables – a week in Jumpspace
  3. David Jaques-Watson Jump space article
  4. David Jaques-Watson Jump Drive article
  5. CANON PROBLEM 1: Jump Torpedoes
  6. 'Fastest Spaceships in the Universe' Infographic Compares Real and Fictional Spacecrafts
  7. The Color of Jumpspace - Freelance Traveller
  8. Jump Sickness - Freelance Traveller
  9. The Implications of Jump Detectability - Freelance Traveller
  10. Starship Activities In Jumpspace - Freelance Traveller
  11. An Outline of Jump Physics - Freelance Traveller
  12. Jump Drive 100D limit - Peter Trevor
  13. Jump Drive operation - Peter Trevor

Links (2019)[edit]

  1. EXTERNAL LINK: I just had an a-ha! moment while working out combat for my group. The travel times given in Book 2 of the LBBs is for constant acceleration to the halfway point, then constant deceleration to the destination. But what if you're running for a jump point? Do you have to be stopped to enter jump, or can you enter jump having accelerated constantly from origination to the jump point (ie. moving as fast as blazes when you punch the big red button)?
  2. EXTERNAL LINK: So, a J-6 drive can make a 3 parsec jump, right? Can a J-1 make a... no parsec jump? Infrasystem Jump?
  3. EXTERNAL LINK: Article feedback request on FB / Focus Group
  4. EXTERNAL LINK: Is it possible to install a new jump drive, retrofit an old one, or otherwise improve it's performance?
  5. EXTERNAL LINK: Anyone know where the 168 +\- hours for a jump came from?
  6. EXTERNAL LINK: This may have been discussed in the past, but I am new here. Is there room in the Traveller rules for other types of FTL drives?
  7. EXTERNAL LINK: Jump always takes a week. Would it be possible to deliberately misjump and drop out earlier? I am thinking of in-system tactical scenarios.
  8. EXTERNAL LINK: So, first question, what happens if a ship is forced out of a jump mid jump? So someone sabotages the jump drive mid jump for example?
  9. EXTERNAL LINK: With a jump drive (or any FTL drive), can you travel fast enough to catch the first light that ever existed (assuming it survived)?
  10. EXTERNAL LINK: So... here's another question. Ship (A) for what ever reason clamps to ship (B). Can both ships now jump together? (Given enough fuel, working drives etc)?
- Maksim-Smelchak (talk) 11:19, 13 March 2019 (EDT)

Links (2017)[edit]

  1. EXTERNAL LINK: Just how much work does the J-drive do?
  2. EXTERNAL LINK: Can they make multiple jumps by siphoning fuel from their "cargo" tankage?
  3. EXTERNAL LINK: A-rating-plant
  4. EXTERNAL LINK: 'Fastest Spaceships in the Universe' Infographic Compares Real and Fictional Spacecrafts
  5. EXTERNAL LINK: For comparison, a Jump-1 starship can manage 170C through hyperspace...
  6. EXTERNAL LINK: Given that time in Jump is always stated as 168hrs + or - 10%, in YTU do you allow synchronised jumping of multiple starships, or do they arrive in dribs and drabs within the +-10%?
- Maksim-Smelchak (talk) 22:45, 28 April 2017 (EDT)

Links (2016)[edit]

  1. EXTERNAL LINK: Jump astrogation question
  3. EXTERNAL LINK: How long does it take to calculate a jump, please?
- Maksim-Smelchak (talk) 18:51, 18 December 2016 (EST)

Smelchak Notes (2017)[edit]

Jump Drive Travel Times

Jump Drive (FTL) Estimated Travel Times
Distance:	Jump-1	Jump-2	Jump-3	Jump-4	Jump-5	Jump-6
54 parsecs
(1 sector)	54 weeks
1 year	27 weeks
½ year 	18 weeks
4.5 months	14 weeks
3.5 months	11 weeks
2.75 months	9 weeks
2.25 months
108 parsecs
(2 sectors)	108 weeks
2 years	54 weeks
1 year	36 weeks
9 months	27 weeks
6.75 months	22 weeks
5.5 months	18 weeks
4.5 months
162 parsecs
(3 sectors)	162 weeks
3 years	81 weeks
1.5 years	54 weeks
1 year	41 weeks
10.25 months	33 weeks
8.25 months	27 weeks
6.75 months
216 parsecs
(4 sectors)	216 weeks
4 years	108 weeks
2 years	72 weeks
1.5 years	62 weeks
15.5 months	44 weeks
11 months	36 weeks
9 months
270 parsecs
(5 sectors)	270 weeks
5 years	135 weeks
2.5 years	90 weeks
22.5 months	68 weeks
17 months	54 weeks
1 year	45 weeks
11.25 months


Jump Duration:	1 week (168 hours +/- 10% variance)
Jump Velocity:	170.0c (+/- 20.0c variance)
Month (Time):	4 weeks (28 days by Imperial calendar)
Assumptions:	(Top efficiency, near-instantaneous refueling, no crew fatigue, etc.) 
Sector (Area):	(size of a sector in 2D parsecs x & y coordinates)
Galaxy (Area):	Milky Way Galaxy (estimated 55 kiloparsecs in diameter) (…over 1,000 years at J-1)

Must it be Lanthanum? (2016)[edit]

I heard of Vargr jump drives using Barium instead of Lanthanum. Is there a canon evidence of this? What are the differences, in functionem & in the rules?

No idea. Can ask around.
- Maksim-Smelchak (talk) 00:55, 6 August 2016 (EDT)

Hey, where did you hear that?
- Maksim-Smelchak (talk) 18:02, 6 August 2016 (EDT)

I believe it is in DGP:Starship Operators Manual - a comment made by the "Old Timer" in a textbox.
--WHULorigan (talk) 14:56, 8 August 2016 (EDT)

One can also use Zuchai Crystals. Atymes (talk) 19:50, 23 November 2018 (EST)

Yes. Other options too.

- Maksim-Smelchak (talk) 02:47, 24 November 2018 (EST)

Jump Drive Phenomena (2016)[edit]

How about some weird conjectures about the nature, color and solitude of jumpspace? Ghost ships, Winkles, ghost fleet, Lanth Abyss, relation if any to psionics, etc.

It's all unknown. Agent talks about some of it.
- Maksim-Smelchak (talk) 00:55, 6 August 2016 (EDT)

Droptanks? (2010)[edit]

Should some mention be made of droptanks, as a possibility (I suspect a GM may or may not allow them, or may allow them for part but not all of the fuel...)?

  • Allens 07:09, March 12, 2010 (UTC)

Style notes (2019)[edit]

These are a few style notes for the Jump timeline (which I'm excerpting from the Integrated Timeline:

  • I use data-sort-value="[date]" to force the sortable Date column to sort correctly.
  • I have the Date column right aligned to the end of the date, as opposed to the end of the text.
The <span style="color: transparent;">*</span> construction is a CSS kludge to make all of the numbers right-align, rather than right-aligning the full text whether the asterisk is present or not. Yuck.
  • In the Date column, I use the &minus; ("−") for dates instead of the hyphen ("-") because &minus; can only mean "negative", while a hyphen has multiple uses, including negative, compound word joiner, span, syllable break at the end of a line, etc.
I have also observed that &minus; always sticks to the number it's attached to, while hyphen is often (though not consistently) left behind on the preceding line.
(Note also that the Wikipedia Manual of Style requires the &mdash; ("—") in many cases, and a hyphen in other cases; compare Hyphens with Dashes.)
  • In the Culture column, Droyne and Ancients are listed separately, since the Ancients are a very small, limited subset of Droyne in the Ancients' era.
  • In the Details column, all sources are linked, even where that results in sources that are linked repeatedly.
  • It would be reasonable to add a fourth Sources column, but I have not done so. A better solution would be to use page citations, such as {{Page cite | name=Secret of the Ancients | page=42 | version=classic Traveller}}[1] , which for some reason doesn't
Steve98052 (talk) 04:42, 11 September 2019 (EDT)

Example reference list:

If you want to include the references inline in the table you should use Template:Ludography ref. This is the version used in the Template:Sources.
- Tjoneslo (talk) 07:05, 11 September 2019 (EDT)

Steve, you have my number. Ring me sometime and I'll walk you through the process.

  • Really appreciate what you do and your works really add to the site.
- Maksim-Smelchak (talk) 09:08, 11 September 2019 (EDT)

Jump drive damage[edit]

In a social media discussion, there was a question about what can go wrong with a Jump drive if it is damaged or neglected. My reply, quoted in full below, would be off-limits original research on Wikipedia, but might be a starting point for a new section of the article, or at least for a meta page.

I started from the premise that starship combat tables can produce results that include both "Jump drive disabled" and "Jump drive reduced in range" (as well as increasing risks of operation and no effect). If the Jump drive is a single monolithic device, damage would either disable it, increase risk, or not harm it.

To allow for the result of reduced range, I can think of a few possible causes that imply something about how it works:

1. Jump drives require immense amounts of hydrogen very rapidly. Damage to the liquid hydrogen tanks, pumps, pipes, and related equipment could reduce range if some of the hydrogen delivery systems were disabled, but some hydrogen delivery equipment remained operational due to the need for multiple sets of that equipment.

2. The Jump drive innards (that do whatever kicks a starship into Jump space in a way that it will return to normal space) are not a single grand device, but rather a collection of duplicate parts for which failure of a small number is normal (but demands eventual maintenance), failure of a larger number allows operation at reduced Jump range, and failure of an even larger number precludes safe operation, and failure beyond a certain point precludes Jump entirely.

3. The Jump drive includes some Jump analog to avionics, and some degree of damage allows operation at higher risk, reduced range, or both.

4. Self-check features in the equipment and the computing systems that support it may be overly cautious, so it might be possible to override them, such as in a combat where destruction is certain in the absence of a high-risk Jump.

Some sources state that in the early history of Jump technology, drive failures that crippled a starship, stranding it, were very common. That implies that in early Jump drives, there were no effective ways for partial redundancy of components to provide for operations after a major failure. Thus early starships would have to completely duplicate Jump drives to protect against getting stranded in travel between systems that lacked shipyards capable of repairing a catastrophic failure.

Steve98052 (talk) 07:29, 25 April 2021 (EDT)