Showing posts with label Die Hard. Show all posts
Showing posts with label Die Hard. Show all posts

Thursday, November 21, 2013

Obliviated

There is, sometimes, a desire to see a movie that you know is going to be bad, but you just can't talk yourself out of seeing it. For whatever reason. Maybe, like with the Die Hard movies, you've seen all the other ones and can't make yourself not watch the newest one despite all the dumb pouring off of it. Or, maybe, there's just some cast member that you just have to see every movie that he's in, like I was with Harrison Ford back in the 80s. Or, maybe, the movie just looks cool and you hope you're just wrong about how bad it's going to be. That's kind of where I was with Oblivion. It just looked cool, and I was hoping, maybe, it was one of those things that the masses wouldn't get into but was really kind of good.

I was wrong.

So here's the spoiler warning, because I'm not going to try to not talk about aspects of the movie, so, if you think, like me, that the movie looks cool and you're probably going to watch it anyway despite what I say (just don't do it. really), you shouldn't read this. If you want to know about all of the dumb (you should!), read on.

I realize this isn't an issue for some people, but it is for me, as I've mentioned before: The movie did that opening narration thing to explain what's going on. I'm convinced that opening narration is almost always a bad thing. If you have to have it, you have either (1) started your movie in the wrong place (2) failed to provide information within the movie in a way that works for the viewer. The Star Wars movies are one of the few places where you can find effective opening narration (in the form of the prologue scroll). And, then, not only did Oblivion open with the narration providing the viewer with an out-of-character monologue of events, but all of that same information was provided about halfway through the movie in almost exactly the same format. Please, do not provide me the same information more than once in your movie. I can almost guarantee you that I got it the first time (which is why I tell my kids to not repeat themselves when they do something they find funny: I did just see it happen).

Despite the opening narration, the movie doesn't make much sense. Ostensibly, Jack and Victoria are a team placed on Earth to defend these large fusion reactors, but, really, why are they needed? There's actually no good reason for them to be there. Sure, sure, he's some technician who has to repair the drones, but that's flimsy at best, because that whole set up is just to support the fact that they want this character that doesn't have any memories, but from any kind of logical standpoint, it doesn't make any sense. I mean, it might (almost) make sense if the stated premise of the movie was true, but you know it's not, because, even if it was, what would be the point of erasing the memories of the support teams? However, with the knowledge that the aliens are really in charge, there is absolutely no good reason to have things set up the way they are. Why do they need humans to repair their drones? And why, after the Jack clones fought for them as their army when they took over the Earth, do they need to trick the clones into believing they're normal humans anyway?

Then there's the problem of Jack having this whole wilderness retreat that he's built, somehow, without anyone finding out. He's able to just turn off the tracking unit in his (what I'm calling) dragonfly ship (which  is very cool, by the way) and go "off comm." What the heck? His navigator person (who never leaves "the tower") doesn't have any idea where he is when he does this and neither do the aliens. Seriously? They just allow him to go off and do secret things without bothering to know what he's up to. Completely implausible. Sure, it makes sense if you believe the story as it's presented at the beginning of the movie, but, again, you know that's not the whole story fairly quickly, and the idea that the aliens (or whatever) would just allow this is beyond imagining. It's what the writer/director do to support the lie and get the audience to buy into it, but those things need to make sense after the truth is revealed, too.

Jack has these dreams... dreams of being in New York before it was destroyed, but that was 50 or so years ago, and he's not that old. My wife kept joking about them being "clone dreams" because, at that point, we were trying to go along with what the movie was telling us. Trying. But we both knew she was right. Right in that being what the movie was going to say they were: memories of Jack's life before he was cloned by the aliens. Seriously? This isn't the 80s anymore, and we already knew in the 80s, even in sci-fi, that clones don't get the memories of the being they were cloned from. The memory flashes work if his mind really was "wiped" before his mission, but it doesn't work as some remnant from his genetic donor. It's just dumb. Why can't we seem to get past this stupid idea that clones have the memory of whatever they were cloned from? (And, again, I just have to point out that Star Wars does not do this, the only sci-fi clone movie I can think of that doesn't fall back on that tired idea.)

Also, the drones, which can follow Jack's "DNA trail" (really? we leave a trail of DNA in the atmosphere even when we're in an enclosed, airtight vessel?) have a problem with his voice identification and consider killing him more than once. I suppose they can't sense his DNA when he gets too close. That's only a long-range thing. (Do you sense the sarcasm there?)

And there's the bit where the drones are flying through the human hideout blasting everyone into cinders but, when one of them corners Jack's wife, Julia (introduced only to be a princess-in-the-tower character), and a bunch of other humans in a dead-end corridor, it pauses and decides to scan them. Again, really? The drone, programmed to kill humans, suddenly needs to stop and scan them? For just long enough for it to get exploded from behind, of course.

And, after all of that, we're not even up to the stupidest part of the movie. I know! I see your jaws hanging. The stupidest part is when he finally flies up to the alien ship, this huge, upside-down pyramid thing, and it's just full of vast expanses of space on the inside! When did this become a thing and what kind of sense does it make? So, yeah, he's flying through this huge space and, every once in a while, he has to fly through an opening in a wall, and the walls are covered in clone pods. The only other things in the huge alien space ship are drones. No aliens. And, when he finally gets to the center to arrive at "Sally," it's just another inverted pyramid thing with a flashing (talking?) red light. NO ALIENS! So tell me why they needed to take over the Earth and use it as a source of material for their fusion reactors IF THERE ARE ACTUALLY NO ALIENS? And, if that's all they needed, why didn't they just stop at any of the unpopulated planets on the way into the solar system? Wouldn't that have been so much easier than having to fight a bunch of humans for the materials they wanted? AND WHERE WERE THE ALIENS?

There was also an even more stupidest part. The part where somehow the flight recorder from Jack's spaceship from when he first got captured by the alien ship went from being in the command module, recording what was happening, to being in the sleeping quarters of the ship even though the sleeping portion had been jettisoned. Because that makes all the sense.

The acting, though, wasn't bad. Not great but not bad, either. And the tech was decently cool. But there was a reason (many of them, actually, as I've pointed out) the movie didn't make back its production budget domestically. So, unless you just have to prove to yourself how dumb the movie is, this is not one I could suggest to anyone.

Thursday, September 5, 2013

A Good Day For This Movie To Die Hard

Despite the bad reviews, I figured I should probably see A Good Day to Die Hard since I've seen all of the other Die Hard movies and liked at least one of them. Okay, maybe two of them. However, I went in with low expectations. This is the series in which the protagonist survives the explosion of a boat by jumping into the water next to the boat. Because, you know, being in the water totally protects you from explosions in the water. So, not only do we have that, but this one, the 5th (and I'd totally lost track, at this point, that this was the 5th one), was actually getting pretty horrible reviews.

It seems I did not lower my expectations far enough. Good Day fails at pretty much every level of story telling and movie making. Well, except for the explosions. It has plenty of those, which, in the Michael Bay theory of movie making, is all you need to make a good movie. I have to suppose John Moore and Skip Woods (the director and writer, respectively) are Bay disciples.

The first real mistake the movie makes is having the movie open with McClane's son instead of with McClane himself. It's Die Hard; we're here to see John McClane, not junior. To make it worse, they just throw the audience into the middle of a situation for which there is no context. This is one of the reasons I hate that whole "start in the middle of the action" "rule." They definitely did that with this movie. However, not knowing anything about the characters or the situation, there is no way real way to know whom we should be caring about, so we don't really care about anyone. Of course, this all ends, as we come to find out, with John Jr. (Jack) in a Russian prison. And, as my wife said, "What? I didn't even know he had a son."

[As a total aside, the plot arc includes the exposition for a reason. When you skip that part so that you can "start in the middle of the action," you skip the part where the audience gains empathy for the protagonist and comes to care for him or her. Without an exposition, you do not have a complete story, and that's just bad writing.]

The issue here is that there is an expectation that we will care about Jack because John cares about Jack. Except we don't have any context, really, for John caring about Jack since he's barely mentioned or seen in the other movies. Conveniently enough, John has suddenly chosen this moment to care about Jack, whom he has not spoken to in years, and has had one of his old cop buddies track Jack down for him just at the time that Jack is arrested and thrown into a Russian prison. Of course, there is no good reason why McClane's cop friend should be able to find out that undercover CIA agent Jack McClane has been thrown into a top Russian prison. Especially within what seems to be hours of it happening. Not that McClane even knows that his son is CIA.

Being John McClane, he just jumps on a plane to Russia with some vague expectation that he will be able to connect with his son when he gets there. His son that is in a top, possibly top secret, Russian prison. And, of course, without planning it, he happens to arrive on the day that his son is going to appear in Russian court as a witness against the guy that Jack is supposed to be saving. And, also of course, he stumbles into the middle of a prison break/abduction of the guy that Jack is supposed to be saving (and also testifying against).

This is where we expect, I guess, John McClane to become "yippee-ki-yay" John instead of old, tired John that we find at the beginning of the movie. But we don't get that. No, what we get is John chasing his son around during the middle of a fire fight trying to talk to him about how sorry he is that he wasn't there for him when he was a kid. I think it was supposed to be funny. I think. But it didn't even rise to the level of ludicrous as John meanders through the bullets and explosions and, eventually, when his son takes off in a vehicle without him, steals a truck to follow his son while yelling, "I'm not through talking to you!"

And through all of this we have been given no real reason as to why this guy Jack needs to save is so important other than that the CIA want him and that some muckety-muck Russian wants him dead. Or abducted. And the guy's daughter is involved, except we're not supposed to know that, but as soon as the dude tells McClane that he has a daughter, I knew it was his daughter that was the woman in the group trying to capture and/or kill the dude. And also of course no one turns out to be on the sides they're presented to be on except McClane, the sadist bad guy, and the dead people.

Possibly the worst bit, which is saying a lot considering how terribly the movie began, is when Jack overhears John telling the Russian dude about how bad a parent he was and how bad he feels about it and how all he wants to do is make everything right with Jack. But, since, Jack hears John saying this, we are spared any action or work on the part of John to repair his relationship with his son, because his son, now, understands that his dad worked all the time because of how much he loved Jack. And, then, of course, they bond over killing the bad guys and everything is okay.

I'm not making it out to be as bad as it really is. It was bad enough that, before the hour mark, my wife decided that she was through with the movie. I'm not actually sure why I finished watching it other than the fact that I have a hard time stopping something once I've started it no matter how bad it is. That this movie was bad wasn't even the worst part about it. It just felt completely inauthentic. McClane's actions didn't feel authentic (Who, really, just jumps in a plane and flies to Russia with the vague plan of getting in to see someone in a Russian prison? John was a cop; he, theoretically, knows how this stuff works and it's beyond far-fetched that he, even being John McClane, would just hop in a plane without contacting the State Department or something). The fact that Jack refers to his father as "McClane" didn't feel authentic (Seriously? "Damn you, McClane" is the best they could come up with for Jack to say? I buy him calling his father "John" but the whole "McClane was a stretch the rubber band couldn't take). The whole conflict of the movie involving Russia and nukes didn't feel authentic. It's not the 80s anymore.

So, yeah, give me more of escaping explosions by jumping into the water next to the boat that's exploding. At least that was just a brief moment of stupidity unlike the stupidity that was this movie from beginning to end. And that doesn't even cover how dumb the title is, because, if you're going to use the phrase "a good day to die," you need to actually have it be relevant to the movie, but no... no relation at all. Just a cool title. But, then, a cool title doesn't make a cool movie.