Alec Nevala-Lee

Thoughts on art, creativity, and the writing life.

Posts Tagged ‘Ridley Scott

Show me the monster

leave a comment »

Godzilla 2014

Over the weekend, I finally caught up with the recent remake of Godzilla. I’d wanted to see this movie for a long time, and although I was aware that a lot of viewers had found it disappointing—especially with regard to Godzilla’s own limited screen time—I was looking forward to watching a big, effects-driven blockbuster that followed what I’ve called one of the cardinal rules of suspense. You don’t show the monster. You let the viewer’s imagination do the work. It’s what Spielberg did in Jaws and Ridley Scott did in Alien. I know all this, and I believe in it. Yet after Godzilla was over, my first reaction was, well, that I wished I’d seen more of the monster. Part of me feels a little guilty even for typing this. Director Gareth Edwards and his production team are obviously harking back to Spielberg, and there’s no question that this approach is preferable to the nonstop pummeling of the senses we get from the likes of Michael Bay. But if we look back at what what Roger Ebert wrote in his review of Roland Emmerich’s own Godzilla remake, we start to realize that the truth is a little more complicated: “Steven Spielberg opened Jurassic Park by giving us a good, long look at the dinosaurs in full sunlight, and our imaginations leapt up. Godzilla hops out of sight like a camera-shy kangaroo.”

So which is it? Would Spielberg want us to show the monster or not? Or to put to put it another way, why does an approach that works for Jaws leave us so dissatisfied with Godzilla? For one thing, there’s the fact that while Jaws leaves its shark offscreen for most of the movie, it spends the intervening time developing a trio of engaging protagonists we’d happily follow on an ordinary fishing trip, while Godzilla kills off its most interesting character before the halfway mark. A director like Spielberg also knows that every delay demands a corresponding payoff: most of the flying saucers in Close Encounters stay out of sight, but when we see the mothership at last, it still has the power to delight the imagination almost forty years later. Godzilla never affords us that kind of cathartic moment, which even a movie like Peter Jackson’s King King offers almost to a fault. More subtly, it’s worth pointing out that most of the films that first come to mind when we think of the power of suggestion, like Jaws or Alien, were forced in that direction out of technical limitations. Not showing the monster is only one of a series of ingenious decisions and workarounds imposed by real constraints, and it’s no surprise if the result is more compelling than a movie that doesn’t need to sweat as hard.

Roy Scheider (and Bruce) in Jaws

But I think the real explanation is even simpler. In Jaws, it makes sense to leave the shark off screen: for the most part, we’re seeing events from the perspective of men on shore or on the boat, fighting an unseen foe, and as long as we stick to their point of view—which makes for good dramatic logic—we won’t see more than a dorsal fin or underwater shadow. The same holds for Alien, which pits its crew against a single murderous creature in a labyrinth of darkness, and even Close Encounters, where the flying objects, by definition, are elusive enough to remain unidentified. But Godzilla is hard to miss. He’s 350 feet tall. This is a creature defined by its overwhelming physical presence, and to keep him out of sight, we need to artificially depart from the perspective of those on the ground. We cut away from the main action or cheat the lighting and the camera angles, so instead of seeing things through a character’s eyes, we enforce a kind of alienation from what the human beings in the story are experiencing. (Having already been entertained but underwhelmed by Pacific Rim, I’m starting to think that any story about two or more really big monsters might be inherently undramatic: there isn’t enough room for action on a human scale when the plot turns on a fistfight between creatures the size of skyscrapers.)

In other words, Godzilla understands the “rule” that it shouldn’t show the monster, but it forgets why that rule has meaning in the first place. Watching it, I felt much the same way I did when I saw Ti West’s The House of the Devil. In that movie, we’re repeatedly shown the heroine moving past dark doorways, and each time she does, our heart rate accelerates—but time and again, nothing happens. And after an hour of establishing the layout of its terrifying house, when the horror finally does come, the film commits the ultimate crime: it cuts away to a room we’ve never seen. Maybe it knows, rightly, that dread is more effective than terror, but it forgets an even more basic rule: if you’re going to tease us with all those shots of a doorway, sooner or later, something has to come out of that door. Godzilla makes much the same mistake, which is only a reminder of the difference between approaching a genre from the outside, even from the standpoint of a loving fan, and figuring out its logic from within, as Spielberg did. Rules, to the extent they exist, are there for a reason, and it can be dangerous, especially for smart storytellers, to honor those conventions with great technical skill while failing to articulate while they’re there in the first place. And as Godzilla proves, you can be a careful, perceptive, and talented director, but still miss the monster in the room.

Prometheus and the perils of secrecy

with 2 comments

I’m tired of secrets. Over the past few years, ever since the release of the teaser trailer for Cloverfield, an increasing number of movies have shifted from the entirely reasonable attempt to keep certain plot elements a surprise to making a fetish of secrecy for its own sake. I blame J.J. Abrams, a talented director and producer who often puts more thought into a movie’s marketing campaign than into the story itself—witness Super 8, which shrouded in great intrigue a plot that turned out to be utterly conventional. Ridley Scott’s Prometheus is perhaps the most disappointing victim of this tendency to date, a movie that comes cloaked in secrecy—is it a prequel to Alien, or isn’t it?—only stand revealed as a total narrative nonevent. (It may not be a coincidence that one of the film’s writers is frequent Abrams collaborator Damon Lindelof, whose Lost displayed a similar inability to deliver on the revelations that the hype had led us to expect.)

Prometheus, to put it mildly, has some script problems. The trouble begins in one of the very first scenes, in which Noomi Rapace and Logan Marshall-Green, as a pair of startlingly incompetent archaeologists, discover an array of remarkable cave paintings at a site in Scotland, only to begin blithely tromping around with flashlights, no doubt destroying thousands of years of material in the process. The paintings, we’re told, are 35,000 years old—the age of the earliest human settlement in Scotland is usually dated closer to 15,000 years, but never mind—and depict a constellation that has appeared in works of art in every human culture, a configuration the archaeologists have confidently identified with a single star system many light years away (the arrangement of the stars in the sky having evidently remained unchanged across thirty millennia). Such plot holes are far from unusual in a big summer movie, of course, but none of these issues make us especially optimistic about the quality of the story we’re about to be told.

Our concerns are not without foundation. Rapace and Marshall-Green end up traveling on the most casually organized interstellar voyage of all time, a trillion-dollar project whose members not only haven’t been told the purpose of the mission, but haven’t even met yet, or been told anything about the chain of command, before awakening from hibernation on their arrival. Upon landing, they do, in fact, make the greatest archeological discovery in human history, stumbling at once on the remains of a massive alien civilization, a result which is somehow seen as disappointing, because none of the aliens there are still alive. (This is after a single day of exploration at one random site, which is sort of like aliens landing at Chichen Itza at night and bemoaning the fact that the humans there have gone extinct.) But of course, there is life here, of a particularly unpleasant kind, and Prometheus soon turns into something less than a coherent horror movie than a series of disconnected ideas about scenes it might be cool to have in an undeclared Alien prequel.

In interviews, Scott and Lindelof have spoken about the supposed profundity of the film’s ideas, and their decision to leave certain elements unexplained, with a nod toward such works as 2001: A Space Odyssey. But 2001, for all its obscurities, gives us the pieces for a perfectly straightforward explanation, which the novel makes even more clear, while Prometheus consists of such ill-fitting parts that any coherent reading seems impossible. There are occasional pleasures to be found here: Michael Fassbender is particularly good as an android who draws his personal style from Peter O’Toole’s Lawrence of Arabia, and there’s one nifty scene involving Rapace, an automated medical pod, and a particularly traumatic surgical procedure. For the most part, however, the astronauts are such idiots that one finds oneself missing the cult of of competence that James Cameron brought to Aliens. And that’s the heart of the problem. If we had characters that we cared about, the movie’s incoherencies wouldn’t matter. Because in the end, I don’t want answers. I want Ripley.

Written by nevalalee

June 11, 2012 at 9:50 am