Showing posts with label Christian Slater. Show all posts
Showing posts with label Christian Slater. Show all posts

Friday, October 28, 2011

Interview With the Vampire: The Vampire Chronicles

While I wouldn't ordinarily consider myself mean-spirited, there is something about failed movie franchises that I find extraordinarily amusing.  I'm not talking about the movies that kill a franchise (Batman and Robin), but the movies that were supposed to have sequels, but never did.  Street Fighter, Super Mario Bros., The Adventures of Buckaroo Banzai Across the 8th Dimension, Remo Williams: The Adventure Begins, Godzilla (1998) --- and that's not even counting every comic book or video game movie that never spawned a direct sequel.  While Interview With the Vampire: The Vampire Chronicles was, eventually, followed by Queen of the Damned, nobody from the original film reprised their role and the film was pretty loose with its continuity; Queen was more of a reboot than a direct sequel.  Still, it's hard to believe that such a successful movie --- it grossed almost four times its budget --- with such an ambitious subtitle didn't wind up being a tent pole film.  Maybe audiences just weren't that interested in Hollywood heartthrobs wearing frilly shirts.
"Doth he besmirch our honor, bro?"

Interview With the Vampire: The Vampire Chronicles is, essentially, the 200-year life story of Louis (Brad Pitt), as told to a reporter (Christian Slater) in --- you guessed it --- an interview.  In colonial New Orleans, Louis was a plantation owner who was mourning his late wife and child.  He had lost his taste for living, and spent his time tempting death; as it turns out, he got more than he bargained for.  Thanks to his deliciously suicidal tendencies and hunky good looks, Louis attracted the attention of the vampire Lestat (Tom Cruise).
Hickeys hurt so good
Lestat turned Louis into an undead creature, but Louis had more in common with the grunge scene than just his hair; he had angst, which meant that he refused to take the life of another person.  Sure, watching Louis drink the blood of rats is fun for a while, but Lestat transformed Louis to be a companion, not a novelty.  He needed something to force Louis to stop moping and get on with his un-life.  Enter Claudia (twelve year-old Kirsten Dunst).
Adorable + Horrifying = Adorrifying?
Would turning an innocent child into a natural predator be enough to keep Louis by his side?  Is giving a child the power of evil a good idea?  Will Louis ever get over his whining and start killing people?  And where the hell do vampires come from, anyway?  Most of these questions get answered as Louis tells his tale, whether explicitly or not.

Perhaps the most impressive parts of Interview With the Vampire are the productions aspects.  The sets are pretty awesome throughout, peaking with Armand's ridiculously Gothic underground catacombs.  The soundtrack is pretty good, although occasionally over-dramatic; in a movie that has so many emotional bromances, though, that can be expected.  The costumes are also excellent period pieces, although the hair and make-up for the vampires was hit-and-miss for me.  I liked that the paleness of the vampires would depend on how recently they fed, and I thought Brad Pitt's vampire eyes were pretty cool-looking.  However, I couldn't get past some of the crappy wigs and Lee Press-On Nails used by some of the cast.
"Available in Natural or Glamor lengths!"

Production values don't make a movie, though.  Since this is, essentially, a vampire biopic, it needs a compelling lead and a solid story arc.  I enjoyed Brad Pitt's performance as the eternally morose Louis, but his character was not really one of action; everything he did was a reaction, which makes him less interesting than some of the other characters.
Louis, in action
The headlining actor in this film is Tom Cruise, and it's easy to see why.  While Lestat is not the main character in this film, he is the most active character.  Whether he is playing a villain, trying to fight loneliness, or merely gazing at Louis with his jaw hanging open in a not-at-all-homoerotic fashion, Lestat is the wheel that propels this story.
It's too bad that Tom Cruise isn't very good here.  I normally don't have a problem with Tom Cruise's acting, but this just felt like a poor match.  He wasn't scary when he was being evil and his wicked laughter felt forced.  He improved dramatically after Claudia plays her trick on Lestat, but it was a little late for that improvement to matter much.  Kirsten Dunst was actually pretty good as the spoiled vampire child, which shocked me, since she's generally pretty awful.  I thought Christian Slater was fine in his small part, too, although it wasn't too demanding.  Antonio Banderas was less impressive as the mysterious Armand; he might have been mediocre if his wig wasn't ridiculous, or if his character's scenes weren't almost entirely devoted to subtext.  Stephen Rea was a little more fun as Santiago, but he should have been more terrifying.  You also might recognize Thandie Newton as Louis' main house slave; she wasn't particularly impressive, but she wasn't bad, either.

As cool as some parts of Interview With the Vampire are, they just don't add up to an entertaining or horrifying whole.  I felt that director Neil Jordan focused too much on the look of this picture (which is admittedly great) and not nearly enough on the main actors.  Brad Pitt can play tortured in his sleep, but I thought he wasn't given enough to do in this movie.  Tom Cruise, on the other hand, had a much wider range of emotions to play with, but never came close to meeting all the demands of his character.
Tom Cruise emotes
Thanks to those to flaws, the film's pacing seems extraordinarily slow.  I remembered liking this movie when I first saw it, because the tortured and moody vampire was a novelty.  This movie does a great job with that desolate loneliness, but with the current influx of vampire characters in popular culture, it no longer feels special.

Maybe my problem lies with the source material.  I remember reading the first few volumes of Anne Rice's Vampire Chronicles when I was younger, and I enjoyed the first couple of books (of which, Interview... was the first).  After a while, though, I realized just how annoying most of her characters are.  Take this story, for instance.  You have a wicked vampire (Lestat), a Goth-inspired depressed vamp (Louis), a bratty child (Claudia), a maybe kind of manipulative or maybe just bored blood-sucker (Armand), and another wicked vampire without a back-story (Santiago).  Who am I supposed to give a rat's ass about?  By default, it becomes Louis, but he is far from an entertaining storyteller.  Even what makes him initially special (his refusal to kill humans) is eventually brushed aside with barely a comment when he finally gives in to his nature.
Why so serious?

For all the technical prowess Interview With the Vampire: The Vampire Chronicles has to offer, it's lacking in drama and interesting characters.  That's not a deal-breaker for an entertaining film, but this movie isn't much fun to watch and isn't gruesome enough to scare.  If you're a fan of Gothic horror, this might be up your alley.  I'm not, so this one definitely earns a "meh" rating from me.

Sunday, February 13, 2011

True Romance (Director's Cut)

Continuing with my mini-theme of romantic movies that I actually like, in honor of Valentine's Day, I bring you True Romance.  Directed by Tony Scott and one of Quentin Tarantino's first professional screenplays (I can never figure out if this came first, or Reservoir Dogs), True Romance is a blend of crime, action, Tarantino dialogue, and true love.  This film also boasts one of the all-time greatest supporting casts, with some of the most memorable scenes highlighting supporting characters that you will ever see.

Clarence (Christian Slater) works at a comic book store (awesome!) and, for his birthday, has decided to catch a triple feature of Sonny Chiba movies at a local theater (awesomer!).  While watching the movies, a busty blonde named Alabama (Patricia Arquette) comes in and spills her popcorn all over him.  Clarence is very gracious about the whole thing, possibly because of her cleavage, and the two strike up a conversation.  They end up getting some pie after the movie (awesomest!), which eventually leads back to Clarence's place for some sexy sexy time.  Of course, this isn't as perfect as it seems.  It turns out that Alabama is a call girl, hired by Clarence's boss to sleep with him as a birthday present.  Clarence doesn't mind at all, insisting that he had had the night of his life; the two abruptly declare their eternal love for each other and get married in the morning.  Aww.  The rest of the movie has the two getting to know each other and finding out that true romance means compromise.

The "crime" part of the story begins when Clarence chooses to confront Alabama's pimp, Drexl (Gary Oldman).  He doesn't really have a solid reason for this, it's just his inner alpha male (which is personified by an imaginary Elvis that gives him advice) needing to prove itself.  The short version of the story has Clarence killing Drexl and leaving with a suitcase of Alabama's clothes.  When he returns home and tells Alabama that he just killed Drexl, her response is "That's so...romantic!"  I guess Clarence married the right gal.  The suitcase he brought with didn't have his new wife's old clothes, though; it was filled with uncut cocaine.  Not knowing what to do with a suitcase of coke, Clarence and Alabama do the only sensible thing they can think of: they go to California to sell it to move stars.  Unfortunately, the late and unlamented Drexl was selling the drugs for the mob, and they are not as forgiving as you might think.

The first thing you notice about True Romance is the dialogue.  It still sounds fresh and funny today, but it really sticks out against the rest of 1993 Hollywood.  To put it in perspective, the nominees for Best Picture that year were The Fugitive, The Remains of the Day, The Piano, In the Name of the Father and Schindler's List, none of which were particularly renowned for their rapid-fire creative vulgarity.  And while you might recognize some echoes of Tarantino's dialogue from this movie in Pulp Fiction, it's still good stuff.

The script is definitely this film's strongest point, but the astonishing supporting cast is a close second.  This movie has so many recognizable actors in it, and most of them have surprisingly meaty roles.  Dennis Hopper and Christopher Walken share one of my all-time favorite scenes, and it's just the two of them talking.  Brad Pitt is hilarious as a worthless, pot-smoking roommate; he was actually offered the role of Clarence, but it conflicted with his filming schedule for Kalifornia --- he just picked Floyd, who originally had no lines, out of the script and ad-libbed all his stuff.  And Gary Oldman's performance as Drexl is so good that I usually watch it two or three times before continuing with the rest of the movie.  I don't know whose idea it was to make this pasty-white pimp pretend that he was a black man, but it's pretty damn funny; Oldman doesn't let his character become a joke, though, and turns out a frightening performance.

Just those four performances would be enough for most movies, but this film is overflowing with larger-than-life supporting characters.  Chris Penn and Tom Sizemore (before he was a train wreck) did a great job as detectives.  Bronson Pinchot and Saul Rubinek play obnoxious Hollywood types almost to the point of becoming caricatures, but they're still entertaining.  James Gandolfini has a good scene as (what else?) a mob enforcer.  Even the normally talentless Michael Rappaport looked good (because he was playing a talentless actor).  And then there are the bit parts!  Samuel L. Jackson has a brief but entertaining scene where he discusses the universal nature of oral sex, Val Kilmer plays Clarence's imaginary Elvis (whose face is never shown, thanks to some truly awful makeup), and a young Kevin Corrigan has a small non-speaking role, too.  On the whole, this supporting cast is good enough to star in three or four solid movies; all together with a clever script, True Romance is a movie that has no boring scenes, and every minute has an actor you recognize in it.

Of course, all that support would be worthless if the main actors are no good.  And, to be honest, half of them aren't great.  Patricia Arquette, while very white-trash hot in this movie, does not do a good job.  In fact, I would argue that she sounds like she has some sort of mild retardation.  For some reason, her character is given a voice-over at the beginning and end of the movie, too, and they're not great either, even with a good script.  Christian Slater, though, does deliver his lines well, giving Clarence a cocky, roguish attitude that matches the tone of the picture perfectly.

Tony Scott directed this movie, but it was before his work in Enemy of the State, so it doesn't have all the 360-degree, fast-motion establishing shots that his last decade of films have had.  Instead, he plays it pretty simple and lets the script do most of the work.  Nobody's monologue is interrupted by unnecessary camera cuts, there are no fancy split-screens or anything like that.  Aside from some particularly violent fights scenes, Scott doesn't really take the opportunity to show off, and the film is better for it.  I disagree with giving Alabama bookend voice-overs, but that's a small price to pay.  Really, aside from a better soundtrack, I don't see how this movie could be improved by having Tarantino direct it himself.

This is a fast-paced crime movie with lots of overly-clever vulgar dialogue. If that's not your thing, then catch a Katherine Heigl movie instead.  This is the first time (and only time, so far) a Tarantino script had anything resembling an actual romance in it, and while pretty unconventional, it works.  There is no point in the movie where I wondered why these two characters were together, and that adds a lot of heart to the mix.  This isn't your typical romantic comedy, but Clarence and Alabama's unquestioning, immediate, and confident love for each other is unusually refreshing.  It's simple and untroubled, and that's perfectly fine in a movie like this.  Even with Arquette's mentally challenged performance, True Romance remains one of my favorite films of the 1990s, and one of the few that deserve ten stars.

Friday, September 10, 2010

Alone in the Dark

How might you know Alone in the Dark is going to be a bad movie before you watch it?  Well, perhaps you know that it is a film adaptation of a video game franchise.  Those always make for good movies, right?  Or maybe you noticed that Uwe Boll is the director.  Or perhaps you saw Tara Reid's name above the title.  All of these are good reasons not to watch this movie.  The only reason you should watch this is if you want to see just how bad it gets.  Here's a hint: pretty bad.

For those of you unfamiliar with the video game series, Alone in the Dark is a suspense/horror game.  Basically, you wander around creepy buildings, looking for clues as to what has made everything so creepy, until you encounter a monster.  At this point you can either mash your controller buttons frantically, hoping that your character will shoot the damn thing, and/or you can soil yourself.  That basic concept makes this series sound like a natural fit for the supernatural thriller movie sub-genre.  So, should we expect a lot of eerie sets and the kind of suspense that has you waiting and for something to happen, and nothing happens and nothing happens and nothing happens and then the music gets real loud and LOOK OUT there's nothing there?  Repeat three times, and on the fourth time, exchange the "nothing" for "a zombie frothing at the mouth."  Actually, that might not be a terrible movie.  Too bad that's not the direction the filmmakers took.

The film opens with a lengthy prologue, which is immediately followed by a reenactment of the lengthy prologue.  That prologue must be pretty important to the story, right?  Actually, no.  It feels like some poor soul watched an early cut of the movie and asked "What the hell was the beginning all about?"  Instead of taking this as a hint that the plot and script are pretty bad, they just had someone do a voice over summary of the first scene.  Brilliant save, Mr. Boll!  It then turns out that the prologue and the reenactment were just dreamed by Edward Carnby (Christian Slater), paranormal investigator.  So...his dreams have voice overs?  How very meta.  Carnby was asleep on an airplane, when he wakes with a start.  The child sitting next to him helpfully tells him that there's nothing to be afraid of in the dark.  Not that the airplane was dark.  When Carnby lands, he is then followed by a creepy dude, and they eventually fight.  The creepy bad guy clearly has super powers, because he can jump high, run fast, and punch through bricks.  Carnby also appears to have powers, because he can hold his own in the fight.  That's never explained, but at least it's shot in slow-motion.

Meanwhile, we are introduced to the assistant curator of a museum, Aline Cedrac (Tara Reid).  She doesn't speak, but instead acts intelligent by wearing glasses and writing on a clipboard.  Instead, an unusually well-informed security guard discusses how awesome she is to a delivery driver within earshot of her.  He also explains that the stuff being delivered is a bunch of Abkani artifacts.  The Abkani were a super-advanced culture that vanished 10,000 years ago, and their relics have been found in the most remote parts of the world.  You've probably heard of this not-at-all fictional siciety, so I won't bother you with any more information about them.  Neither will this film.

What does that have to do with anything?  Well, Carnby shows up at the museum with an artifact for Aline to check out.  The two are apparently lovers, but Carnby vanished for several months without contacting her.  Aww...but they seemed so right for each other!  Aline scans the artifact into her computer (How?), and it immediately builds a three-dimensional image of the artifact (No, really...how?) before telling her that the artifact is definitely Abkani (What?!?  Now you're just messing with me!).  How did Carnby get his hands on this artifact?  In his exact words,
"I was in the Amazon for six weeks, tracking poachers across their transport lines and I fell in with a group of ex-Chilean military that were selling artifacts on the black market."  
Dude, if you don't want to tell me the truth, just say so.

So, I guess the super-powered bad guy was after the artifact?  It's never explained, really, but not explaining that at least avoids explaining how the bad guy knew Carnby had the artifact to begin with.  Anyway, these weird kind of, sort of, sometimes invisible monsters that look like a blend of a dog, reptile and scorpion break into the museum and chase Carnby and Aline for a while.  Then a military group shows up, shoots the dogorpions, and the field leader, Burke (Stephen Dorff), belittles Carnby for being involved.  If that makes no sense to you, congratulations, you're sane.  Apparently, Carnby used to be part of this military group, but he quit for the exciting life of the paranormal investigator.  Burke hates him for that.  Or something else.  You never find out.  But he hates Carnby and refuses to accept his help.  Until he changes his mind.  And then more super-powered people show up and kill a bunch of soldiers.  And then Carnby, Aline, and Burke figure out where the dogorpions are coming from and go there to attack the source.  Will they succeed?  Or will they just suck?

Here are just a few ridiculous things about this movie:
  • The main characters are never actually alone in the dark.
  • All travel scenes are done with long shots of vehicles and voice over.  Cheap.
  • Christian Slater and Tara Reid have a sex scene, where she keeps her bra on.  I certainly don't want to see her mangled boobs again, but that's just weird.  It's not like she was cast for her acting ability, so the lack of nudity is absolutely befuddling.
  • How do they find the location of the dogorpion source?  By combining Abkani artifacts so that they make a tower, which somehow indicates a constellation, which helps pinpoint a geographic land mass, which appears to be the United States.  Pin and point!
  • An abandoned scientific lab has power, twenty-odd years after being abandoned.

This is just a mess.  Characters come and go, with no points of reference to indicate how close they are to danger.  The super-powered bad guys turn out to be sort of zombies, which somehow connects to the prologue, but not very well.  The special effects are cartoony, and even the lack of light on the set doesn't disguise it.  Characters change their personalities on a dime and randomly prioritize things.  Hey, Stephen Dorff, you've left dozens of your soldiers after they've died, but when time is a factor in the plot, you all of a sudden have to save an undoubtedly dead guy?  C'mon!  These obvious flaws are kind of funny, but the movie isn't any fun to watch.  I can like me some Lefty Gold when I find it, but this was just a draining experience.

This was a bad movie from start to finish.  And, when I say "start," I am referring to the start of pre-production.  It didn't stay true to the tone of the games and it doesn't feel like a horror movie.  The action sequences are boring and stupid.  The plot was unintentionally incomprehensible.  On paper, you would think that casting Tara Reid as the resident smart person in the movie would be the film's biggest mistake, but that pales in comparison to all the story problems.  I'm convinced that Uwe Boll doesn't understand the concept of storytelling.  In the unrated version (which I have not seen), Boll allegedly re-cut the film radically, virtually eliminating Reid from the final product.  Now, I'm not going to lie and say that Tara Reid is a fine actress, but her involvement was far from the worst thing about Alone in the Dark.  The fact that Boll would misunderstand his product's shortcomings that much makes me hope never to see another of his movies again.  I probably will, because they all look hilarious, but I should probably see this film as a lesson in how bad movies can be.

Thursday, July 15, 2010

Windtalkers

Loud explosions, pyrotechnics, and bodies flying through the air come naturally to the modern war movie, even to the point that sheer devastation is no longer an effective selling point.  These movies need their own angle in order to avoid being seen as lame Saving Private Ryan copycats.  The hook for Windtalkers is the relatively unknown tale of the Navajo tribesmen that joined the army to act as code talkers in the Pacific side of World War II.  That actually sounds like an interesting premise; so many war movies go boom, while very few spend the time to think.  Sending and breaking codes sounds fairly cerebral, right?

Ooh...but John Woo directed this movie.  And he teamed up with Nicolas Cage as the lead actor and Christian Slater as an important supporting character.  So...the main character isn't Navajo, despite the hook for this movie being about the Navajo code talkers.  Great.  I will give credit where it's due; at least they didn't pull a Touch of Evil and give the lead actor an unconvincing ethnic makeover.  Well, if the story is not centering on a Navajo character, what is the story?

Joe Enders (Cage) begins the movie by holding his platoon's position on Guadalcanal at all costs, which means everyone died except him; he was injured, losing hearing in one ear, which also occasionally hurts his balance.  He recovers in a hospital, thanks in part to a nurse (Frances O'Connor) that is clearly attracted to him, despite the fact that he is played by Nic Cage in his "brooding" mode.  Enders gets a promotion and a new assignment as soon as he is well; his new assignment is to protect Ben Yahzee (Adam Beach), one of the new Navajo code talkers.  Ox Anderson (Slater) receives a similar assignment, protecting Charlie Whitehorse.  The Navajo language is an unwritten one and is almost incomprehensible, even within its own language family, which makes it especially hard for enemies to translate; these code talkers were bilingual Navajo that transmitted important messages without the risk of being understood by the enemy.  If the Japanese managed to ever understand the Navajo language, though, the American forces would be in trouble.  Therefore, both Enders and Anderson are told that they must protect the code at all costs; their code talkers must die before being taken captive by the enemy.

That's pretty much the story basics, but there's plenty of stock subplots.  You've got the predictable awkward assimilation into the unit by the Navajo.  They are seen as savages at first, but their impossibly calm demeanor and passivity earn the respect of their squadmates and their practices become more acceptable over time.  Of course, there's one guy (Noah Emmerich) in the squad that is racist; of course, his life is eventually saved by a Navajo.  There's the nervous soldier (Mark Ruffalo) and the guy with the cool weapon (Brian Van Holt).  There's the commanding officer (Peter Stormare) that needs things done, no matter the cost.  There's the inevitable split between the two parallel plot lines; you know either Anderson or Enders will eventually have to kill a Navajo to protect the code.  Who will it be, the nice Anderson, or the bad-ass Enders?

This movie should have been so much better.  Obviously, the big problem is the story.  Why make a movie about the Navajo code talkers, if they are not the main characters?  I'm not crazy about Adam Beach as an actor, but using him as the POV character would have been much better.  Instead, we have a tortured white soldier to identify with.  Even better, it's Nicolas Cage in full-on inappropriate overacting mode.  Ignoring the poor choice of main character, this movie still has major problems.  Are you telling me that the Marines put two extremely valuable code talkers in the same squad, facing immediate danger?  There were only about two hundred of these guys in the war.  I'm pretty sure they would have been better suited for sending messages from wherever the local base was.  This movie barely even uses them for sending or receiving codes; they spend most of their time giving uncoded coordinates for air support.  That's really stupid.  What, are the Japanese (who are shown listening to the radio transmissions) going to hear their own coordinates and assume that whatever is coming their way is good?  Maybe the Americans are bringing them ice cream!  Stupid.  And how many Japanese die in this movie?  This is the Pacific war, where they were dug in and well-protected.  The Americans just run up the side of mountains, and yet I'd estimate that the dead Japanese outnumbered the dead American soldiers by a 4:1 ratio.  That is so far beyond stupid, it's insulting to stupid.

The acting is what you would expect from a John Woo movie.  It's barely there.  Nicolas Cage gets to make funny faces when he's in battle and sulk when he's not.  I'm sorry to say that he actually showed the most range in this movie.  Christian Slater, Peter Stormare, Mark Ruffalo, and Brian Van Holt were all one-dimensional caricatures of 1940s soldiers.  Noah Emmerich got to be the racist jerk that sees the error in his ways (well, he learns to accept one Navajo, anyway), but the character is so boring and predictable that you still don't care.  Adam Beach was a little better, but his character had no emotional arc, so there was nothing for him to do in this role.  Whose fault is all this?  Well, you can blame the writers, John Rice and Joe Batteer, because this story sucks, but I'm going to blame John Woo.  As the director and a producer on the film, he had ample opportunity to realize how crappy this script was and have it fixed.  He didn't, so the responsibility for this wreck belongs to him.

This movie doesn't even have the normal perks of a John Woo movie.  The action isn't good.  Woo is best known for his slow-motion, stylized action sequences, where impossible things happen and then explode.  Here, he tries to channel the destructive spirit of the Pacific war and fails.  The big battle scenes try to have a documentary feel to them (a la Saving Private Ryan), but the special effects in these scenes are far worse than any war movie released in 2002 should be.  Some of the smaller-scale battle sequences are fine, but it's not enough to make this movie watchable.

Let's see...bad story, bad acting, and bad action.  Yep.  This is a bad movie.