Showing posts with label Alex Kurtzman. Show all posts
Showing posts with label Alex Kurtzman. Show all posts

Tuesday, June 13, 2017

Dead on Arrival: THE MUMMY



Every few years, Universal decides to do something with its roster of classic monster movies – Dracula, Frankenstein, The Wolf Man, and so on – beyond rereleasing the original 30’s and 40’s films on whatever new home video format has arisen since the last time. Lately that means we get 2010’s Wolf Man and 2013’s Dracula Untold, attempts to make new effects pictures out of the old creatures, and maybe even spark a new franchise along the way. Now this had led to The Mummy, the newest attempt to make a whole monster mash adventure series on the solid foundation of hoary old horror tropes. Hey, it worked in 1999 when Brendan Fraser headlined a charming, good old-fashioned Indiana Jonesy period piece action serial about dodging undead Egyptians and their various mythological curses. This time around, in addition to some archeological creepiness the premise requires, director and co-writer Alex Kurtzman (who has had a hand in screenplays for a half-dozen franchises) makes a picture that is a modern Tom Cruise movie, which means it’s at least as interested in hurtling action as it is any simmering supernatural suspense. The movie opens on the star fighting ISIS for control of an ancient Mesopotamian burial site where evil incarnate waits hidden beneath a pool of liquid mercury. Once out, the long-dormant mummified witch (Sofia Boutella, an acrobatic and comitted highlight) will inevitably unleash havoc. That’s enough for a good time, at least until the whole enterprise – growing thinner and duller by the sequence – thoroughly wears out its welcome well before the finish line. And they want to make more of these? Hopefully they’ll be improving as they go.

The main problem with this movie – which has a grinding workmanlike competence to the expected pattern of hectic, noisy collisions of conflict punctuated by droopy exposition spouted by famous faces – is how schematic it is. You can see all too transparently the contract negotiations, marketing decisions, franchise planning, and formulaic plotting on screen. It gives Cruise reasons to take off running from explosions, get into rollover accidents, and smirk at his colleagues before getting likably pummeled. It also has Russell Crowe show up and call him a young man, despite Cruise being two years older (a neat showbiz trick). Crowe is here playing Dr. Jekyll, a clear tip of the hat to a brewing monster meetup in the planned future installments, what with his laboratory with Creature from the Black Lagoon flippers and vampire skulls floating in specimen jars. The film also gives Cruise his usual bantering love interest/professional rival (Annabelle Wallis) and comedic sidekick (Jake Johnson). The script never successfully turns all this into real characters or clear motivations or easily comprehendible MacGuffins, settling for just moderately diverting nonsense and the inexorable pull of blockbuster spectacle sequence-hopping logic. There’s no sense of escalation or danger or invention, just dutifully hitting the marks. 

A constant churn of action works in the exceedingly excellent Mission: Impossible series (probably the most consistent franchise Hollywood currently has running), but those movies use Cruise’s hardworking, hard-charging action demeanor in a series of escalating and cleverly deployed stunts and creatively twisty heist plots. Here it’s just lumpy, car chases and plane crashes and shootouts and howling effects jolting a half-hearted Mummy-stalking feature into the shape of a generic summer movie. In the context of a theoretically spooky monster movie, dripping with zombies and ancient curses and a “who-is-possessed-and-unwittingly-prepared-to-channel-an-evil-Egyptian-god?” plot engine, it starts to feel like two competing ideas smashed unsuccessfully into one. The better idea is the Cruise vehicle, where his charisma and star power can carry along a thin character, and his effortlessly effortful forward momentum can paper over leaps of logic and plot holes big enough a supernatural sandstorm can be seen through them. The lesser idea, alas, is the one that wins out in the end, weakly hitting rote monster beats while hedging its bets, teasing future story and failing to live in the moment long enough to give us a movie worth watching in the here and now. There’s just barely enough for an only mildly disappointing brainless night at the movies, but it’s certainly not enough to crave more.

Friday, May 2, 2014

Caught in a Web: THE AMAZING SPIDER-MAN 2


What makes Spider-Man fundamentally engaging and enjoyable is his relatable humanity. Peter Parker is just a normal young guy with real problems with family, school, girls, and employment. That provides a ground-level rooting interest that’s a more direct emotional appeal in all his action sequences than in all the boring climactic near-apocalyptic scenarios that pervade the superhero genre. That’s what I found most charming about The Amazing Spider-Man. With Andrew Garfield the reboot’s filmmakers found, like Sam Raimi found in Tobey Maguire for their superior films, a likable guy. Even if Peter didn’t always do the right thing, you knew the decisions pile up and weigh on him without getting in the way of the high-flying fun of being Spider-Man. What was most refreshing about that retelling of Spidey’s origin story was its relatively self-contained narrative. It didn’t seem to be spending too much of its time teasing future installments or leaving storylines conspicuously hanging at loose ends like so many superhero movies do these days. It simply found good performers in a narrative that had a beginning, middle, and end.

But when it comes to The Amazing Spider-Man 2, the charm of a complete story has been entirely thrown out. It consists of 142 minutes of scenes – some better than others – that never cohere. The whole production exists for the moment, chasing a this-happens-then-this-happens high where everything is pitched at a consistent level of spectacle and import. I thought of Ebert’s criticism of Michael Bay’s Armageddon as a feature-length trailer. The problem is, this Spider-Man isn’t just cut together like its own highlights. It’s cut together like a teaser for its own sequel. It’s all color, noise, and shapeless plot, stuffed full of subplots and character introductions foreshadowing and previewing where the studio would like to take this franchise in the future. As a result, the movie plays out busily with much happening, but little impact. There’s no clear through-line. Narrative, character, theme, and style exist in a haze, constantly threatening to take shape, but never getting there.

To even briefly summarize the plot seems a losing proposition. Instead I’ll describe some of the variables bouncing around. Peter (Garfield) is on-again-off-again with the lovable Gwen Stacy (Emma Stone, continuing her appealing performance from the first movie). He’s also trying to hide his superhero identity from sweet Aunt May (Sally Field). Meanwhile, the heir to the CEO throne of the omnipresent and obviously menacing Oscorp Industries, Harry Osborne (Dane DeHaan), skulks about looking to cure his mysterious hereditary ailment. A dweeby and unjustly ignored scientist (Jamie Foxx) gets electrocuted and then falls into a tank of genetically altered eels, an experience that leaves him blue, translucent, able to manipulate energy, and has rattled his brain in a way that leads him to decide he’s a supervillain and take the name Electro. He must know he’s in a superhero movie. The rest of the movie is filled with bit parts for the likes of Paul Giamatti, B.J. Novak, Felicity Jones, and Sarah Gadon, all clearly sitting around hoping they get to play more important roles in a future installment.

Director Marc Webb, with cinematographer Dan Mindel, shoots it all clearly and colorfully, juggling the plotlines as best he can. It’s all broad and comic-booky, with cartoony fluidity to the bright special effects and shots of action that twist gymnastically around Spidey in sometimes-exciting ways. But it is when Webb gets the chance to narrow in on the human relationships that the movie works best. The scenes are not particularly well written, but Garfield and Stone continue to have nice chemistry and manage to have a believable romantic spark as they juggle their lives individually and together. He’s a freelance photographer and Spider-Man. She’s an Oscorp intern and wants to go to Oxford in the fall. The question of what their future looks like, and whether they’re a couple beyond the present, is treated with some gravity. It works only because the performances are convincing.

Garfield is enjoying himself, creating a Peter Parker who is having so much fun being Spider-Man, swinging down New York City skyscrapers and wisecracking with bad guys, that darker shadings of grief and mystery almost don’t have room to stretch out comfortably. Stone, for her part, is even better. Not just a prop or an object to be rescued, she holds her own. Smart, she helps think Spidey’s way out of a number of predicaments, and is her own independent-minded person. It’s a shame that she has to reenact one of the source material’s most famous plot developments, a decision that turns her into yet another female character we’re only supposed to care about because of how what happens to her makes the male lead feel.

But it’s not just her. Alex Kurtzman and Roberto Orci’s screenplay makes the wrong moves by having every character and event become simply an overtly reverential and referential signpost on the way to the next spectacle, moving the pieces and gears into place for the next installment instead of becoming a wholly satisfying story of its own. (That Kurtzman/Orci scripts have sometimes made this a bad habit is not encouraging. I went into the film unaware of its writers and when their credit appeared I groaned and thought “makes sense.”) If I’m being charitable, the movie is an accidental post-narrative experiment. If I’m not being charitable, it’s desperately laying track just ahead of a franchise barreling down a route-in-progress. Either way, the flop sweat starts to show. It leads to a wobbly tone and confused plot.

Take Jamie Foxx for example. He’s delivering an amused big, campy performance that appears to belong in a different movie. Electro is a jumble of shifting personalities, goofy jealousies, and legitimate complaints, not to mention some serious-minded hints of metaphoric marginalization that remain largely inactive, all mixed into one convincingly weird persona. His scenes rise to match his nutty intensity and scattered evolution. I thoroughly enjoyed his scene opposite the exquisitely named Dr. Ashley Kafka (Marton Csokas), a man with a thick German accent who captures Electro in an Oscorp-funded insane asylum’s contraption that looks like a rubber body suit welded into a giant circuit board suspended over a hot tub. (Why would such a thing even exist other than to accommodate the plot of a superhero movie?) It’s a scene that feels one or two notches away from pure comedy.

But it is hard to square that tone with what we see elsewhere. We get straining emotional scenes of Dane DeHaan brooding with intensity in a heightened sickly torment that nearly breaks past the quick and dirty token characterization given to him. There is light relationship comedy, intimations of fatherly secrets for Spidey and Osborne alike, an opening phony-baloney plane crash flashback, a concluding manipulative little-kid-in-danger scene, a perilous blackout, a couple of winking references to the sadly still-unseen J. Jonah Jameson (the best of all Spider-Man supporting characters), and a funeral. It’s a sequel that does so much, it ends up feeling like nothing at all. I didn’t exactly have a bad time, but its diverting qualities are fleeting and its frustrations linger.

Friday, May 17, 2013

Top Warp Speed: STAR TREK INTO DARKNESS

Undoubtedly the most breathless of all Star Trek pictures, Star Trek Into Darkness is a nonstop barrage of spectacle, movement, and noise. It’s manipulative, relentless and a fun time at the movies. It gets the job done. With 2009’s Star Trek, director J.J. Abrams got a great deal of entertainment value out of dropping a wormhole into Trek continuity, scattering the familiar pieces every which way and providing a shock of delight as the pieces snapped back into place. It’s about as clever as a combination sequel, prequel, reboot, and remake of a nearly 50-year-old franchise could be. While Into Darkness can’t have the same pleasurable jolts of fresh perspective, what it lacks in discovery it makes up for in chemistry. The cast crackles through energetic banter and terse exposition as they’re forever running up and down the gleaming corridors of the starship Enterprise, desperate to solve the latest crisis in which they’ve found themselves.

With a plot that’s in some ways an extended riff on a classic bit of Trek – to even say whether it’s a movie or a TV episode would probably be enough for Trekkers to spring the film’s secrets sight unseen – the screenplay by longtime Abrams collaborators Roberto Orci, Alex Kurtzman, and Damon Lindelof is packed with dramatic incidents and fan-friendly winking. It’s an expertly calibrated event picture that hurtles from one bit of action or humor into the next without any room to slow down. We start urgently in the middle of a high-energy action sequence with Captain Kirk (Chris Pine) and Dr. McCoy (Karl Urban) fleeing an angry alien tribe while Spock (Zachary Quinto) proceeds logically into a volcano to shut it down and save this foreign world. As the sequence plays out, all of the returning cast – Zoe Saldana’s Uhura, Simon Pegg’s Scotty, John Cho’s Sulu, and Anton Yelchin’s Chekov – get their little moments to shine. It’s like stumbling into the last few exciting minutes at the end of an episode and then sticking around for the next couple in the marathon. There’s recognizability and comfortability the cast has in the roles and with each other that provides an instant anchor and funny rapport amidst the chaos around them.

Chaos quickly comes in the form of a terrorist attack on Earth that blows up a Starfleet base in London. The man responsible is John Harrison (Benedict Cumberbatch), one of their own who clearly has his secret motives for turning against them. The scheming scenes leading up to and including these surprise attacks have a scary edge. As the film progresses and Cumberbatch gets to put his sonorous voice into full intimidating villainy, the relationships his character develops take a few interesting twists and turns. Meanwhile, back at Starfleet, the good admiral (Bruce Greenwood) and crusty admiral (Peter Weller) agree to let Kirk take the Enterprise after the attacker in a rare show of force from this research and peacekeeping group that finds a new science officer (Alice Eve) escorting top secret missiles on board. They’re not out boldly going where no man has gone before. They’re on a manhunt.

This streamlined feature slams through its sequences of energetic intensity with sensational special effects and top-notch sound design expected from a Hollywood blockbuster in this budget range. Abrams, not particularly invested in the more cerebral, allegorical aspects of Trek lore, sees fit to deliver a slam-bang spectacle with phaser battles, whooshing warp drives, and brusque threats around every corner. This leaves plenty of time for the film’s politics to be a little muddled, if benign, with the exception of a weirdly misjudged bit of disaster overkill in the final stretch. It’s one thing for a movie like this to destroy a chunk of a metropolis, sending skyscrapers crumbling to the ground. It’s another thing entirely to do so almost off-handedly, skip the aftermath, and then put a strange title card in the end credits proclaiming tribute to post-9/11 workers. (Seriously, what’s going on there?) It’s a film that summons up War on Terror paranoia (potential drone strikes, brief pointed debates about killing terrorists without trial) and twisty conspiracy theories, but uses it only as set dressing for a plot that’s all present tense forward movement. Gone is the Cold War-era utopian optimism of Roddenberry’s original concept. This time it’s all about fear, dread, and explosions.

But it’s amazing how far momentum alone can take you. Abrams has made a film that’s a crackling roller coaster that’s all dips, dives, drops, and top-speed loops with an excellent, blaring score from the ever-reliable Michael Giacchino. The intensity never slows, even when the movie self-consciously incorporates a debate with itself about what kind of mission this Trek is following. “This is clearly a military operation,” Scotty disappointedly tells Kirk. “Is that what we are now? I thought we were explorers.” The fact of the matter is that Trek on TV had room to be as eggheaded as it wanted (at best, thrilling so), whereas the movies have always largely been about elaborate revenge schemes and potentially world-ending super-calamities. This just happens to be a particularly single-minded action adventure that’s constantly chasing the next thrill. And that works.

It works not just because Abrams and crew are skilled technicians, but because of the people on screen as well, with characters filled wonderfully by the talented cast working from borrowed cultural awareness without much original characterization in this particular script. (There’s an assumption, rightly or wrongly, that the audience will know who these characters are and what they mean to each other, so that all emotional development can be left to shorthand.) These characters have lived long and prospered in the cultural imagination for a good reason. The core of the film is the crew, the group of professionals thrown together by duty, bound together by the friendships that developed. Even at their prickliest, when Kirk and Spock speak sharply to each other, engaging in their expected debate between reason and emotion, there’s a core of respect and love that’s a comfort and a constant, even when everything is constantly blowing up around them.

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.