Posts Tagged ‘Lawrence Kasdan’
Revenge of the list
Note: A few minor spoilers follow for Star Wars Episode VII: The Force Awakens.
When I try to explain my mixed feelings about the new Star Wars movie, I find myself turning, heretically, to a story about the franchise’s greatest rival. Nicholas Meyer was, in many ways, the J.J. Abrams of his day: a hugely talented, relatively young outsider who was brought in to correct the course of a series that had lost its sense of purpose. He wasn’t a Star Trek fan, but he was able to find elements—like its echoes of the Horatio Hornblower novels—that he could highlight and enlarge. When he signed on to write and direct the first sequel, however, five separate scripts had already been written, and he had to prepare a workable screenplay in twelve days. His response to the challenge resulted in one of my favorite Hollywood anecdotes ever, as Meyer recounts it in his memoir The View From the Bridge:
“Well, here’s my other idea,” I told them, taking a deep breath and producing a yellow legal pad from under my chair. “Why don’t we make a list of everything we like in these five drafts? Could be a plot, a subplot, a sequence, a scene, a character, a line even…And then I will write a new script and cobble together all the things we choose…”
We then made the list. It included…Khan (from the “Space Seed” episode…); the Genesis Project (creating planetary life); Kirk meeting his son; Lieutenant Saavik (Spock’s beautiful Vulan protégée); the death of Spock; and the simulator sequence…All these materials were culled higgledy-piggledy from the five different drafts that I never—to the best of my recollection—consulted again.
Longtime readers of this blog will know that I never tire of retelling this story, both as an illustration of the power of lists as a creative tool and as a reminder of how surprising, organic narratives can emerge from the most artificial of beginnings. And it’s as true today as it ever was. In the excellent bonus features for Mission: Impossible—Rogue Nation, Christopher McQuarrie says that they began writing the movie with a list of action set pieces, and that important emotional beats—including Ilsa Faust’s motivations and the entire character of Attlee—emerged when they put those scenes in a certain order. Matthew Weiner and his core writing staff assembled a list of possible themes and ideas to revisit when it came time to plot out the final season of Mad Men. In the last few months alone, we’ve seen The Peanuts Movie, of which I wrote: “[It] sometimes plays as if it had been written according to the model that Nicholas Meyer used when cracking The Wrath of Khan…The result is an anthology, gracefully assembled, of the best moments from the strip and specials.” And now, of course, we have Star Wars: The Force Awakens, which struck me when I first saw it as a kind of greatest hits collection from the original trilogy, only to have this confirmed by the same Wired interview with J.J. Abrams that I discussed yesterday: “When we began working on this film, Larry [Kasdan] and I started by making a list of things that we knew held interest for us, the things we wanted to see, the things we felt were important.”
Yet the fact remains that The Wrath of Khan comes off as a seamless burst of pure story, while The Force Awakens, for all its considerable merits, still feels like a list. (The best thing that could be said for it, and this shouldn’t be lightly disregarded, is that it’s the right list. ) When you look at the list that Meyer put together for Star Trek, with the notable exception of Khan himself, you see that it consists of ideas that audiences hadn’t seen before. The Force Awakens, by contrast, is a list of things that are familiar, and once we’ve seen a couple of moments or images that remind us of the original movies, we naturally start a mental checklist as we keep an eye out for more. Sometimes, the way it quotes its predecessors is delightful; at other times, as when it gears up for yet another aerial assault on an impregnable planetary superweapon, it’s less than wonderful. As the Resistance prepared for the attack on Starkiller Base, I felt a slight sinking feeling: two out of the first three Star Wars movies ended in exactly the same way, perhaps as a nod to The Dam Busters, and I hoped that Abrams was about to spring some kind of novel twist or variation on that theme. Obviously, he doesn’t, to the extent that he includes a story point—a small group on the ground fighting to deactivate the shield generator—lifted straight from Return of the Jedi. It isn’t hard to imagine a version of this sort of climax that would have given us something new: I’d love to see a full-on Saving Private Ryan sequence showing an infantry assault on the base, or even a naval battle. And if we didn’t get it here, it’s because Abrams and the rest were sticking closely to their list.
But this kind of respectful homage is utterly alien to the spirit of the original movies themselves, which were eager to show us things that we had never imagined. The opening scenes on Hoth in The Empire Strikes Back, for instance, immediately expand the possibilities of that universe: not only does the ice planet give us a gloriously different backdrop, but the battle with the Imperial Walkers feels like a deliberate inversion of the dogfights that ended the first movie. The entire film, in fact, plays like a deliciously inverted list: it takes the things that audiences loved about Star Wars and then turns them all by a hundred and eighty degrees. The Force Awakens lacks that kind of basic invention, as much I liked so much of it. (Among other things, it makes it unnecessary to watch the prequels ever again. If Disney follows through with its plans of releasing a movie of comparable quality every year, Episode I, II, and III will start to take on the status of The Sting II or Grease 2: we’ll have trouble remembering that they even exist.) It’s possible that, like the first season of Fargo, the new movie’s energies were devoted mostly to establishing its bona fides, and that the next batch of sequels will be more willing to go into unexpected directions. Still, the fact remains that while Abrams and Kasdan made a great list, they failed to add anything new to it—which raises the troubling implication that the galaxy of Star Wars, after six films, isn’t as vast or rich with potential as we always thought it was. I hope that isn’t the case. But now that Abrams and his collaborators have gotten that list out of their system, the next thing they need to do is throw it into the nearest trash compactor.
Indy movies
On Saturday, my wife and I spent seven hours at the River East theater in Chicago, watching a marathon of the Indiana Jones movies, which I still insist on calling a trilogy, in advance of their release tomorrow on Blu-ray. It wasn’t the first time I’d seen all three films on the big screen—I spent a wonderful day watching them all at the sadly departed UC Theater in Berkeley over a decade ago—but it had been a long time since I’d seen them from start to finish. The experience, I’m happy to say, was close to perfect: the digital prints were gorgeous, the crowd was large and enthusiastic, and the movies were as satisfying as ever. And the fact that we left before Kingdom of the Crystal Skull doesn’t diminish my appreciation for what the original trilogy achieved. Like everyone else, I’m critical of George Lucas: he remains, as David Thomson notes, the saddest of moguls, and his career over the last twenty years has consisted of one long retreat. And yet with these three films, he shaped and enriched my inner life more than any other filmmaker, and for that, I’m forever grateful.
Of the three, Raiders is by far the most cinematically exciting: it was made when Steven Spielberg was still only thirty-four, with the greatest natural eye in movie history, and the result is dazzlingly assembled—it may be his most technically thrilling film of any kind. A great deal of this can be credited to the screenplay by Lawrence Kasdan, which pulls off the difficult job of moving between set pieces conceived by the director and producer while lavishing every scene with ingenious and delightful beats. (Even so modest a sequence as the “bad dates” scene is a small masterpiece of acting, writing, editing, and direction.) The script for Temple of Doom, by Willard Huyck and Gloria Katz, is far more problematic, and the connective material is considerably less graceful, but the big set pieces—the opening sequence in Shanghai, the spike room, the mine car chase—reach dizzying heights. By comparison, the action in Last Crusade is competent, inventive, but less divinely inspired, and there isn’t an action sequence here that really holds up with the best of the first two movies.
Yet Last Crusade has always been my favorite of the three, and one of my favorite movies of any kind, which gets at a very important point: these films aren’t about action or special effects, as fine as they may be, but about a certain spirit, a promise about the kinds of experiences and adventures that the movies can offer us, and Last Crusade captures that spirit perfectly. It’s both endearingly innocent and highly sophisticated, and it expresses, as Truffaut would have said, both an idea of life and an idea of cinema—and the fact that the ideas are straight out of a boy’s book of adventures doesn’t make them any less moving or less true. Looking back, I’ve begun to realize that it’s as responsible as any movie for the direction my own life has taken: I saw it when I was about ten years old, and it was arguably the first in a sequence of books, movies, and television shows that convinced me that I wanted to tell stories for a living. Other movies have since become more important to me, and I fully see its limitations, but few works of art have ever seized my imagination in quite the same way.
And its spirit is one that I’ve been trying to recapture in my own work ever since. One night after college, I was watching Temple of Doom with my family when I dozed off near the end and awoke as the closing credits began to roll. Somehow, in that moment between sleep and waking, I heard something in the score by John Williams—it’s the unbearably beautiful theme that appears in “Slave Children’s Crusade”—that I’d never heard before: it seemed to crystallize, in a few bars of music, everything that I hoped to accomplish as a storyteller. My first novel, a long adventure story set in India, may have been my subconscious effort to work out that one moment of dreamlike inspiration. And while that novel remains unpublished, one of the great challenges I now face as a writer is gradually nudging my work back to that theme, which has been reduced to a subtle, almost imperceptible note in my published novels and stories. I’m still trying to figure out what shape it will take. But it’s there. And I have a hunch that Indy will be the one to show me the way.
Quote of the Day
If you’re passionate about your work, you can get almost anything made.
George Lucas: Writer of a Lost Art
As long as we’re on the subject of beloved artists who experienced a marked decline in quality, let’s talk about…George Lucas. (Because, obviously, no one has ever discussed this before.) I’m not going to go into all the ways that Lucas’s recent work has been disappointing—you have the entire Internet for that—but I do think it’s important to highlight the ways in which Lucas was, at his best, a remarkable writer.
Exhibit A is the famous transcript, which appeared online last year, of an early story conference for Raiders of the Lost Ark. (You can find a nice clean copy here.) Seated around a table with Steven Spielberg and Lawrence Kasdan, Lucas spins out one idea after another, laying the groundwork not only for Raiders but for the entire Indiana Jones series. The whole transcript is worth a look, but there are a few particular moments that are especially valuable. Here’s Lucas on the importance of a structured plan, and the usefulness of making lists:
In the end I want to end up with a list of scenes. And the way I work generally is I figure a code, a general measuring stick parameter. I can either come up with thirty scenes or sixty scenes depending on which scale you want to work on. A thirty scene thing means that each scene is going to be around four pages long. A sixty one means that every scene is going to run twenty pages long…I have a tendency to work rather mathematically about all this stuff. I found it easier and it does lay things out. Especially a thing like this.
(The process might sound mechanical, but in my own experience, nearly all complex narratives begin in a similar way: you start with ideas for a certain number of scenes, and know you’ll need a certain number of chapters, so you do your best to make the two numbers fit.)
On plausibility:
The trouble with cliff hangers is, you get somebody into something, you sort have to get them out in a plausible way. A believable way, anyway. That’s another important concept of the movie—that it be totally believable.
On the proper use of backstory:
We’ve established that he’s a college professor. It doesn’t have to be done in a strong way. It starts out in a museum. They just call him doctor this and doctor that. We can very easily make that transition, and very quickly establish that whole side of his character. [Italics mine.]
Finally, this wonderful moment:
Spielberg: One thing you should do—He’s on this airplane. There are about four or five passengers around him. He’s asleep and these passengers are looking at him. We don’t know why. They they all get up and put on parachutes, and they jump out the door. He wakes up when he hears the door open, and realizes he’s all alone. The door to the cockpit is locked. The airplane begins to go into a spin. He’s trapped in this airplane and it’s going down. The whole thing was a set up. That’s a great cliffhanger, to see how he gets out.
Lucas: That’s great. Then what happens? One sentence further and it’s a great idea. [Italics mine, of course.]
So what happened between Raiders of the Lost Ark and Kingdom of the Crystal Skull? The simplest answer: for Raiders, Lucas was working for a studio. For Crystal Skull, he was the studio. Raiders was made under a surprising number of limitations—Spielberg had just come off the notorious flop 1941, and was anxious to prove that he could deliver a movie on time and under budget—while Crystal Skull had no limitations at all. And without limitations, as I’ve pointed out before, an artist is free to indulge in all of his worst impulses, until the small moments of ingenuity that made him so special are gone.
Remember, above all else: a good artist needs to be criticized. Every writer needs a handful of early readers whose feedback he or she trusts. At first, it will probably be one or two close friends; later, hopefully, it will be an editor. But Lucas is the richest man in Hollywood; he produces and owns the Star Wars franchise outright; he doesn’t need to listen to critics. And he might reasonably argue that he doesn’t have to. But no matter what your level of success, you need someone to tell you when you’ve lost your way. And Lucas, sad to say, hasn’t had this for a long time.