Showing posts with label Kevin Dunn. Show all posts
Showing posts with label Kevin Dunn. Show all posts

Wednesday, November 17, 2010

Clickety-Clack: UNSTOPPABLE

Early in Unstoppable, two slacker train-yard workers (T.J. Miller and Ethan Suplee) fumblingly start a chain of events that leads to a large freight train carrying toxic chemicals going full speed and unmanned down the tracks. In the grand tradition of Speed and, well, Runaway Train, Unstoppable is an action film about a seemingly unstoppable force. The train blasts down the track, its constant chugging animating the soundtrack as a constant source of tension. It literally howls an animalistic roar as it blasts forward. The danger is omnipresent. This train is clearly on a collision course and when it crashes, it will be messy.

It’s directed by Tony Scott and so is, perhaps inevitably, filled with the kinds of stylistic ticks that he has accrued over the last several years. The camera jitters around while the editing cuts away mid-pan. There are tense little zooms that come out of nowhere. Color filters are intermittently applied. Shots slip out of focus, or start blurry just to be pulled sharply into extreme clarity. Quick frames of double-exposure or pops of white light show up intermittently. You’d think I’d consistently dislike all this busyness, but sometimes Scott puts it to good use. (I particularly enjoyed its deployment in such confidently preposterous actioners as 2005’s Domino and 2006’s Déjà vu). In Unstoppable, the train careening nonstop throughout provides enough of a steady stream of tension that his style here ends up distracting much less than it should.

Speaking of distracting less than it should, the ham-fisted screenplay by Mark Bomback is never afraid to spell out messages in capital letters. Corporations don’t care about people! Rosario Dawson spends the movie in a train control center, sweating out the crisis with safety expert Kevin Corrigan who (irony!) just happens to be visiting this day. She gets on the phone with higher ups (like Kevin Dunn) that are only worried about the bottom line. Repeat. Veteran train engineer Denzel Washington and rookie Chris Pine might have a good idea about how to stop the train. Higher ups don’t listen. Repeat! It’s a good thing the cast has such great charisma and unexpected chemistry. They make their often corny dialogue sound, well, not exactly natural, but somehow simply right.

When the plot ventures outside of the propulsive thrills of that crazy train, the movie is generally out of its comfort zone. Where the movie succeeds the most, though, is in its matter-of-fact moments, portrayals of people at work. It’s something approaching fascinating when the movie takes, even for just a few seconds, a look at the process of how trains work, to simply pay attention to how Dawson, Washington, and Pine are just doing their jobs on a day that happens to feature some particularly harrowing life-and-death decisions.

Where it’s most disappointing is in the cursory family subplots given to Washington and Pine. They’re our main protagonists, but Scott could have easily cut Washington’s two college-aged daughters waitressing at Hooters, especially the uncomfortable scene that cuts from his paternal concern to a close-up of their tight orange shorts. Also easily removed is a vaguely defined subplot about Pine’s estranged family life. Sure, it’s nice to know more about the characters, but not if the information will be dumped into the film indiscriminately. These scenes are just dead weight.

But this is a movie that’s always moving forward. There is always something happening. It may not be something that will be explained, but it will be something exciting, or, failing that, just something loud and frantic. Though it comes with plenty of potential for nitpicking, I must say that this is a fun movie. It’s a kinetic explosion of thrills that barrels along without a second thought given to nuance or meaning. This is cinema that is little more than pleasingly stupid and exciting.

Wednesday, June 24, 2009

Transformers: Revenge of the Fallen (2009)

Despite being based on a line of action figures and a terrible 80s animated series, Transformers was a fast, fun summer movie with satisfying human comedy, a good grasp on its goofy tone, and cool special effects, even if the last twenty minutes devolved into a mess of incomprehensibility. With Transformers: Revenge of the Fallen, Michael Bay has created a film that expands every aspect of his first film, a move that destroys the precarious balance of the comedy, loses sight of the inherent goofiness of the concept, and uses its special effects so often that they become numbing. Not even an intense booming explosion that resonates with a deep bass kick in the climax of the movie could shake me out of my bludgeoned state. I guess the creators thought audiences liked the incomprehensibility the best. The experience of watching the movie is not unlike untangling blinking Christmas lights while listening to all of your dishes fall out of the cupboards.

Once again there are human actors stranded amidst the vehicles that turn into giant robots, but this time they can’t hold their own against the mostly-indistinguishable clanging CGI monstrosities. Where’s someone like Jon Voight or Anthony Anderson from the first movie? They both played the material with just the right amount of winking but are missing here. Why do other similarly lighthearted performers from before – John Turturro, Josh Duhamel, and Tyrese Gibson – get swallowed up by bad writing and self-importance? (Don’t even get me started on Julie White and Kevin Dunn, for whom I’m just embarrassed). Shia LaBeouf and Megan Fox are also in the movie but make so little impact – neither is given any great distinct moments – that they are hardly worth mentioning despite being the ostensible stars of the thing.

The plot involves giant bad robot people who want to find this other big machine to kill humans and the giant good robot people that try to stop them, but even that, believe it or not, takes a back seat to the mindless action that’s little more than militaristic fetishism and rampant misogyny, ethnocentricity, and racism. The only thing Bay’s camera lingers on more than cleavage and explosions are the gleaming weaponry of robot and man alike. All women are either excessively emotional or cold-hearted man-killers (or maybe even robots in disguise). All scenes that take place in foreign countries showcase a startling condescension, using natives for comedic effect or background props and using the basest shorthand for displaying foreign cultures. And then there’s the matter of the two shuffling, illiterate, exaggeratedly incompetent and idiotic, jive-talking Transformers who are practically blackface robots. Need I say more?

I could barely tell the robots apart, could barely understand what most of them were saying, and barely cared about the exposition that both they and the humans were force to spell out. There’s no scene to match the first film’s great comedy of the exposition that reveals the true nature of the Hoover Dam. To say that the script was written with a tin-ear would insult all the great hacks out there who use their tin-ears to competent effect. What went wrong with this script? Two of the writers are Alex Kurtzman and Roberto Orci, who have written fine popcorn flicks like the first Transformers and the great recent Star Trek. I hesitate to lay the blame with them since their record has been so spotless. What about the third credited writer, Ehren Kruger? He’s mostly written horror movies (some of them bad) but I think his influence is felt mostly in the creepy scenes of mechanical intrusions, like when LeBeouf finds himself with an itty-bitty robot crawling up his nostrils. Is the blame then to lie with Michael Bay, who supposedly did some work during the Writers’ strike? It’s possible. Or maybe the script is a result of clashing styles and tones and a rushed schedule which resulted in no ideas being thrown out? It certainly feels at times like a filmed brainstorming session. It’s a total mess.

There are two kinds of Michael Bay movies: dumb fun and just dumb. Can you guess which one this is by now? The movie is everything that is wrong with big-budget sequels. It’s long, formless, and indigestible. It’s scenes of endless noisy nonsense punctuated only by more scenes of endless noisy nonsense, and then it goes on for over two-and-a-half hours. I left with nothing more than a headache.