All of Trek is incredibly inconsistent when it comes to travel times, so it's kind of unfair to single that one instance out.
I think it is fair to say this is the biggest such error so far though.
All of Trek is incredibly inconsistent when it comes to travel times, so it's kind of unfair to single that one instance out.
I think it is fair to say this is the biggest such error so far though.
I think it is fair to say this is the biggest such error so far though.
We'll add a caption in post-post-production: "Five weeks later..."
I like to assume the battle took a lot longer than shown, that there was a lengthy pursuit between the first salvo and the ship being knocked out of warp. That's really the only place you could fit in more.
So why did Marcus stop blasting the crap out of Enterprise until it was approaching Earth?
The film clearly shows Enterprise exiting warp space immediately after the Vengeance's first strike. There simply isn't room for a long pursuit.
Or rewrite the ending so the final battle still takes place a fair distance from Qo'noS, but nowhere near Earth. Maybe a Federation colony just outside Klingon space. Use the "broad strokes" approach.
Why? In "That which survives" Enterprise traveled almost a thousand light years in a handful of hours. Why would a journey of just over a hundred light years take more than a few minutes, especially on a ship that is unquestionably more powerful than its TOS counterpart?Because that part of the film was stupid and diminishes its respectability?
Sorry, that is just not true.
I beg to differ.
It would have worked better, IMO, if the final battle hadn't taken place in Earth's vicinity, but maybe approaching the edge of Klingon space. Of course, that way, Khan wouldn't have crashed the Vengeance into Starfleet Headquarters, and Spock wouldn't have chased him through San Francisco.
^Look, obviously it's an ill-conceived scene that doesn't make sense. I'm trying to salvage it in my own mind. Of course my solution isn't perfect, but shooting it down just makes things worse. Unless either of you can actually propose a better solution.
^Look, obviously it's an ill-conceived scene that doesn't make sense. I'm trying to salvage it in my own mind. Of course my solution isn't perfect, but shooting it down just makes things worse. Unless either of you can actually propose a better solution.
I understand, Christopher, I really do. But in this instance, I just feel that the best solution would be to treat the final sequence of STID similar to how we treat ENT "These Are the Voyages", and rationalize it as a dodgy holo-recording. The Vengeance did cripple the Enterprise, the Vengeance did crash on a planet, and Spock did beat the crap out of Khan.......but none of that happened on Earth, despite what the holographic dramatization of the events may show.![]()
Especially in this case, given that doing "something cool" was the priority rather than a realistic depiction of warp drive.
I understand, Christopher, I really do. But in this instance, I just feel that the best solution would be to treat the final sequence of STID similar to how we treat ENT "These Are the Voyages", and rationalize it as a dodgy holo-recording. The Vengeance did cripple the Enterprise, the Vengeance did crash on a planet, and Spock did beat the crap out of Khan.......but none of that happened on Earth, despite what the holographic dramatization of the events may show.![]()
...but it is a mistake to create an entire story just to explain away a mistake.
I was unaware that there were actually warp drives.
I was unaware that there were actually warp drives.
Oh, you'd be surprised.
http://en.wikipedia.org/wiki/White–Juday_warp-field_interferometer
We use essential cookies to make this site work, and optional cookies to enhance your experience.