Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 28/05/13 in all areas

  1. Personally speaking, I didn't find any gaping plot holes in STID—or at least they didn't bother me enough to notice. The movie was sufficiently entertaining for me to suspend my disbelief above those gaps. I may also be allowing the "alternate reality" premise to gloss over most of these issues (perhaps more than I should). On the other hand, I've been compulsively trained as a Nitpicker to the point where I can't overlook some of the missed connections and wonky premises that cropped up along the way. Here's a couple of my biggest ones . . . which, interestingly enough, provide a contrast in perspective. Some folks have expressed disappointment that the entire story took place in (what appeared to be, anyway) only a day or two. I don't see why that's a problem myself; some movies portray the events of only a few hours, and 24 certainly got plenty of mileage out of the action possible in a single day. My issue isn't with time elapsed—it's with what elapsed during that time. To set the stage: no one in either movie ever attaches a value to the word "warp." They never specify which warp, whether it's Warp one, three, five, whatever. Since we've returned to the earliest incarnation of the Trek universe, maybe we can just assume that "warp" is a standard, fixed, super-light speed that's probably nowhere as fast as later, upgraded vessels can move (as demonstrated by the Dreadnought-class ship in this very movie). So for the sake of this nitpick, let's just say that "warp" in Abrams' world is somewhere around Warp 2—significantly faster than light, but not exponentially so. With that in mind: - Forget what I said in my calculations above. The Enterprise must be capable of something closer to Warp 9.9998, since it takes only minutes for them to go from Earth to Klingon space. Even in the NextGen timeframe that's usually a trip of a few days. While the jaunt to Kronos may have taken longer (we could assume some passage of time between scene cuts), on the way home there's no question about it: the Enterprise goes to warp, Marcus catches up inside of 30 seconds later, fires on them, and brings them out of warp less than a minute later . . . right on Earth's doorstep. How is this possible? - While we're on that, who the hell's drivin' this thing, anyway? Neither Sulu nor the navigator beside him seem to have much of an idea when to stop their starship. They relied entirely on unfortunate circumstances to come out of warp on both occasions. The first time the warp core malfunctioned, halting them at the edge of Klingon space (which is where they were supposed to be, right?). Given that it only takes a minute or two to reach Klingon space, if they had stopped even a few seconds later they'd have been halfway to the Neutral Zone. Shouldn't they have stopped there anyway? It's the same way the second time. Marcus blasts them to an early stop--right next to the moon. Just think: if he hadn't, they would've started their five-year mission a year ahead of schedule. - And while we're on that . . . Klingon space isn't very big, is it? The Enterprise floats to an unpleasant stop within sight of Kronos. That sightline puts it well inside the solar system—well within the next planet's orbit, in fact. Yet they're still supposedly on the edge of Klingon space. Not much of an "empire" yet, I suppose. I'm on a roll. Can't resist one more: - As the Enterprise is falling helplessly from space, Sulu announces that if they don't get shields operating soon they'll be incinerated on re-entry. Very true. So Kirk Riverdances on the warp core for a minute, eventually aligning the two thingies and restoring power. Sulu fires thrusters just as the ship disappears into the cloud layer. It emerges (in very cool fashion, I might add) a moment later, and the news comes that both power and shields have been restored. Except . . . those clouds would lie well below the ozone layer. The Enterprise would've been cinders by then. - Uni
    2 points
  2. I also had the exact same problem Miguel. I use Firefox. Anyway, i found the solution. i pressed the download file, it took me to the page where it has the player and plays the file (in my case a Quicktime player), and in that page i go to the firefox toolbar , File - save page as (i assume this is the translation in english because I have it in Greek), and it saves the 2.3 MB mp3. This is not a different intro! it's the intro of the piece, it's just that the one that is in the start, misses those first few bars (almost 8 bars) due to the video not starting from the start of the piece. maybe someone could grab that intro, and glue it to the piece we have from the start of the video?
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines.