Showing posts with label Paramount. Show all posts
Showing posts with label Paramount. Show all posts

Sunday, June 23, 2013

World War Zzzzzz...

What does $200 million of Paramount’s money get you these days?  Certainly not a fantastic Star Trek movie – that was proven last month.  World War Z proves that it can buy you a gaggle of screenwriters, if you define a “gaggle” as five or more.  The completed movie, however, proves that said gaggle of screenwriters can’t guarantee you an interesting, much less coherent, screenplay.

It’s been said that when a popular genre reaches a point where filmmakers are producing comedies or parodies of it, that’s a sure sign the genre has all but “played out.”  While World War Z may not be a parody (Warm Bodies, from earlier this year, would better fit that bill), it’s at least a sign that the zombie genre is almost dried up from a dramatic viewpoint.  If the old saying about too many cooks spoiling the broth is relatable to filmmaking, then a slew of names under the “written by” credit should be taken as a cause for concern.  Brad Pitt’s production company won a bidding war five or six years ago for the rights to Max Brooks’ (son of Mel) novel about the oral history of a worldwide zombie pandemic.  Of course, this film bears no resemblance whatsoever to that novel, outside of its title and the fact that there are zombies in it, but Hollywood knows best, so out goes all the introspective, human stories and in goes swarms and swarms of computer-generated zombie termites, crashing helicopters, artillery fire and nuclear explosions.  Heaven forbid should somebody make a movie about people describing their experiences in such a fantastically terrifying time as a zombie apocalypse – nobody would want that, right? 

Pitt cast himself in the lead role, that of one Gerry Lane (a name which, for some reason, planted a Beatles’ song in my head and never let it go), who before his recent retirement, was some sort of go-to investigator-type guy for the United Nations at one point, although the movie doesn’t bother explaining any more than that to us.  He, his wife and two daughters manage to escape Philadelphia, by way of Newark, as the pandemic breaks out, narrowly and miraculously avoiding swarming death several times before being rescued and taken out to a helicopter carrier which serves as… Oh, screw it.  None of it matters, because you’ve seen all this before!  Did you see 28 Days Later?  Then you’ve seen this.  Did you see the pilot episode of “The Walking Dead?”  Then you’ve seen this.  The filmmakers have spurned a totally original take on the zombie-movie provided to them by the source novel for which they paid an astronomical sum of money, and instead chosen to make a zombie flick as they imagine Roland Emmerich might have.

Okay, sure, the zombies here evoke “hive” or “swarm” behavior, similar to flocks of birds or colonies of insects, presaged by images of those creatures in the opening credits.  This could be construed as slightly different from some other zombie flicks, but why do they behave this way?  Well, not only is that never explained, we’re also never even given a hint about what actually started all of this.  Oh, sure, there are couple lines of dialogue about somebody biting a doctor in Korea, and the Indian Army “fighting the undead,” but those plot points are never explored.

Gerry’s wife and kids? What about them?  They’re nothing more than a plot device, giving Gerry a reason to call back to the command ship and serendipitously get information that leads him to the movie’s next CGI-created set-piece.  Heck, for all we learn about those characters, “wife and kids” is really all the identification they require.  When a senior military official refers to them as “non-essential personnel” at one point, I wondered for a second if it was meant as a joke.

Why Brad Pitt would be so devoted to such a project that he would throw a good chunk of his own money at it sort of baffles me, too.  Don’t kid yourself, folks – Pitt considers himself a “serious” actor, and maybe with exception of Troy, has never done the “summer blockbuster” movie before.  What’s even more baffling is how the movie we finally get to see is a lot LESS a spectacle picture than was originally intended.  The final forty minutes of the movie are a complete rewrite/reshoot, eliminating a third act that would have centered around a massive zombie battle all throughout Moscow (a good portion of which was actually even filmed, but now won’t see the light of day) into the more intimate, thriller-type ending we get now.  I’ve read of how the original ending played poorly with test audiences, as well as Paramount executives, and how screenwriter Damon Lindelof, the man who made such an absolute mess of the Prometheus script last year, was brought aboard to formulate a new ending.  While that ending is the most zombie movie-like story arc of the entire film, it’s too little/too late by that point.  We’ve learned so little about Gerry, much less the characters who inhabit the medical research facility in which he finds himself, that it’s hard to feel much dread over what possible horrible fate may await him.

I’ve said in some previous review that once you’ve seen one zombie movie, then for the most part, you’ve pretty much seen ‘em all, and that remains so.  Given that semi-debatable fact, the only thing that can differentiate one zombie flick from another is the stable of characters inhabiting the story.  Since I really don’t know any more about Gerry Lane, his wife and/or his kids at the end of this movie than I did at the beginning, much less any cause for the pandemic, was their any point in my seeing it, other than to see that Paramount was willing to spend $200 million to convince me zombies can clickity-clack their teeth and swarm like ants…?

Monday, May 20, 2013

"Star Trek Into Darkness" is just light enough for fun.


It’s not so great a feeling to walk into a theater to see a flick and find yourself becoming mentally prepared to be disappointed, but I must admit to just such a situation this past weekend when going to see Star Trek Into Darkness.  The Star Trek reboot four years ago was a little fun, but with some of the heresy director J.J. Abrams committed upon Star Trek canon, and all that God-awful lens-flaring to which he subjected us, I wasn’t really yearning for the sequel at first.  Well, maybe “heresy” is perhaps a strong word, but it’s the first one to come to mind.  Anyway, as I began to see the promotional materials and teaser trailers over the last several months, and being blown away by some of the visuals, I found myself looking more and more forward to seeing his next attempt at the Star Trek universe.

The pre-title sequence, with Kirk and McCoy fleeing some pursuing primitives while Spock becomes trapped in an erupting volcano, didn’t do much to allay my fears that I’d be disappointed in the movie, though.  Sure, the very Raiders of the Lost Ark-esque chase scene is quite well-crafted, but it almost immediately conveyed to me that Abrams still didn’t “get it” (damn it, Federation Battle Cruisers CAN NOT make landfall!!!).  It had enough hectic and funny banter and interplay amongst the characters, however, that I found myself getting past the details and getting caught up in the movie pretty quickly. 

The movie has the reckless feel of some of original series episodes where Kirk showed his rashness and selective disregard for authority, as the first film did, but the rebelliousness seems to be less for its own sake in this film, and in that sense is an improvement on the previous film.  The Prime-Directive-be-Damned attitude for which Original-Series Kirk was so beloved is in full-force here, and while we do get to see a little bit more consequence of his actions, it’s still not as much as there SHOULD be.  This character trait is the one that Chris Pine seems to enjoy portraying the most, with his smirk-and-narrow-eyes being dished out in Shatner-like proportions.  It’s also the facet of Kirk’s personality that sets the movie’s events in motion.

I won’t delve into plot details too much for fear of inadvertently dropping spoilers, and there are so many to avoid revealing that I hope I can still convey to you that I did enjoy the movie and recommend that you see it.  Into Darkness shamelessly steals plot elements from a few different points of Star Trek’s past, namely some shady forces attempting to instigate a war with the Klingons and a certain villain who turns out to be more than meets the eye.  All of our favorite characters are back, and all have enough to do that their presence doesn’t feel like glorified cameos. 

Seeing these characters interact is the best thing about it, even more so than the previous film.  The casting of all these actors is spot-on, and their preparation and attention to detail is evident.  There were several instances of some combination of each or all three of the lead actors being onscreen when I found myself thinking of Shatner, Nimoy and Kelley, as the body language of Messrs. Pine, Quinto and Urban is all so very perfect. 

On the other hand, not every character harkens back to the original - Simon Pegg’s portrayal of Scotty is done to such a hyperactive level that James Doohan himself might not even recognize the character anymore (if he were still with us, that is…).  The rebooted version of Dr. Carol Marcus didn’t even really seem to serve much purpose here, either, other than to provide an opportunity for Kirk to see her in her undies and possibly plant the seed for him to… er, plant the seed… in the next movie.

After praising the casting, though, I must wonder about the logic of John Harrison’s ethnicity and accent without putting so much detail to this question as to reveal a vital plot point.  Watching any movie requires a certain amount of suspension of disbelief by the audience, but the level of that suspension should not be too great, and if a film attempts at least a token explanation of some illogical point, most folks would probably buy it and move along.  Sadly, Abrams’ screenwriters didn’t even attempt to explain why we’re supposed to accept Benedict Cumberbatch as “Harrison,” and that one point of logic nagged me enough that it took me out of the movie for a few moments.  

The movie is a visual treat, too.  The actions sequences, and there are plenty of ‘em, are technical marvels to be sure, and while Abrams’ penchant for filling the screen with debris and an almost pornographic level of mass destruction continues from the first film, thank God he throttled back on the lens-flare somewhat!

Star Trek Into Darkness is a funny, involving and entertaining popcorn-flick that is very enjoyable in the moment, but I don’t think it as good as the first three or four movie adventures of the original cast.  Abrams expends a lot of effort in giving us “Easter eggs” that remind us of moments from the series’ previous iteration, so much so that his version almost doesn’t seem to be moving in an original direction.  Given his public admission that he was never as enamored of Star Trek as he is with Star Wars, one might hope that his taking over the Star Wars franchise will mean the next Star Trek film might be made by someone who has some interest in creating an entirely original story for these characters to inhabit.

Oh, and as a side note - it’s certainly a relief that San Francisco won’t be destroyed for another 250 years, since I’d very much like to see it before all of Telegraph Hill is overtaken by the Starfleet Campus…