Posts Tagged ‘Star Wars’
Last week, I came across a conversation on Yahoo Movies UK with John Gilroy and Colin Goudie, two of the editors who worked on Rogue One. I’ve never read an interview with a movie editor that wasn’t loaded with insights into storytelling, and this one is no exception. Here’s my favorite tidbit, in which Goudie describes cutting together a story reel early in the production process:
There was no screenplay, there was just a story breakdown at that point, scene by scene. [Director Gareth Edwards] got me to rip hundreds of movies and basically make Rogue One using other films so that they could work out how much dialogue they actually needed in the film.
It’s very simple to have a line [in the script] that reads “Krennic’s shuttle descends to the planet.” Now that takes maybe two to three seconds in other films, but if you look at any other Star Wars film you realize that takes forty-five seconds or a minute of screen time. So by making the whole film that way—I used a lot of the Star Wars films—but also hundreds of other films, too, it gave us a good idea of the timing.
This is a striking observation in itself. If Rogue One does an excellent job of recreating the feel of its source material, and I think it does, it’s because it honors its rhythms—which differ in subtle respects from those of other films—to an extent that the recent Star Trek movies mostly don’t. Goudie continues:
For example, the sequence of them breaking into the vault, I was ripping the big door closing in WarGames to work out how long does a vault door take to close.
So that’s what I did, and that was three months work to do that, and that had captions at the bottom which explained the action that was going to be taking place, and two thirds of the screen was filled with the concept art that had already been done and one quarter, the bottom corner, was the little movie clip to give you how long that scene would actually take.
Then I used dialogue from other movies to give you a sense of how long it would take in other films for someone to be interrogated. So for instance, when Jyn gets interrogated at the beginning of the film by the Rebel council, I used the scene where Ripley gets interrogated in Aliens.
This might seem like little more than interesting trivia, but there’s actually a lot to unpack. You could argue that the ability to construct an entire Star Wars movie out of analogous scenes from other films only points to how derivative the series has always been: it’s hard to imagine doing this for, say, Manchester By the Sea, or even Inception. But that’s also a big part of the franchise’s appeal. Umberto Eco famously said that Casablanca was made up of the memories of other movies, and he suggested that a cult movie—which we can revisit in our imagination from different angles, rather than recalling it as a seamless whole—is necessarily “unhinged”:
Only an unhinged movie survives as a disconnected series of images, of peaks, of visual icebergs. It should display not one central idea but many. It should not reveal a coherent philosophy of composition. It must live on, and because of, its glorious ricketiness.
After reminding us of the uncertain circumstances under which Casablanca was written and filmed, Eco then suggests: “When you don’t know how to deal with a story, you put stereotyped situations in it because you know that they, at least, have already worked elsewhere…My guess is that…[director Michael Curtiz] was simply quoting, unconsciously, similar situations in other movies and trying to provide a reasonably complete repetition of them.”
What interests me the most is Eco’s conclusion: “What Casablanca does unconsciously, other movies will do with extreme intertextual awareness, assuming also that the addressee is equally aware of their purposes.” He cites Raiders of the Lost Ark and E.T. as two examples, and he easily could have named Star Wars as well, which is explicitly made up of such references. (In fact, George Lucas was putting together story reels before there was even a word for it: “Every time there was a war movie on television, like The Bridges at Toko-Ri, I would watch it—and if there was a dogfight sequence, I would videotape it. Then we would transfer that to 16mm film, and I’d just edit it according to my story of Star Wars. It was really my way of getting a sense of the movement of the spaceships.”) What Eco doesn’t mention—perhaps because he was writing a generation ago—is how such films can pass through intertextuality and end up on the other side. They create memories for viewers who aren’t familiar with the originals, and they end up being quoted in turn by filmmakers who only know Star Wars. They become texts in themselves. In assembling a story reel from hundreds of other movies, Edwards and Goudie were only doing in a literal fashion what most storytellers do in their heads. They figure out how a story should “look” at its highest level, in a rough sketch of the whole, and fill in the details later. The difference here is that Rogue One had the budget and resources to pay someone to do it for real, in a form that could be timed down to the second and reviewed by others, on the assumption that it would save money and effort down the line. Did it work? I’ll be talking about this more tomorrow.
How do you release blockbusters like clockwork and still make each one seem special? It’s an issue that the movie industry is anxious to solve, and there’s a lot riding on the outcome. When I saw The Phantom Menace nearly two decades ago, there was an electric sense of excitement in the theater: we were pinching ourselves over the fact that we were about to see see the opening crawl for a new Star Wars movie on the big screen. That air of expectancy diminished for the two prequels that followed, and not only because they weren’t very good. There’s a big difference, after all, between the accumulated anticipation of sixteen years and one in which the installments are only a few years apart. The decade that elapsed between Revenge of the Sith and The Force Awakens was enough to ramp it up again, as if fan excitement were a battery that recovers some of its charge after it’s allowed to rest for a while. In the past, when we’ve watched a new chapter in a beloved franchise, our experience hasn’t just been shaped by the movie itself, but by the sudden release of energy that has been bottled up for so long. That kind of prolonged wait can prevent us from honestly evaluating the result—I wasn’t the only one who initially thought that The Phantom Menace had lived up to my expectations—but that isn’t necessarily a mistake. A tentpole picture is named for the support that it offers to the rest of the studio, but it also plays a central role in the lives of fans, which have been going on long before the film starts and will continue after it ends. As Robert Frost once wrote about a different tent, it’s “loosely bound / By countless silken ties of love and thought / to every thing on earth the compass round.”
When you have too many tentpoles coming out in rapid succession, however, the outcome—if I can switch metaphors yet again—is a kind of wave interference that can lead to a weakening of the overall system. On Christmas Eve, I went to see Rogue One, which was preceded by what felt like a dozen trailers. One was for Spider-Man: Homecoming, which left me with a perplexing feeling of indifference. I’m not the only one to observe that the constant onslaught of Marvel movies makes each installment feel less interesting, but in the case of Spider-Man, we actually have a baseline for comparison. Two baselines, really. I can’t defend every moment of the three Sam Raimi films, but there’s no question that each of those movies felt like an event. There was even enough residual excitement lingering after the franchise was rebooted to make me see The Amazing Spider-Man in the theater, and even its sequel felt, for better or worse, like a major movie. (I wonder sometimes if audiences can sense the pressure when a studio has a lot riding on a particular film: even a mediocre movie can seem significant if a company has tethered all its hopes to it.) Spider-Man: Homecoming, by contrast, feels like just one more component in the Marvel machine, and not even a particularly significant one. It has the effect of diminishing a superhero who ought to be at the heart of any universe in which he appears, relegating one of the two or three most successful comic book characters of all time to a supporting role in a larger universe. And because we still remember how central he was to no fewer than two previous franchises, it feels like a demotion, as if Spider-Man were an employee who had left the company, came back, and is now reporting to Iron Man.
It isn’t that I’m all that emotionally invested in the future of Spider-Man, but it’s a useful case study for what it tells us about the pitfalls of these films, which can take something that once felt like a milestone and reduce it to a midseason episode of an ongoing television series. What’s funny, of course, is that the attitude we’re now being asked to take toward these movies is actually closer to the way in which they were originally conceived. The word “episode” is right there in the title of every Star Wars movie, which George Lucas saw as an homage to classic serials, with one installment following another on a weekly basis. Superhero films, obviously, are based on comic books, which are cranked out by the month. The fact that audiences once had to wait for years between movies may turn out to have been a historical artifact caused by technological limitations and corporate inertia. Maybe the logical way to view these films is, in fact, in semiannual installments, as younger viewers are no doubt growing up to expect. In years to come, the extended gaps between these movies in prior decades will seem like a structural quirk, rather than an inherent feature of how we relate to them. This transition may not be as meaningful as, say, the shift from silent films to the talkies, but they imply a similar change in the way we relate to the film onscreen. Blockbusters used to be released with years of anticipation baked into the response from moviegoers, which is no longer something that can be taken for granted. It’s a loss, in its way, to fan culture, which had to learn how to sustain itself during the dry periods between films, but it also implies that the movies themselves face a new set of challenges.
To be fair, Disney, which controls both the Marvel and Star Wars franchises, has clearly thought a lot about this problem, and they’ve hit on approaches that seem to work pretty well. With the Marvel Universe, this means pitching most of the films at a level at which they’re just good enough, but no more, while investing real energy every few years into a movie that is first among equals. This leads to a lot of fairly mediocre installments, but also to the occasional Captain America: Civil War, which I think is the best Marvel movie yet—it pulls off the impossible task of updating us on a dozen important characters while also creating real emotional stakes in the process, which is even more difficult than it looks. Rogue One, which I also liked a lot, takes a slightly different tack. For most of the first half, I was skeptical of how heavily it was leaning on its predecessors, but by the end, I was on board, and for exactly the same reason. This is a movie that depends on our knowledge of the prior films for its full impact, but it does so with intelligence and ingenuity, and there’s a real satisfaction in how neatly it aligns with and enhances the original Star Wars, while also having the consideration to close itself off at the end. (A lot of the credit for this may be due to Tony Gilroy, the screenwriter and unbilled co-director, who pulled off much of the same feat when he structured much of The Bourne Ultimatum to take place during gaps in The Bourne Supremacy.) Relying on nostalgia is a clever way to compensate for the reduced buildup between movies, as if Rogue One were drawing on the goodwill that Star Wars built up and hasn’t dissipated, like a flywheel that serves as an uninterruptible power supply. Star Wars isn’t just a tentpole, but a source of energy. And it might just be powerful enough to keep the whole machine running forever.
As we were watching the premiere of Westworld last week, my wife turned to me and said: “Why would they make it a western park?” Or maybe I asked her—I can’t quite remember. But it’s a more interesting question than it sounds. When Michael Crichton’s original movie was released in the early seventies, the western was still a viable genre. It had clearly fallen from its peak, but major stars were doing important work in cowboy boots: Eastwood, of course, but also Newman, Redford, and Hoffman. John Wayne was still alive, which may have been the single most meaningful factor of all. As a result, it wasn’t hard to imagine a theme park with androids designed to fulfill that particular fantasy. These days, the situation has changed. The western is so beleaguered an art form that whenever one succeeds, it’s treated as newsworthy, and that’s been true for the last twenty years. Given the staggering expense and investment involved in a park like this, it’s hard to see why the western would be anybody’s first choice. (Even with the movie, I suspect that Crichton’s awareness of his relatively low budget was part of the decision: it was his first film as a director, with all of the limitations that implies, and a western could be shot cheaply on standing sets in the studio backlot.) Our daydreams simply run along different lines, and it’s easier to imagine a park being, say, set in a medieval fantasy era, or in the future, or with dinosaurs. In fact, there was even a sequel, Futureworld, that explored some of these possibilities, although it’s fair to say that nobody remembers it.
The television series Westworld, which is arriving in a markedly different pop cultural landscape, can’t exactly ditch the premise—it’s right there in the title. But the nice thing about the second episode, “Chestnut,” is that it goes a long way toward explaining why you’d still want to structure an experience like this around those conventions. It does this mostly by focusing on a new character, William, who arrives at the park knowing implausibly little about it, but who allows us to see it through the eyes of someone encountering it for the first time. What he’s told, basically, is that the appeal of Westworld is that it allows you to find out who you really are: you’re limited only by your inhibitions, your abilities, and your sense of right and wrong. That’s true of the real world, to some extent, but we’re also more conscious of the rules. And if the western refuses to go away as a genre, it’s because it’s the purest distillation of that seductive sense of lawlessness. The trouble with telling certain stories in the present day is that there isn’t room for the protagonist that thrillers have taught us to expect: a self-driven hero who solves his problems for himself in matters of life and death. That isn’t how most of us respond to a crisis, and in order to address the issue of why the main character doesn’t just go to the police, writers are forced to fall back on various makeshift solutions. You can focus on liminal figures, like cops or criminals, who can take justice into their own hands; you can establish an elaborate reason why the authorities are helpless, indifferent, or hostile; or you can set your story in a time or place where the rules are different or nonexistent.
The western, in theory, is an ideal setting for a story in which the hero has to rely on himself. It’s a genre made up of limitless open spaces, nonexistent government, unreliable law enforcement, and a hostile native population. If there’s too much civilization for your story to work, your characters can just keep riding. To move west, or to leave the center of the theme park, is to move back in time, increasing the extent to which you’re defined by your own agency. (A western, revealingly, is a celebration of the qualities that we tend to ignore or dismiss in our contemporary immigrant population: the desire for a new life, the ability to overcome insurmountable obstacles, and the plain observation that those who uproot themselves and start from scratch are likely to be more competent and imaginative, on average, than those who remain behind.) The western is the best narrative sandbox ever invented, and if it ultimately exhausted itself, it was for reasons that were inseparable from its initial success. Its basic components were limited: there were only so many ways that you could combine those pieces. Telling escapist stories involved overlooking inconvenient truths about Native Americans, women, and minorities, and the tension between the myth and its reality eventually became too strong to sustain. Most of all, its core parts were taken over by other genres, and in particular by science fiction and fantasy. This began as an accidental discovery of pulp western writers who switched genres and realized that their tricks worked equally well in Astounding, and it was only confirmed by Star Trek—which Gene Roddenberry famously pitched as Wagon Train in space—and Star Wars, which absorbed those clichés so completely that they became new again.
What I like about Westworld, the series, is that it reminds us of how artificial this narrative always was, even in its original form. The Old West symbolizes freedom, but only if you envision yourself in the role of the stock protagonist, who is usually a white male antihero making the journey of his own volition. It falls apart when you try to imagine the lives of the people in the background, who exist in such stories solely to enable the protagonist’s fragile range of options. In reality, the frontier brutally circumscribed the lives of most of those who tried to carve out an existence there, and the whole western genre is enabled by a narrative illusion, or a conspiracy, that keeps its solitary and brutish aspects safely in the hands of the characters at the edges of the frame. Westworld takes that notion to its limit, by casting all the supporting roles with literal automatons. They aren’t meant to have inner lives, any more than the peripheral figures in any conventional western, and the gradual emergence of their consciousness implies that the park will eventually come to deconstruct itself. (The premiere quoted cleverly from The Searchers and Unforgiven, but I almost wish that it had saved those references until later, so that the series could unfold as a miniature history of the genre as it slowly attained self-awareness.) If you want to talk about how we picture ourselves in the heroes of our own stories, while minimizing or reducing the lives of those at the margins, it’s hard to imagine a better place to do it than the western, which depended on a process of historical amnesia and dehumanization from the very beginning. I’m not sure I’d want to visit a park like Westworld. But there will always be those who would.
Note: As I dive into the research process for my upcoming book Astounding: John W. Campbell, Isaac Asimov, Robert A. Heinlein, L. Ron Hubbard, and the Golden Age of Science Fiction, I’ll be taking the opportunity here to highlight works within the genre that deserve to be rediscovered, reappraised, or simply enjoyed by a wider audience.
Nothing dates more quickly than a vision of the future. This isn’t just because reality has a way of catching up with and passing even the most plausible predictions, or because certain narrative elements, like the constant smoking we find in so much golden age science fiction, become anachronistic even before the prophesied year approaches. It’s because any literary work is inevitably saturated with the era that created it, regardless of genre. Language, cultural attitudes, style, pacing: they all require some degree of mental adjustment, just as a modern moviegoer has to be ready to meet the classic films of the forties halfway. If you aren’t willing to undergo that kind of mental shift, like a viewer who can’t sit through Casablanca because it’s in black and white, you’ve shut yourself off from an entire world of storytelling: anything outside that window—which creeps forward over time, cutting you off from more and more of the past—remains out of bounds. Science fiction, in any medium, is particularly vulnerable to this. If few of us watch When Worlds Collide or This Island Earth for our own pleasure these days, it isn’t just because the special effects seem clunky, but because it’s hard to accept an idea of the future filtered through the idiom of the fifties. Go back further to the pulps, and that cognitive divide looms even wider. And if you’re going to read the science fiction of the thirties, you have to account for the personal equation that separates you from its intended audience, a gap that even devoted fans can have trouble crossing.
This is all my way of leading up to the fact that Galactic Patrol by E.E. “Doc” Smith probably requires less of an adjustment to enjoy today than any other story of the space opera or superscience genre. In other words, it’s a blast, and it’s the first novel I’d recommend to anybody who was curious about what was happening in science fiction before the golden age. Smith, who in his nonwriting life was a food engineer specializing in doughnut mixes, isn’t all that familiar to mainstream readers today, but he was beloved, even idolized, within the fandom for decades, and it isn’t hard to see why. Galactic Patrol is the first installment in the saga of the Lensmen, an interstellar police force tasked with protecting the galaxy from the depredations of a ruthless nation of space pirates. (Just whisper the word “Lensman” and you feel a little internal shiver of anticipation, even if you have no idea what it means.) Each officer wears the Lens, a jewel constructed by an advanced alien race that serves as a universal translator, telepathic communicator, and identification badge. It can be wielded only by its intended user, who is selected after a rigorous training process designed to produce individuals of superhuman bravery, intelligence, and integrity. Galactic Patrol follows Kimball Kinnison, a recent graduate from the academy, on his first mission, and although he starts out by “attacking imaginary foes and actual meteorites with equal zeal”—as L. Ron Hubbard would later do during his own brief command in the Navy—he rapidly embarks on an adventure that dwarfs anything the genre had ever seen.
Because the book really moves. Smith’s conception of interstellar travel is based on an inertialess drive, which instantly accelerates a spacecraft to faster than the speed of light, and Galactic Patrol has what I can only describe as an inertialess narrative. It’s as close as any novel can get to pure action, jumping from one high point to the next without any of the boring parts in between, and it doesn’t let up until literally the very last word. It sends both Kinnison and the reader bounding across the galaxy, and at its best, it’s still breathtaking. In fact, it miraculously manages to evoke both Star Trek and Star Wars, in sort of the same way that the Aeneid contains both the Iliad and the Odyssey, except that Smith is their great originator. It anticipates Star Trek in revolving around a starship and its crew—including an oddly familiar engineer who emerges from below decks, clutching a spanner and asking for some grease soap—but its breakneck pacing and emphasis on action are closer to Star Wars, although significantly more violent. (“As he struck and struck and struck again, the cell became a gorily reeking slaughter-pen, its every corner high-piled with the shattered corpses of the Wheelmen and its floor running with blood and slime.”) Parts of it even look ahead to Dune, with its idea of a single planet serving the sole source of a priceless drug, in this case a kind of superheroin called thionite. It’s all very artless, but thrilling, and it could only have come from the heart. Later, as one of the first in a long line of imitators, John W. Campbell would make his name in much the same kind of story, but in his hands, it feels like hackwork, while Smith writes this sort of novel just because he loves it.
Not every element of Galactic Patrol has aged equally well. There are the obvious moments of dissonance, like the fact that the crew of the spacecraft plots its course using calipers, compass, and slide rule, or that when we’re introduced to a “computer,” it turns out to be a man who computes for a living. Its attitudes toward women are harder to stomach: the Lensmen we meet are exclusively male, and for most of the story, the only women in sight are nurses, decoys, or hostages, along with the unnamed “stenographer” with whom Kinnison collides at headquarters. Only Clarissa MacDougall, the red-headed nurse who becomes Kinnison’s love interest, gets anything like a real speaking part. (It’s worth noting that Smith’s first novel, Skylark of Space, had two significant female characters, thanks in all likelihood to his coauthor Lee Hawkins Garby—another female writer who has fallen out of the history of science fiction.) It’s a boy’s book of adventure in space, sexless and morally unwavering, and once you account for this, it comes closer than any other story to recapturing the excitement of the days in which readers would lurk at newsstands to avidly await the next installment of a serial in Astounding. Later, the genre would leave Smith behind: he was grandfathered into Campbell’s circle of authors as a beloved elder statesman, but he never broke through to a readership outside the fandom. And that’s a real loss. The kind of storytelling that he perfected, for better or worse, is still what occurs to most people when they think of science fiction, even if they know it only through his imitators. And Galactic Patrol gives it to you uncut, like a pure hit of thionite.
Difficult to see. Always in motion is the future.
—Yoda, The Empire Strikes Back
At some point over the next few hours, perhaps as you’re reading this post, The Force Awakens is projected to surge past Avatar to become the highest-grossing movie in the history of the North American box office. We usually don’t adjust such figures for inflation, of course, probably because there wouldn’t be as many records broken each year if we did, and it’s all but certain that the original Star Wars will remain tops in the franchise in terms of tickets sold. Yet it’s impossible to discount this achievement. If the latest installment continues on its present trajectory, it has a good chance of cracking the adjusted top ten of all time—it would need to gross somewhere north of $948 million domestic to exceed Snow White and the Seven Dwarfs and earn a spot on that rarefied list, and this is starting to feel like a genuine possibility. Given the changes in the entertainment landscape over the last century, this is beyond flabbergasting. But even this doesn’t get at the real, singular nature of what we’re witnessing today. The most unexpected thing about the success of The Force Awakens is how expected it was. And at a time when Hollywood is moving increasingly toward a tentpole model in which a handful of blockbusters finance all the rest, it represents both a historic high point for the industry and an accomplishment that we’re unlikely to ever see again.
When you look at the lineal timeline of the most successful films at the domestic box office, you have to go back seventy-five years to find a title that even the shrewdest industry insider could have reasonably foreseen. This list, unadjusted for inflation, consists of Gone With the Wind, The Sound of Music, The Godfather, Jaws, Star Wars, E.T., Titanic, and Avatar. Gone With the Wind, which claimed the title that The Birth of a Nation had won a quarter of a century earlier, is the one exception: there’s no doubt that David O. Selznick hoped that it could be the biggest film of its era, even before the first match had been struck for the burning of Atlanta. Every other movie here is a headscratcher. No studio insider at the time would have been willing to bet that The Sound of Music—which Pauline Kael later called The Sound of Money—would outgross not just Doctor Zhivago and Thunderball that year, but every other movie ever made. The Godfather and Jaws were both based on bestselling novels, but that’s hardly a guarantee of success, and both were troubled productions with untested directors at the helm. Star Wars itself hardly needs to be discussed here. Columbia famously passed on E.T., and Titanic was widely regarded before its release as a looming disaster. And even Avatar, which everyone thought would be huge, exceeded all expectations: when you take regression to the mean into account, the idea that James Cameron could break his own record is so implausible that I have a hard time believing it even now.
Which is just another way of saying that these movies were all outliers: unique, idiosyncratic projects, not part of any existing franchise, that audiences discovered gradually, often to the bewilderment of the studios themselves. The Force Awakens was different. It had barely been announced before pundits were speculating that it could set the domestic record, and although Disney spent much of buildup to its opening weekend downplaying such forecasts—with the implication that rival studios were inflating projections to make its final performance seem disappointing—it’s hard to believe that the possibility hadn’t crossed everybody’s mind. Most movie fans will remember that William Goldman said “Nobody knows anything” in Adventures in the Screen Trade, but it’s worth quoting the relevant paragraph in full. After noting that everyone in town except for Paramount turned down Raiders of the Lost Ark, he continues:
Why did Paramount say yes? Because nobody knows anything. And why did all the other studios say no? Because nobody knows anything. And why did Universal, the mightiest studio of all, pass on Star Wars, a decision that may just cost them, when all the sequels and spinoffs and toy money and book money and video-game money are totaled, over a billion dollars? Because nobody, nobody—not now, not ever—knows the least goddam thing about what is or isn’t going to work at the box office.
If Hollywood has learned anything since, it’s that you don’t pass on Star Wars. Whatever you might think of its merits as a movie, The Force Awakens marks the one and only time that somebody knew something. And it’s probably the last time, too. It may turn into the reassuring bedtime story that studio executives use to lull themselves to sleep, and Disney may plan on releasing a new installment on an annual basis forever, but the triumphant rebirth of the franchise after ten years of dormancy—or three decades, depending on how you feel about the prequels—is the kind of epochal moment that the industry is doing its best to see never happens again. We aren’t going to have another chance to miss Star Wars because it isn’t going to go away, and the excitement that arose around its return can’t be repeated. The Force Awakens is both the ultimate vindication of the blockbuster model and a high-water mark that will make everything that follows seem like diminishing returns. (More insidiously, it may be the Jedi mind trick that convinces the studios that they know more than they do, which can only lead to heartbreak.) Records are made to be broken, and at some point in my lifetime, another movie will take the crown, if only because inflation will proceed to a point where the mathematics become inevitable. But it won’t be a Star Wars sequel. And it won’t be a movie that anyone, not even a Jedi, can see coming.
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.
Note: Oblique spoilers follow for Star Wars Episode VII: The Force Awakens.
At this point, it might seem that there isn’t anything new left to say about The Force Awakens, but I’d like to highlight a revealing statement from director J.J. Abrams that, to my knowledge, hasn’t been given its due emphasis before. It appears in an interview that was published by Wired on November 9, or over a month in advance of the film’s release. When the reporter Scott Dadich asks if there are any moments from the original trilogy that stand out to him, Abrams replies:
It would be a much shorter conversation to talk about the scenes that didn’t stand out. As a fan of Star Wars, I can look at those movies and both respect and love what they’ve done. But working on The Force Awakens, we’ve had to consider them in a slightly different context. For example, it’s very easy to love “I am your father.” But when you think about how and when and where that came, I’m not sure that even Star Wars itself could have supported that story point had it existed in the first film, Episode IV. Meaning: It was a massively powerful, instantly classic moment in movie history, but it was only possible because it stood on the shoulders of the film that came before it. There had been a couple of years to allow the idea of Darth Vader to sink in, to let him emerge as one of the greatest movie villains ever. Time built up everyone’s expectations about the impending conflict between Luke and Vader. If “I am your father” had been in the first film, I don’t know if it would have had the resonance. I actually don’t know if it would have worked.
Taken in isolation, the statement is interesting but not especially revelatory. When we revisit it in light of what we now know about The Force Awakens, however, it takes on a startling second meaning. It’s hard not to read it today without thinking of a particular reveal about one new character and the sudden departure of another important player. When I first saw the film, without having read the interview in Wired, it immediately struck me that these plot points were in the wrong movie: they seemed much more like moments that would have felt more at home in the second installment of the sequel trilogy, and not merely because the sequence in question openly pays homage to the most memorable scene in The Empire Strikes Back. To venture briefly into spoilerish territory: if Kylo Ren had been allowed to dominate the entirety of The Force Awakens “as one of the greatest movie villains ever,” to use Abrams’s own words, the impact of his actions and what we learn about his motivations would have been far more powerful—but only if they had been saved for Episode VIII. As it stands, we’re introduced to Ren and his backstory all but in the same breath, and it can’t help but feel rushed. Similarly, when another important character appears and exits the franchise within an hour or so of screentime, it feels like a wasted opportunity. They only had one chance to do it right, and compressing what properly should have been the events of two films into one is a real flaw in an otherwise enjoyable movie.
And what intrigues me the most about the quote above is that Abrams himself seems agonizingly aware of the issue. When you read over his response again, it becomes clear that he isn’t quite responding to the question that the interviewer asked. Instead, he goes off on a tangent that wouldn’t even have occurred to him if it hadn’t already been on his mind. I have no way of looking into Abrams’s brain, Jedi style, but it isn’t difficult to imagine what happened. Abrams, Lawrence Kasdan, and Michael Arndt—the three credited screenwriters, which doesn’t even take into account the countless other producers and executives who took a hand in the process—must have discussed the timing of these plot elements in detail, along with so many others, and at some point, the question would have been raised as to whether they might not better be saved for a later movie. Abrams’s statement to Wired feels like an undigested excerpt from those discussions that surfaced in an unrelated context, simply because he happened to remember it in the course of the interview. (Anyone who has ever been interviewed, and who wants to give well-reasoned responses, will know how this works: you often end up repurposing thoughts and material that you’ve worked up elsewhere, if they have even the most tangential relevance to the topic at hand.) If you replace “Darth Vader” with “Kylo Ren” in Abrams’s reply, and make a few other revisions to square it with Episode VII, you can forensically reconstruct one side of an argument that must have taken place in the offices of Bad Robot on multiple occasions. And Abrams never forgot it.
So what made him decide to ignore an insight so good that he practically internalized it? There’s no way of knowing for sure, but it seems likely that contract negotiations with one of the actors involved—and those who have seen the movie will know which one I mean—affected the decision to move this scene up to where it appears now. Dramatically speaking, it’s in the wrong place, but Abrams and his collaborators may not have had a choice. As he implies throughout this interview and elsewhere, The Force Awakens was made under conditions of enormous pressure: it isn’t just a single movie, but the opening act in the renewal of a global entertainment franchise, and the variables involved are so complicated that no one filmmaker can have full control over the result. (It’s also tempting to put some of the blame on Abrams’s directing style, which rushes headlong from one plot point to another as if this were the only new Star Wars movie we were ever going to get. The approach works wonderfully in the first half, which is refreshingly eager to get down to business and slot the necessary pieces into place, but it starts to backfire in the second and third acts, which burn through big moments so quickly that we’re left scrambling to feel anything about what we’ve seen.) Tomorrow, I’m going to talk a little more about how the result left me feeling both optimistic and slightly wary of what the future of Star Wars might bring. But in this particular instance, Abrams made an error. Or he suspects that he did. And when he searches his feelings, he knows it to be true.