Sunday, September 27, 2009

Geek Movie Plot Holes

So Wired magazine published a list of the Top 10 Unanswered Questions in Geeky Movies. (HT: Neat-O-Rama)

I thought it was a good read that merited sharing, but not without comment. A few of these plot holes aren't really plot holes at all. Specifically, the Star Wars ones. Maybe some of the others have explanations too, but I don't know enough to offer a rebuttal.

Quoting from the article:
"4. Star Wars: The Death Star’s slow attack - So the Death Star follows the tracking device on the Millennium Falcon to the rebel base. They jump out of light speed, and, for no clear reason, emerge on the far side of the planet Yavin from the moon where the base is. This light-speed jump takes a split-second, but now they have to wait minutes so they can clear the planet. Not only that, but the Death Star is capable of blowing up entire planets, not just moons, so why don’t they just blow up the entire planet of Yavin? Surely that would effectively destroy anything on its moons as well."

Resolution: The Death Star is a giant space station that travels very slowly. Hyperdrives (the faster-than-light) technology operate on completely different principles than the sublight drives. The Death Star followed the Millennium Falcon to the Yavin system, and once it got there, had to use its slow engines to get around the planet (the long lag time makes sense). Why not hyper-jump around the planet? Hyperdrive jumps take a while to calculate, and gravity is a big obstacle that limits where you can go safely. Intra-system jumps were never part of the story--hyperdrives only get you from system to system.

Why not blow up the planet Yavin itself? This one bothered me too, and several answers come to mind. One, it's a gas giant, so blowing up the relatively tiny core might not be a guaranteed kill against the moon, especially if most of the planets mass is actually in the gas or there are other strange principles at work (magnetic ones come to mind, but I won't expand on that here). Why not blow up the planet, THEN blow up the moon if you miss? I'm guessing a giant superlaser like that takes long enough to recharge that it made sense to go for a guaranteed kill after a 20 minute trip than to risk having to wait around for hours (maybe more) for your second shot, giving the Rebels plenty of time to evacuate.

A bigger unanswered question in my mind would be: why didn't the Rebels start evacuating the moon of Yavin IV immediately, just in case 24 one-man fighters didn't manage to destroy a space station that was 235 miles in circumference?

"2. The Empire Strikes Back: Time dilation - Luke and R2D2 leave Hoth to go to Dagobah at the same time Han, Leia, Chewbacca, and C3PO leave to go… well, they never really say what their initial destination is. Anyway, on Dagobah, Luke embarks on an intensive Jedi training course with Yoda — it’s never stated, but it’s heavily implied that this takes a long time; and besides, you would think a full course of Jedi training would take at least months, right? (We know it’s a full course, because when Luke comes back in Jedi, Yoda tells him he doesn’t need more training.) So, at the same time that Luke finishes this months-long training and runs off to Cloud City, his friends have clearly just gotten there a short time before. Yet all they did on the way was flee from a Star Destroyer and fly down the gullet of a giant space worm. That must have taken hours, not months. So was the Millennium Falcon flying at close to the speed of light (but not at light speed) for a while and thus experiencing time dilation? Yeah, that’s the ticket."

Resolution: This one's pretty easy: the Millennium Falcon's hyperdrive was out. They had to make the trip from Hoth to Bespin at sublight speeds. I think it's more amazing that didn't take YEARS, as planets are typically pretty far apart (and Hoth was in a supposedly remote region). What's amazing here isn't that Luke's training was so short--it's that the OTHER storyline was so chronologically compact (or, conversely, that the training was so long and the Falcon had enough emergency rations so no one died of starvation or dehydration along the way).

No comments: