Chapter 124: Project STAR WARS
Date: 25-26 June 1973 Location: Bombay — Shergill Cinema Offices, Pedder Road; Shergill Animation Warehouse, Eastern Bombay; Shergill Residence, Malabar Hill
The newspapers were still running pieces about Kuber.
Not reviews — the reviews had run weeks ago and had ranged from bewildered to rapturous depending on which paper you read and which editorial politics shaped the coverage. What was running now were the follow-on pieces, the second-order commentary, the articles with titles like What Shergill Films Means for Indian Cinema and The Industrialisation of Storytelling and one particularly ambitious piece in the Sunday Times of India that attempted to draw a line from Licence Raj in January 1971 through twelve films across two and a half years to some conclusion about what Indian culture was becoming and whether this was good for it. The piece was ten thousand words long and had not reached a conclusion by the end of it, which was appropriate because nobody had reached a conclusion yet. The thing was still happening.
In the Shergill Cinema offices on Pedder Road — a building that had begun three years ago as a rented floor above an export company and had expanded through four additional floors as the studio's operation had grown into something that required that much space to contain — the aftermath of Kuber's release had the specific quality that peak-momentum success produces, which is not celebration but rather the particular exhausted tension of an organisation that has been running at the edge of its capacity for so long that success feels less like arrival than like the moment when you look down and discover that the ground has been moving under you for some time without your having noticed.
The editors were exhausted. Shergill Cinema was currently in post-production on three projects simultaneously, which was a level of parallel output that the studio had not previously attempted and that was discovering, in real time, the specific ways in which simultaneous post-production on three projects simultaneously was different from sequential post-production on three projects in sequence. The ways were not comfortable ones.
The animation warehouse on the eastern edge of the studio district was generating its own pressure. The Ganesha sequences were seven weeks ahead of where they had been when Karan had reviewed them in May and sent them back for the sari movement to be corrected, but being ahead of schedule in one respect had produced the discovery that three other sequences were behind schedule in ways that the schedule had not previously accounted for, and the resolution of this required the kind of creative problem-solving that creative people do not always welcome when they are already tired.
The Bombay film industry had been watching Shergill Cinema for two and a half years with the specific attention of competitors who are not sure whether to be impressed or alarmed and have settled on a posture of public scepticism combined with private imitation. The imitations were proliferating. Other studios had released films with no songs, which was what you got when you identified the visible feature of a thing and reproduced it without understanding the principle it expressed. The films with no songs that other studios had made were uniformly unsuccessful, in ways that the studio heads described as evidence that Indian audiences were not actually ready for this kind of film and that the film critics who were not sympathetic to Shergill Cinema described as evidence that execution mattered as much as concept, and that the film critics who were sympathetic to Shergill Cinema described as evidence that you could not produce accuracy by deciding to omit melodrama, that accuracy was a positive quality produced by positive attention rather than a negative quality produced by the removal of its opposite.
The engineers who had proliferated through the Shergill Cinema offices in the past two years — optical engineers, sound engineers, camera engineers, the mechanical team that had been hired initially to maintain the studio's expanding technical equipment and had gradually become something more like a research and development function — were everywhere. They occupied corners of the editing suites. They had taken over two storage rooms on the fourth floor and converted them into what they called a testing environment and what looked, from outside, like the aftermath of a workshop explosion. They were enthusiastic in the specific way of engineers who have been given permission to be interested in something outside their primary domain.
Karan moved through all of this on a Tuesday morning in the last week of June with the controlled attention of someone who is seeing a large operation that is working and is thinking: what next?
Not impatiently. Not in dissatisfaction with what was working. In the specific mode of a mind that finds stasis difficult and that is constitutionally oriented toward the next problem in the sequence even when the current problem has not fully resolved itself. He had been in this mode since the Vigyan Bhawan press conference. He had been in it since the BUM announcement. He was in it now, moving through the Pedder Road offices with his operations director Priya Verma beside him, reviewing the three simultaneous post-production situations, and thinking: what next?
"The Ganesha background work," he said. "The forest sequences."
"Five weeks out," Priya said. "The team has been reviewing Pahari miniatures for three weeks straight. The movement is right now. You'll see it when the cut comes in Thursday."
"And the sound design?"
"The composer wants another month. He says what he's doing with the classical instruments in the birth sequence requires more time to resolve correctly."
"Give him another month. Don't rush the birth sequence."
Priya made a note. "The second Kaoboys script. Draft four is on your desk."
"I read it last night. It's better than draft three. There's a scene in the Tehran sequence where the tradecraft is wrong. I'll mark it."
"The Tehran consultant is available for a call Thursday."
"Schedule it after the Ganesha review."
They walked through the editing floor — banks of editing tables, the mechanical click and whir of editing equipment, editors bent over footage in the focused isolation of people doing work that requires the entire available brain. The floor smelled of cigarette smoke and coffee and the specific slightly chemical smell of editing chemicals on film stock. It was a working smell, a productive smell.
"The animation warehouse," Karan said. "I'm going there this afternoon."
"The VFX team has been asking for a review. They've been working on something they want to show you."
"What something?"
"They described it as a compositing experiment. I don't entirely know what that means in the context of what they're doing."
"I'll find out this afternoon."
The animation warehouse in the afternoon was a different world from the Pedder Road offices in the morning. Not in character — both were working environments, serious and loud in the way of places where demanding work is being conducted by people who care about doing it correctly. But different in texture. The Pedder Road offices were the texture of the film business: polished, organised, aware of itself as an industry with conventions and hierarchies and protocols developed over decades of Indian cinema. The warehouse was the texture of something that did not yet have conventions because it was still in the process of determining what it was.
It was three hundred feet long and a hundred and fifty feet wide. The ceiling was forty feet high, which was necessary for the scale of some of the background work and for the optical printer installation that took up the warehouse's northern quarter. Daylight came in through clerestory windows along the upper walls and was supplemented by artificial lighting that the team had been adjusting for three months to produce the specific quality of consistent, shadowless illumination that animation work required.
The background painters occupied the eastern end — twenty-two of them, working on surfaces that ranged from individual cel-sized backgrounds to the large-format establishing shots that would anchor the viewer in the world of the animation. They worked in a silence that was less absence of noise than the presence of concentration. The Pahari miniature reproductions that Karan had commissioned were pinned at eye level along the full length of the eastern wall — two hundred and thirty of them, covering every major period and regional variant of the tradition, providing the visual reference library that the team worked from.
Karan stopped at the first painter's table.
The man working there — Ramesh, who had come from the Bombay School of Art and who had been at the studio since it opened, which meant he had been there long enough to be the person newer painters came to when they had questions about the style — was working on a forest background. Dense vegetation, the specific quality of morning light filtering through canopy that the Pahari tradition rendered with a combination of flat colour areas and fine line detail that produced, in the animation context, a visual richness different from any other technique.
"The movement layer," Karan said.
Ramesh pointed to the side table where four variant cels of the same forest section were laid out. Each was identical except for the position of specific leaves and branches, creating, when cycled in sequence, the impression of wind through the forest.
"Four frames for the cycle," Ramesh said. "We've been testing eight but four looks more natural."
"Why does four look more natural than eight?"
"Because Pahari painting doesn't try to show continuous motion. It shows the state of things. When you animate it with eight frames you get something that looks like a Western animation cycle. Four frames keeps the quality of the painting moving rather than the feeling of the painting being replaced by a motion picture."
Karan looked at the four cels for a moment. "Keep four," he said. "Put that reasoning in the production document. When the next team picks up the forest background for the Ramayana series, I want them to know why."
He moved along the eastern wall.
The motion-layer experiment section was three tables in the middle of the eastern section where two painters and an engineer were doing something that appeared, from ten feet away, to involve painting on glass. From five feet away it resolved into something more interesting: painting multiple layers of a single background on different transparent surfaces, each surface representing a different depth plane, so that when the camera moved between them at different speeds it created the impression of three-dimensional depth in what was otherwise a flat image.
"Multi-plane," the engineer said when Karan stopped. His name was Ajit, and he had come to the animation division from the Shergill Aerospace manufacturing division for reasons that he described, when asked, as curiosity about a different kind of precision problem. "Disney developed this in the thirties. We've been adapting it for the Pahari art style, which has different spatial conventions than Western animation."
"How different?"
"Western spatial conventions use perspective to create depth — things get smaller as they recede. Pahari painting uses a different system — elements are arranged vertically on the picture plane to indicate spatial position, with distant elements at the top and near elements at the bottom, but without the size reduction of perspective. When you try to animate multi-plane with Pahari conventions you have to rethink the speed relationships between layers."
"And you've done that?"
"We've done it for three types of establishing shot. We have a working rule. It's in the production document."
"Show me the result."
Ajit took him to the testing area — a darkened alcove at the end of the eastern section where a small projection setup allowed them to review work in progress. He threaded the test footage.
What appeared on the small screen was a landscape — a mountain valley with a river and dense forest and distant peaks. The camera moved slowly across it. The elements at different depths moved at different speeds relative to the frame edge, creating a spatial illusion that was unmistakeable and that was, simultaneously, recognisably Pahari in its visual quality rather than being a Pahari painting that had been converted into something else.
"That works," Karan said.
"It works for this type of shot. We have three more problem types to solve before we have the full system."
"How long?"
"Four weeks for the problem types. Two weeks to integrate into the production workflow. Six weeks total."
"You have eight. Use the extra two to document it properly."
The optical printer department occupied the northern quarter of the warehouse. It was the newest and loudest and most experimental section of the operation, and it was the section that had been making Priya most anxious, because the optical printer department had been consuming resources at a rate that was not obviously connected to the animation work it had ostensibly been established to serve.
An optical printer was, at its most basic, a machine that re-photographed film. You placed a piece of source film in the printer, you placed a fresh piece of film in the camera attached to the printer, and you re-photographed the source frame by frame, which allowed you to manipulate — enlarge, reduce, combine multiple sources, add mattes, change the colour balance, add elements that had not been in the original photograph. It was the fundamental tool of visual effects work. Every major special effects sequence in every significant film of the past thirty years had been produced through an optical printer.
Shergill Cinema's optical printer department had two printers. One had been purchased from a German manufacturer in late 1972. The second had been partially built and partially modified by the engineering team, who had taken the base mechanism of the German machine and redesigned its mechanical precision components to achieve registration tolerances — the accuracy with which each frame of film was positioned before re-photographing — that the commercial machine could not match.
The head of the optical printer department was a man named Vikram Bose, who was thirty-four years old, who had trained as a chemist, had worked for five years in the photographic chemical industry, and who had come to the animation division through a route that was impossible to explain briefly. He was brilliant in the specific, narrow, technically obsessive way of people who have found the exact problem that fits the exact shape of their intelligence, and who become, in the presence of that problem, single-minded in ways that people around them find either inspiring or alarming depending on their relationship to single-mindedness.
He was at the bench beside the modified printer when Karan arrived, running a test sequence.
The test sequence was on the projection screen at the end of the northern quarter: a field of stars.
Not animation stars — not the flat dots of hand-painted starfields that had appeared in previous Shergill Cinema productions. These were stars with depth and variation in brightness and the specific quality of photographic reality, created by photographing actual light sources through the optical system and compositing them against a black background using the modified printer's superior registration tolerance.
But that was not what Vikram was excited about.
"Watch the glow effect," he said.
He ran the sequence again. In the starfield, one star — larger and brighter than the others — had a quality of luminous energy around it. Not a halo, not a simple brightness increase, but the specific quality of light that is produced when a very intense source is captured through certain optical elements: a diffusion, a radiance, a sense of the light itself having physical weight.
"How did you do that?" Karan asked.
"Multiple exposures. We shoot the star point through a diffusion element on the first pass. Then we shoot it again at a different exposure through a clean lens on the second pass. The combination registers as a single image with the centre sharp and the radiance around it. On the third pass—" Vikram stopped himself. "I'm going too deep into the process. The point is: we can do it. And we can do it consistently, with registration tight enough that it holds over a sequence of frames."
"How many frames have you tested?"
"Sixty-four."
"And it holds?"
"It holds for sixty-four. I don't know the upper limit yet. That's what I'm testing."
Karan looked at the star on the screen. At the quality of light around it.
"What else can you do?"
Vikram's expression changed in the way of someone who has been waiting for this question and has been waiting long enough that the having of it is itself a pleasure. "Come see."
What followed was forty minutes in the optical printer department that Karan had not scheduled and that rewrote the rest of his afternoon. Vikram showed him, in sequence, the experiments that the department had been running for the past three months. The starfield work was the most advanced but it was not the most interesting. The most interesting were the compositing experiments — the technique of combining multiple separately-photographed elements into a single image in a way that made them appear to occupy the same physical space.
A miniature spacecraft — built by the props team from plans that Vikram had given them, a thirty-centimetre model of a vessel shape that nobody in the room had been able to identify as resembling anything from any film they had seen — photographed against a black card and then composited through the optical printer against a photographed starfield background. The result was on the screen at the end of the department: a spacecraft in space. An apparently real spacecraft in apparently real space, created entirely from a thirty-centimetre model, a field of photographed lights, and an optical printer.
"The matte work is rough," Vikram said, indicating the edges of the spacecraft where the composite boundary was visible as a slight luminance discontinuity. "We're working on a better matte technique. But the principle is sound. We can put objects that don't exist in places that don't exist and make them look like they're there."
"How rough is rough?"
"Visible on close examination on a large screen. Not visible from a normal viewing distance on a normal screen. The matte improvement will take another two months."
"What's the limitation on size? If the model were larger—"
"Larger model means more detail and less visible boundary at normal viewing distances. The limitation is the photography, not the model. We need motion control on the camera to do anything with movement."
"Motion control," Karan repeated. "Explain."
"Right now the camera that photographs the model is stationary. We can move the model relative to the camera — we've built a rig for that — but we can't move the camera through a trajectory and have that trajectory be precisely repeatable. To do a sequence where the camera appears to fly past a spacecraft, we need to be able to move the camera through exactly the same path on multiple passes so we can composite the different elements — the spacecraft, the background starfield, any other elements — precisely on top of each other. That's motion control. We don't have it."
"Can it be built?"
Vikram looked at him. "It's a mechanical precision problem. If the Gorakhpur engineering division were to look at the specifications, I think they'd say yes."
"Give me the specifications by Friday."
An engineer on the far side of the department — a young man named Suresh, who had come from the Shergill Aerospace manufacturing division two months ago for reasons similar to Ajit's — looked up from his bench. He had been listening to the conversation while appearing to be working.
"If you give us enough motor control resolution," Suresh said, without being asked, "we could do repeat trajectories to within a millimetre."
"What resolution do you need?" Karan asked.
"I'd need to look at the application requirements. But it's solvable. It's a stepper motor problem."
"Talk to Vikram. Put a proposal together by Friday."
Suresh nodded and went back to his bench.
Vikram was looking at the spacecraft composite on the screen with the expression of someone thinking about something adjacent to the thing they're looking at.
"With enough layering," he said, almost to himself, "and with miniature work at sufficient scale, and with the motion control allowing repeatable trajectories—" He stopped.
"What?" Karan said.
Vikram looked at him. "We could fake space itself. Not suggest it. Not indicate it. Actually fake it. A full, believable, photographically real space environment, built from models and lights and optical compositing, that would be indistinguishable on screen from actual space." He paused. "Obviously actual space is not filmable. But we could make something that looked like what actual space would look like if you could film it."
Karan looked at the screen.
The thirty-centimetre spacecraft hung in its photographed starfield, imperfect at the edges, real at the centre, occupying a space that did not exist in any physical location but that existed completely on the screen.
Something happened in his mind that was not a dramatic event and did not feel like one. It was quiet. It was the specific quality of a connection forming between two pieces of information that had been separately present and had not previously been adjacent.
He looked at the spacecraft.
He looked at the starfield.
He thought about a film he had seen.
He thought: that film has not been made yet.
He left the optical printer department without explaining why he was leaving. He told Priya he was going to walk the rest of the warehouse and that she should go back to Pedder Road and handle the Thursday review scheduling. She looked at him with the attention of someone who has worked alongside a person long enough to know when their internal state has changed without being sure what has changed it.
"Is everything all right?" she asked.
"Everything is very good," Karan said. "I'll be at the warehouse until this evening. I'll call if I need anything."
She left. He walked the warehouse.
He walked it slowly, which was not his usual pace in working environments. He walked it the way you walk a place when you are not looking at the place you are walking through but at something that the place is showing you, something that exists in the overlap between what your eyes are seeing and what your mind is assembling from everything it already knows.
He walked past the background painters and through the multi-plane section and back through the optical printer department and into the section of the warehouse that had not yet been fully organised into the animation workflow — the south end, where a team of four engineers had set up a space that combined, in a way that reflected the specific logic of their collective curiosity rather than any organised institutional intention, elements from several different categories of work.
There were camera rigs. Three of them, in different states of assembly, each representing a different approach to the problem of how to move a camera through a precise controlled trajectory. There was a gyroscopic stabilisation system that one of the engineers had adapted from a military application with a clearance issue that had required two phone calls to resolve. There were tracking systems — mechanisms for photographing a moving subject while keeping it consistently in frame and in focus.
There were miniatures. More than Karan had expected. On the long table along the south wall, a collection of model objects that the engineering team had been building for reasons that were not entirely clear from the documentation — or rather, the documentation recorded what they had built and the techniques used to build them, but did not fully explain what the building was in service of. Spacecraft shapes. Vehicle shapes. A cityscape section, approximately two square metres, constructed from materials ranging from carved wood to cast resin to sheet metal to found objects incorporated for their visual qualities. Building façades that were clearly not Indian architecture — something more futuristic, or more ancient, or both simultaneously.
He stood at the model table for a long time.
The buildings on the model table were not quite any architecture he knew. They were not futuristic in the clean chrome way of science fiction magazine covers. They were ancient and functional and specific, the way that things which have been used for a long time by a lot of people acquire specificity — not designed for elegance but accumulated into existence through use and modification and the particular entropy of things that work getting more complicated as they acquire more functionality. They looked like a city that had been built over centuries by people who were trying to get things done rather than trying to make anything beautiful.
He had a word for what they looked like, and the word was one he had not expected to find applicable in this warehouse in Bombay in June 1973.
The word was: Mos Eisley.
He stood very still.
The thought that was forming was not forming dramatically. It was forming the way that thoughts form when they are the product of two streams of information that have been running in parallel for long enough that their convergence, when it happens, feels less like revelation than like recognition. He had known both things. He had simply not previously looked at them at the same time.
He knew what Shergill Cinema had built in this warehouse. He knew what the optical printer department could do and what the engineering team was working toward and what the background painters had developed and what the multi-plane system was producing. He had seen all of it this afternoon, seen it separately, understood each piece in isolation.
He knew what Star Wars was. He remembered it the way he remembered everything he had seen in his previous life — not with perfect clarity, not as a verbatim record, but with the specificity of something that had mattered. He remembered the quality of it. The feeling in the theatre when it opened. The spacecraft and the aliens and the lightsabers and the specific quality of a universe that was used and dirty and real in a way that science fiction had not previously managed to be. He remembered John Williams. He remembered the opening scroll. He remembered what it had done to everyone who saw it.
He remembered that it had not been made yet.
George Lucas had not made it yet.
Which meant that nobody owned it.
Which meant—
He stood at the model table with the Mos Eisley cityscape in front of him and held that thought for a long time. Not dramatically. Not with the feeling of a man standing at a turning point in history. With the cold, clear, specifically industrial feeling of a man who has identified an opportunity and is in the process of determining whether the opportunity is real.
Was it real?
He went through it systematically. Not because systematically was the only way to go through it, but because going through it any other way would have produced excitement rather than clarity, and clarity was what he needed.
The film required visual effects at a scale and quality that had not previously existed. That was the first requirement. Without it, the film was not the film. Without the effects, Star Wars was a science fiction film with bad production values and audiences would correctly conclude that the universe it was depicting did not exist, which would make them not care about the people in that universe, which would make the film fail. The effects were not ornamental. They were constitutive.
Did Shergill Cinema have a path to those effects?
He looked at the warehouse.
The optical printer department: the composite work, the matte technique under development, the starfield photography. Not there yet. Approaching.
The engineering team's motion control work: not built yet. Specified. Buildable, according to the engineers who had listened to the problem. The Gorakhpur aerospace engineering division could contribute to the mechanical precision requirements.
The miniature work: demonstrated. The models on the table were not professional VFX miniatures — they were experimental constructions, built by engineers exploring what was possible rather than by model-makers executing a brief. But the capability was there. The precision manufacturing capability that Shergill's steel and aerospace operations had developed could produce miniatures at a quality level that the current experimental work did not yet achieve.
The background systems: the multi-plane work, the Pahari-adapted spatial conventions. Not directly applicable to science fiction backgrounds. But the underlying technology — the optical system, the compositing approach — was.
He thought about the semiconductor division in Gorakhpur. About the signal processing work that had gone into the S-27's radar systems. About the specific capabilities that precision electronics manufacturing provided that had no obvious application to cinema and that he was now, standing in this warehouse, beginning to see an application for.
He thought: Shergill already has perhaps forty percent of what this film requires, built accidentally, scattered across divisions that do not know they are building it.
The thought arrived quietly and stayed quietly.
He looked at the Mos Eisley cityscape for another minute.
Then he walked to the corner of the south end of the warehouse where there was a folding table and two chairs that the engineers used for their informal meetings, and he sat down, and he began to think.
He was still thinking three hours later when Vikram Bose found him.
The optical printer department head had been looking for him since six o'clock — Karan's operations director had called asking his whereabouts and Vikram had taken it upon himself to find him, moving through the warehouse section by section until he discovered his employer sitting at the folding table in the south end with a legal pad in front of him that was covered in handwriting and diagrams that Vikram, looking at them from a respectful distance, could not fully read.
"Mr. Shergill. Priya Verma is asking—"
"Tell her I'll be home by nine. I'm staying here."
Vikram hesitated. He was thirty-four years old and had worked for three employers before this one and understood, from three employers' worth of experience, the difference between a moment when an employer wants to be left alone and a moment when an employer has found something and needs someone to talk to it with. The distinction was not always obvious and making the wrong call had costs in either direction.
He looked at the legal pad.
He read, upside down, the words at the top of the first page.
A long time ago in a galaxy far, far away.
He looked at Karan.
"Are you working on something new?" he asked.
Karan looked up. He looked at Vikram for a moment with the specific assessment of someone who is deciding whether the person in front of them is someone they can say the next thing to.
"Sit down," Karan said. "I want to ask you something."
Vikram sat.
"The spacecraft model. The composite you showed me this afternoon. If the model were two metres long instead of thirty centimetres, and if you had the motion control system built to the specifications Suresh was describing, and if you had six months of additional development time — what could you put on screen?"
Vikram thought about it. "Something real. Not approximate — actually real. A spacecraft that flew, that had surfaces and scale and shadow and the quality of being a physical object in space rather than a drawing."
"Could you put a battle on screen? Multiple spacecraft in movement relative to each other, with weapons fire between them?"
Vikram was quiet for longer. "The weapons fire is the hard part. Movement — with motion control, yes. The compositing of multiple moving objects is technically demanding but it's a compositing problem and compositing problems have solutions. Weapons fire is different. We'd need to create light phenomena that don't exist — energy beams, explosions in vacuum, that kind of thing."
"Explosions in vacuum look different from explosions in atmosphere," Karan said.
"Yes. No shockwave. Just radiant energy." Vikram paused. "That's interesting actually. The optical approach to that would be—"
"Don't solve it right now," Karan said. "I'm asking a different question. Is the total capability — everything you've shown me today plus six months of development plus the motion control — is it within the range of achievable? Not easily. Within range."
Vikram looked at him steadily. "Yes," he said. "If the resources were committed at a level significantly above what we have now. But yes."
"How significantly above?"
"Three to five times the current optical department capacity. Additional engineering resources for the motion control and the camera systems. Probably a dedicated miniature construction team — professional model makers, not engineers building experimental objects. And time. The development can't be rushed past certain points because some of it requires the previous step to succeed before the next step can be designed."
"Two years of dedicated development before principal photography."
"That would be my estimate," Vikram said. He was looking at Karan with an expression that had evolved, over the course of this conversation, from polite inquiry through something more focused. "What is this for?"
Karan looked at the legal pad. At A long time ago in a galaxy far, far away.
"I'm going to tell you something," he said, "and I need you to hear it as a technical problem before you hear it as anything else. Can you do that?"
"I've been hearing technical problems for fifteen years," Vikram said. "Yes."
"I have a film in my head," Karan said. "A science fiction film. A space opera — not space exploration, not a prediction of what space travel might look like, but a mythology set in space. Ancient and modern at the same time. A universe that has been lived in for thousands of years and that looks like it. A hero's journey. An evil empire. A mystical energy that binds the universe together and that certain people can learn to use as a weapon and as a sense. Spacecraft battles. Alien worlds. A villain in black armour who breathes like a machine. A princess who is also a general. A young farm boy who is the heir to something ancient and powerful."
He stopped.
Vikram was looking at him.
"And?" Vikram said.
"And the effects required to put that on screen do not currently exist anywhere in the world," Karan said. "No studio has ever made a film with space battles of the complexity I'm describing. No studio has ever maintained the believability of a science fiction universe at this scale. The only way this film works is if what's on screen is real enough that the audience stops noticing the screen. If the audience is ever aware they're watching effects, the film is broken."
"You're describing a level of optical work that nobody has done," Vikram said.
"Yes."
"And you want to do it here."
"I want to build what's required to do it here," Karan said. "I don't want to make this film with what exists. I want to build what the film needs, and then make the film."
Vikram was quiet for a long time. The warehouse had quieted around them — it was past seven in the evening and most of the team had gone home, leaving the large space with the specific quality of emptiness that working spaces have after the people have left: not vacant, but resting.
"The motion control," Vikram said finally, thinking aloud rather than speaking to Karan directly. "If the Gorakhpur team gives us the mechanical precision we need, and if Suresh designs the motor control correctly, we could do trajectories that are repeatable to within tolerances that the compositing can handle. That's the foundation. Everything else builds on that."
"Everything else builds on that," Karan agreed.
"The matte work needs to improve. The matte work is currently the limiting factor in how believable the composites are." Vikram was going through it systematically, the way Karan had gone through it earlier but with the specific knowledge of the practitioner rather than the oversight knowledge of the person watching the practitioner work. "We need a different matte technique. The blue-screen process — we've been experimenting with it. If we can get the blue-screen matting clean enough, the compositing believability goes up significantly."
"How clean do you need it?"
"Cleaner than we can currently do it. The problem is lighting consistency. If the lighting on the subject photographed against blue screen doesn't perfectly match the lighting implied by the background it's being composited into, the eye registers the discontinuity. The brain doesn't know what's wrong, but it knows something's wrong."
"Can we solve that?"
"We can solve the technical part. The lighting matching requires someone with the cinematographic understanding of how light behaves in different environments. For space sequences — light in vacuum from a single source at astronomical distance — the lighting is actually simpler than for a lot of other environments. Single source, no atmospheric diffusion, hard shadows. The problem is simulating that consistently."
"Find whoever understands that best," Karan said. "International, if necessary. There are people in Hollywood who have been working on this kind of problem. Find out who they are."
"Discreetly?"
"Very discreetly," Karan said. "I don't want anyone to know what we're building until we're far enough along that the knowing doesn't matter."
Vikram nodded slowly. "The miniatures," he said. "The spacecraft you're describing — if they're meant to look like used machinery, like things that have been flying for decades, the model construction is a specific craft. The weathering, the detail at scale, the way wear and maintenance marks are distributed. That's not engineering. That's—"
"Art and engineering together," Karan said. "Find people who can do both."
"How large a team are we talking about?"
Karan looked at the legal pad. At the diagrams he had been drawing for the past three hours. At the notes that were his attempt to reconstruct, from memory that was not complete and not perfectly ordered, the essential architecture of something that did not yet exist.
"Large enough to do it right," he said. "Whatever that number is."
He drove home at nine-thirty. The Malabar Hill residence was quiet when he arrived — the household staff had retired, the house was in the evening state of a large building that has been actively inhabited all day and is now resting into itself.
Sakshi was in the study. She had adapted to his irregular hours the way practical people adapt to the permanent facts of the life they have chosen — not by pretending the irregularity was ideal, but by structuring her own time around it in a way that meant it did not impose on her more than she was willing to let it impose. She had her own work: the charitable foundation she ran, the educational programmes she had developed, the institutional relationships she maintained. She had her own life inside the life they shared. This was, Karan had concluded some years ago, the reason the sharing worked.
She looked up from the book she was reading when he came in. She looked at his face.
"What happened?" she said. Not alarmed — observant. The tone of someone who has learned to read the specific quality of her husband's face after long days.
"Nothing happened," he said. "I had an idea."
"Sit down," she said. "You look like you've been sitting in the warehouse for three hours."
"I have been sitting in the warehouse for three hours."
"Sit down here, then. Different sitting."
He sat. She put the book down. She had learned, over the time of their marriage, that when Karan described having an idea it generally meant something that would occupy a significant portion of the next several years of their lives in ways that were not always predictable in advance, and she had developed a specific set of listening skills calibrated to the receiving of ideas of that scale.
"What kind of idea?" she asked.
He looked at her. He thought about how to explain it.
"You know films," he said.
"I watch your films, yes."
"Not the Shergill films. Films in general. Have you seen many Hollywood films?"
"Some. The ones that come through properly. Why?"
"Have you seen science fiction films?"
She considered. "The American ones? The ones with rockets and aliens?"
"The ones with rockets and aliens. Have you seen any?"
"A few. They always look quite cheap."
"They do. They look cheap because making space look real on screen is extremely technically difficult and nobody has quite solved it yet." He paused. "I want to solve it."
She looked at him. "You want to make a film about space."
"I want to make a specific film about space," he said. "A very specific one. A film that has never been made. A film that — if it's made correctly — will be unlike anything anyone has seen."
"What kind of film?"
He thought about this. He had been thinking, in the warehouse, about how to describe it in terms that captured the architecture without requiring the listener to have seen something that didn't exist yet. The problem was that the film's power was the thing you couldn't describe — the experience of being in it, the specific quality of being transported into a universe that was completely real and completely impossible simultaneously.
"You know the Ramayana," he said.
"Obviously."
"The Ramayana is a specific kind of story. A hero with a destiny he doesn't yet know he has. An evil force of enormous power. A guide who teaches the hero the skills he needs. Companions who join the journey. A rescue. A final confrontation. Good against evil with the entire universe at stake."
"Yes," Sakshi said. "That's the Ramayana."
"Now imagine the Ramayana. But in space. Thousands of years in the future, or thousands of years in the past, it doesn't matter. A galaxy with a thousand planets. An empire that controls everything and is evil in the very structural way of empires — not because the people in it are individually evil but because the structure of it requires terrible things. Planets being destroyed. Populations in rebellion. And in the middle of it, a young man on a desert planet who discovers that he has the same gift his father had — an ability to feel and use an energy that runs through all living things, that can be used as a weapon, that connects everything to everything else."
Sakshi was listening. "Like the Force?," she said.
Karan stopped. "What?"
She smiled slightly. "I said like the Force. That's what you're describing, isn't it? That kind of energy."
He stared at her. "How do you know that word?"
"I read," she said smugly. "I read a lot. There's been quite a bit written about the idea of a fundamental energy underlying existence. In physics, in philosophy, in religious texts. Force is a reasonable translation of several concepts from several traditions." She looked at him. "Is that what you're calling it? The Force?"
"Yes," he said. "That's what it's called."
"And the young man. The hero."
"He's from a desert planet. His aunt and uncle raise him. He doesn't know his father was one of the warriors who used this energy — they were called Jedi. He meets an old Jedi master who begins to teach him. He meets a pilot — funny, cynical, competent, the best at what he does and aware of it in a way that is more charming than annoying. He meets a princess who is also a rebel leader. And he encounters the villain."
"Tell me about the villain," Sakshi said. She had the tone of someone who is genuinely engaged but who is also waiting for the part of the description that will tell her what the film is really about underneath the surface of what it is about.
"The villain was a Jedi once. The greatest one. He was the hero's father. But he was corrupted — turned to the other side of the Force, the side that uses fear and hatred and the desire for power rather than the balance of things. He is entirely in black. He breathes through a machine — his body is damaged, he lives inside a suit of armour that keeps him alive. His breathing sound is the sound that precedes every terrible thing he does." Karan paused. "When he enters a room, you know everything has gone wrong."
Sakshi was quiet for a moment. "And his son fights him."
"His son fights him. And defeats him, eventually. But not in this film — this film is the first part of three. Like the first book in a trilogy."
"You're making three films."
"Eventually. The first film is sufficient for now." He looked at her. "Can I tell you what the opening is?"
"Please," she said.
"Complete darkness. Stars. And then, from the top of the screen, a spacecraft appears. Moving from right to left, ordinary size, and you think: all right, a spaceship. And then from the top of the screen, following it, a second spacecraft appears. Larger. Much larger. And it keeps appearing — the camera holds still and the ship moves across and it is enormous, it fills the screen, it takes thirty seconds to pass from one side to the other, and it is still coming. The audience understands, in those thirty seconds, that the universe of this film operates at a scale that is beyond what they have encountered."
He stopped.
Sakshi was very still.
"The music," she said. "When the ship appears."
"Enormous. Brass. The kind of music that tells you what you are feeling before you know you are feeling it."
She sat with this for a moment. "Karan," she said.
"Yes?"
"Do you know how you're going to make it?"
"Not yet," he said. "Not entirely. I know what it needs. I know we have the beginning of what it needs. I know the rest has to be built."
"Built."
"The effects technology. The compositing. The miniature work. The motion control systems. The sound design — the sound of that film is as important as the visuals, and sound at that level has never been done in India. Probably never been done anywhere." He paused. "Two years of building before we film anything. Maybe more."
She looked at him with the expression she brought to his ideas of this category — the ideas that were not iterations of things he had already done but genuine departures, things that required building something that did not yet exist before the thing itself could be built. She had seen this expression on his face before. When he had described the S-27 to her the first time. When he had described the BUM petroleum programme. She had learned to read it as a combination of assessment and acceptance — assessment of whether the idea was real, acceptance of what the idea being real would require.
"You're describing the most expensive film ever made in India," she said.
"I'm describing the most expensive film ever made anywhere," Karan said. "If it's done correctly."
"And if it isn't done correctly?"
"It's unwatchable," he said. "There's no middle version of this. Either the audience believes the universe completely, or they don't believe any of it, and if they don't believe any of it, the story — which is a very old story, a story that has worked for five thousand years — doesn't work, because the story requires the universe to be real for its stakes to be real."
Sakshi nodded slowly. "And who directs it?"
Karan was quiet.
"That's the problem," he said. "I don't know."
She looked at him. "You know the story. You know the effects. You know the music. You know the opening sequence with the enormous spacecraft. You know what the villain sounds like when he breathes. You know all of this."
"Yes."
"But you don't know who directs it."
"I don't know who in India can direct at this scale," he said. "This isn't a film about bureaucracy or war or farming. This is a film about a mythology that exists in a universe that doesn't exist, and the making of it requires someone who can hold both the mythology and the universe simultaneously, who understands that the spectacle serves the story and the story lives inside the spectacle, and who has the technical confidence to work with effects technology that has never been used before." He paused. "India has directors. India does not have architects of spectacle."
"Not yet," Sakshi said.
"Not yet," he agreed.
She looked at the book she had set down when he came in. Then looked back at him. "Tell me the villain's name," she said.
"Darth Vader," Karan said.
She tried it. "Darth Vader."
"Yes."
"And the hero?"
"Luke."
"Luke," she said. "Simple."
"Simple names. Simple story. Enormous universe." He paused. "That's the whole trick of it. The simplicity of the story is what makes the scale of the universe bearable. If the story were complicated, the universe would overwhelm it. But because the story is as old and as simple as the Ramayana — the hero, the quest, the teacher, the villain, the love, the sacrifice — the audience always knows where they are, regardless of how extraordinary the surrounding universe becomes."
Sakshi was quiet for a moment. "It sounds," she said carefully, "like something that could change cinema the way Licence Raj changed cinema. But larger."
"Larger," he said. "By an order of magnitude. Licence Raj changed what Indian audiences expected from Indian cinema. This would change what audiences everywhere expected from cinema."
She looked at him for a long moment.
"Go build it," she said. "You're not going to sleep until you've started."
He smiled — genuinely, the specific unguarded smile that appeared on occasions when something that was right had been named correctly. "Not tonight," he said. "Tonight I'm staying here."
"Tonight you can stay here," she said. "Tomorrow you go build it."
He went to the study after she had gone to bed. He sat at the desk and opened the legal pad he had brought home from the warehouse — the one with A long time ago in a galaxy far, far away at the top and three hours of notes beneath it.
The notes were messy. That was the accurate description. They were the notes of a person writing from memory rather than from source material, which meant they had the character of reconstruction rather than transcription — the broad structure clear, the specific details sometimes uncertain, sometimes contradictory, sometimes flagged with questions that he would need to resolve through thought rather than reference because the reference didn't exist yet.
He opened to a new page and stared at the blank yellow surface for a moment.
The problem with writing from memory was that memory was not linear. What he knew about Star Wars was not arranged in any order that corresponded to how the film was organised — it was a collection of images, moments, feelings, and specific details that existed in the specific arrangement of things that had mattered rather than things that had occurred in sequence. The opening spacecraft had lodged first in his memory because it had been the first thing. The breathing of Vader had lodged separately, equally powerful, not attached to a sequence of events but to a quality of presence. Luke looking at the twin suns of Tatooine and the specific musical phrase that accompanied that moment — he remembered that image with complete clarity, the colour of the sky and the silhouette of the figure and the feeling that the image produced, but he was not entirely certain of the sequence of events that led to that moment within the film's first act.
He had to be careful about this. He had to distinguish, as he wrote, between what he knew and what he was filling in from the logic of the story, and he had to flag the fillings-in clearly so that when the time came to develop the screenplay properly, whoever was doing the development knew which elements were recovered memory and which were reconstruction.
He drew a line down the centre of the page. Left side: Known. Right side: Inferred/Reconstructed.
He began to write.
He wrote for two hours.
What he was producing was not a screenplay. He knew enough about screenplays to know that a screenplay was a technical document with specific formal requirements, and what he was writing was prior to that — the architecture of the thing, the bones of it, the essential elements that any version of the film would need to contain for the film to be itself rather than something else.
He wrote the galaxy structure. The Republic that had become an Empire. The nature of that becoming — not a sudden coup but a gradual accumulation of emergency powers that had eventually become permanent, the specific and chilling mechanism by which democracies consumed themselves. He wrote this from memory and found that he remembered it clearly, because it was the part of the story that had made him, when he first encountered it, feel that the story was about something real.
He wrote the Jedi. The nature of the Force — not magic in the sense of arbitrary power but something more like the quality of attention and presence that made certain people different from others. He wrote about the two sides of it, the balance that the Jedi sought and the seduction of the imbalanced power that the dark side offered. He wrote about Vader's turn — not the detail of it, which he remembered imperfectly, but the essential quality of it, which he remembered completely. A man who loved something so much that the fear of losing it had made him capable of the worst things.
He wrote Luke. The specific quality of Luke's beginning — not extraordinary, not obviously heroic, a young man who wanted more than he had and felt guilty about wanting it because what he had was the aunt and uncle who had cared for him. He wrote about the moment of the call — when Luke encountered Obi-Wan Kenobi and understood for the first time that there was a larger world and that he had a place in it. He wrote about the resistance to that call, which was also part of the story and which was necessary because resistance was what made the acceptance meaningful.
He wrote the droids. R2-D2, which he could describe precisely, and C-3PO, which he could describe precisely, and the specific quality of their partnership — one capable of communication across all forms, the other limited to beeps that somehow conveyed everything necessary. He was smiling as he wrote about the droids, which was something he noticed and registered as important information about the film. The droids were funny. The film needed to be funny, in specific places and in specific ways, not as a relief from the seriousness but as a constituent element of the world — because worlds that have no humour are not believable as worlds.
He wrote Han Solo. He thought carefully about Han Solo, because Han Solo was the character he was least certain he could reproduce accurately from memory, not because he remembered him imperfectly but because Han Solo's quality was the quality that came from casting rather than from description. On the page, Han Solo was a cynical, selfish, talented pilot who did not believe in the Force and whose character arc was the discovery that belief in something larger than self-interest was not incompatible with being Han Solo. On the page, this could be described. On screen, it required a specific actor, and the specific actor was not someone Karan could identify.
He wrote: Han Solo. Find the actor.
He wrote the Death Star. He was careful about the Death Star, because the Death Star was the centrepiece of the plot's moral architecture — the evil empire's capacity for absolute destruction made concrete, made physical, made into a thing you could see and understand as the scale of what was at stake. He wrote the scene of Alderaan's destruction, which he remembered with complete clarity because it was the scene that made the stakes real. Before that scene, the empire was described. After that scene, the empire was felt.
He wrote Obi-Wan Kenobi. He wrote the specific quality of Obi-Wan's wisdom, which was not the wisdom of someone who had all the answers but the wisdom of someone who understood which questions mattered. He wrote the moment of Obi-Wan's death — letting himself be killed rather than killing Vader, because Obi-Wan understood something about the path that Luke needed to walk that required Obi-Wan to be gone. He wrote this from memory and was not certain he had the detail right and flagged it with a note: Review this. The mechanism matters. The meaning is clear. The mechanism may need refining.
He wrote the Force ghost. He wrote it and then looked at it and thought: this is going to require a visual effects solution that does not currently exist.
He added it to the list of effects problems. The list was already long.
He wrote Princess Leia. He thought about Leia carefully because Leia was the most unusual element of the story and the one that would be most challenging to explain to producers and financiers who were accustomed to the role that female characters played in Indian cinema. Leia was not a love interest in the conventional sense. She was a military and political leader who happened to be in the position of requiring rescue, and she spent most of the film being annoyed by the quality of the rescue and conducting the remainder of it more efficiently than the rescuers. She was funny in the specific way of someone who is genuinely competent surrounded by people who are less competent and is trying to be patient about it.
He wrote: Leia must be played by someone who is genuinely intimidating. The audience must believe that she commands.
He wrote the cantina. He spent fifteen minutes on the cantina, because the cantina was the moment in the film where the universe fully revealed its scale — not through the spacecraft or the Death Star or the politics of the Empire, but through the density of different species occupying the same bar, each with their own biology and their own agenda and their own history, all of which was visible in the design of the character rather than explained in the dialogue. The cantina told you that this galaxy had been populated for a very long time by an enormous variety of life, and that all of that variety had produced a universe in which nobody found a cantina full of aliens particularly remarkable.
He wrote the music. He wrote: John Williams. And then thought: there is no John Williams in India in 1973. There may be no John Williams anywhere in 1973 in the sense I need.
He wrote: The music must be orchestral. Full orchestra. The main theme must be immediately recognisable as the theme of this film and no other film. The theme of Luke — heroic, ascending, unfinished. The theme of the Empire — brass, relentless, the music of organised power. The cantina music — jazz, alien jazz, the universe having a good time. He wrote this and knew that he was describing what the music needed to do rather than what the music was, and that the difference between those two things was a composer, and the composer was a problem he did not currently have a solution for.
He wrote the lightsaber. He spent a long time on the lightsaber because the lightsaber was both the film's most memorable image and its greatest effects challenge. A blade of pure energy, luminous from within, that could cut through metal and deflect blaster fire — this required a visual effects solution that did not exist. The rotoscoping of each frame was the approach that his incomplete memory suggested, but he was not certain of the detail and flagged it: Lightsaber visual effects — research optical approach. Consider: practical element plus optical enhancement per frame. This is a critical problem.
He wrote the trench run. He spent thirty minutes on the trench run, because the trench run was the climax and the climax was the test of everything the film had built. Not only the effects — though the trench run would be the most technically demanding sequence in the film — but the emotional architecture. The pilot failures. Luke's decision to use the Force rather than the targeting computer. Han Solo's return. The moment of the torpedo. He wrote all of it and found that he remembered it clearly enough to write it and not clearly enough to be certain he had it exactly right.
He wrote at the top of the trench run notes: This must be perfect. The audience has spent two hours building to this. If the execution fails, the film fails. The effects, the editing, the music, the acting — everything converges here. Plan accordingly.
At two in the morning he put the pen down.
He had thirty-seven pages of notes. They were messy and incomplete and flagged in a dozen places with questions he could not yet answer. They were also, he was reasonably certain, the essential architecture of a film that would not exist without them.
He read through them once, quickly.
The scope of what he was facing was clear. The visual effects problem was the largest single problem, but it was a solvable problem — technical problems were solvable problems, they required time and resources and the right people but they had solutions. The sound design problem was also solvable, though the solution required finding people he had not yet found. The casting problem was solvable. The score was solvable.
The director problem was the problem he could not currently see a solution to.
He sat with it for a while.
The film required someone who understood mythology — the deep structural grammar of hero's journey stories, the reason they worked, the specific things they required to work. It required someone who understood spectacle — not the spectacle of emotion, which Indian directors handled supremely, but the spectacle of scale, of physical reality at a magnitude that exceeded ordinary experience. It required someone who was comfortable with technology — with the specific creative constraints and opportunities of effects work, with the relationship between what was imagined and what could be captured. It required someone who trusted simplicity — who understood that the ancient story at the centre of the film was what the audience was actually there for, and that the universe surrounding it served that story rather than substituting for it.
He did not know who that person was.
He wrote at the bottom of the last page: Director. This is the constraint that determines everything else. Find this person first.
Then he sat for a moment longer.
Then he wrote, on a new page, in large letters:
PROJECT STAR WARS
He looked at it.
He put the pen down. He went to the dining room. He made himself a cup of tea. He stood at the window that looked out over the Malabar Hill darkness, the city below invisible in the specific blackness of a Bombay night with overcast, the Arabian Sea somewhere in the darkness beyond the lights.
He thought about Walt Disney standing in a converted warehouse on Hyperion Avenue in 1934 with a drawing of a dwarf, not yet knowing what Snow White would require to build. Disney had known the story. He had known he needed to build something new to tell it — not a new kind of story, the story was old, but a new kind of telling that required capabilities that did not yet exist.
He thought about George Lucas — the George Lucas who did not yet exist in this timeline, who was somewhere in America in 1973 working on American Graffiti, who was carrying in his mind the architecture of a film that he had not yet convinced anyone to fund and that would require, when he finally made it, the building of an entirely new visual effects company, the development of entirely new technologies, the assembly of a team of specialists who did not yet know that their specialty was what they would become specialists in.
Both men had built what they needed to build because the film required it. Both had started with the story — or rather, both had started with the image. The image of what they wanted the audience to see. And then had built backwards from that image, identifying each component that the image required and finding or building each component in turn.
That was the method.
Karan put the tea down and went back to the study. He opened a new page on the legal pad and wrote at the top: What the film requires. Build backwards.
He began to list.
The visual effects division: current state, required state, path from one to the other, resources required, timeline. The motion control engineering: specifications, who builds it, timeline. The miniature construction: current experimental state, professional state required, people needed, timeline. The sound design capability: what India currently has, what the film requires, how to close the gap. The score: what the film requires from music, what capabilities exist or need to be developed or what talent needs to be identified. The director: constraints, qualities required, how to find the person, what to do if they don't exist in India.
He wrote for another hour.
At the end of the hour he had a second set of notes, less emotional than the first set, more analytical. The first set was the film. The second set was the construction programme for the film.
Both sets together were, in approximately thirty pages of handwritten notes on a yellow legal pad, the beginning of something that did not yet have a name except for the two words he had written at the top of the fresh page in the middle of the session.
Project STAR WARS
In the morning he called his operations director for the film division at seven.
"I need a meeting," he said. "Today. This afternoon. The optical printer team, the engineering team, the animation leadership. Not the full studio — the technical leadership of each division. Conference room at the warehouse."
"How long a meeting?"
"As long as it takes. Clear my afternoon."
"The Thursday review—"
"Move it to Friday morning. Clear the afternoon."
"Done. Anyone else?"
He thought. "Call Gorakhpur. I need Nair's equivalent in the aerospace engineering division — whoever is leading the precision mechanical work. I need them available by phone this afternoon, ready for a specific technical question."
"The aerospace division?"
"Yes."
A pause. "What's the meeting about?"
"A new project," Karan said. "I'll explain it this afternoon."
He put the phone down.
He picked it up again and called the animation warehouse directly — Vikram Bose, who answered on the second ring with the alert quality of someone who had also been thinking about the previous evening's conversation and had not stopped.
"This afternoon," Karan said. "Conference room. Bring the specifications for the motion control system. Bring the best examples of the composite work. Bring the blue-screen experiment results."
"I have them ready," Vikram said. "I've been preparing since six."
"Good. One more thing. The model table in the south end — the cityscape. Don't move it. I want it in the room for context."
"The Mos Eisley model?" Vikram said.
Karan stopped. "What did you say?"
"The cityscape. The engineers have been calling it Mos Eisley. I don't know where they got the name from."
There was a silence.
"How long have they been calling it that?" Karan asked.
"A few weeks. Since they started building it. I assumed it was someone's name for the design aesthetic — something they'd found in a book, or a technical term I didn't know."
Another silence. Shorter.
"Bring the model," Karan said. "I'll explain the name this afternoon."
He put the phone down.
He sat at the desk with the two sets of notes in front of him for a moment.
Then he picked up the legal pad, stood, and went to find his car.
The afternoon meeting at the warehouse lasted four hours and twenty minutes.
There were nine people in the room: Karan, Vikram Bose, Ajit from the multi-plane section, Suresh from the engineering team, three members of the animation leadership, and two engineers from the optical printer department who had been working on the blue-screen experiments. The Mos Eisley cityscape model was on the table in the corner of the conference room, which was barely large enough to hold it.
Karan did not begin the meeting by showing them the notes. He began by asking Suresh to describe the motion control specifications he and Vikram had discussed the previous evening. Suresh described them. Karan asked the aerospace engineering division contact in Gorakhpur — on the phone, speaker mode, the connection somewhat crackly — whether the mechanical precision requirements were achievable. The aerospace contact said they were, and described the approach. Karan asked for a written specification within a week. The contact agreed.
Then Karan described the film.
Not as a film. As a series of technical problems that needed to be solved to enable a film that he described in sufficiently broad terms that the technical requirements were clear without the narrative being fully disclosed. Space environments. Spacecraft in motion. Alien worlds. Energy weapons. A sequence involving a trench attack on a massive space station involving multiple spacecraft in coordinated movement.
He described each requirement. For each one, he asked the room: do we have a path to this?
The motion control: yes, with the Gorakhpur engineering support.
The space environment compositing: yes, with significant development of the current blue-screen work.
The spacecraft miniatures: yes, if the miniature construction team was built up to professional standards with people who had the right craft knowledge.
The energy weapons: not yet. The lightsaber visual effect — Karan described it in abstract terms as a luminous blade of coherent energy — required a per-frame optical treatment that nobody in the room had a complete solution for. Vikram said: rotoscoping per frame, with a practical element for the actor reference. The optical enhancement per frame would be possible with the modified printer. Would it be consistent enough across a long sequence? Unknown. Required testing.
The alien characters: prosthetics and costume construction. Not an optical problem. A craft problem. Required people with creature design and costume construction experience. Did those people exist in India? Unknown. Required investigation.
The large-scale space battle sequence: the room went quiet when Karan described this in enough detail for the scope to be clear. Multiple spacecraft in coordinated motion, photographed from multiple angles, composited against starfield backgrounds with weapons fire between them. The compositing complexity was a different order of magnitude from anything the department had previously attempted. Vikram said: possible, in principle. With three times the current capacity and the motion control system and eighteen months of development. He said it as an engineer states a fact rather than as someone seeking to be impressive.
Karan wrote down the estimates as they were generated. He asked for specificity where he received vagueness. He pushed back on optimism when he heard it and on pessimism when he heard that. He was running the meeting the way he ran all technical meetings — toward precision rather than toward comfort, toward the honest picture of what existed and what didn't rather than toward the reassuring picture of what was achievable with appropriate enthusiasm.
At the end of the technical review, he put the pen down.
"I'm going to tell you what the film actually is," he said. "And I need you to hear it as the application that the technical requirements serve. Not as a concept to be excited about. As the specification that the technical programme is building toward."
He told them.
He did not tell them everything — he told them the essential architecture, the structure of the story, the quality of the universe. He told them about the opening sequence with the enormous spacecraft. He told them about the hero and the villain and the Force. He told them about the Death Star.
The room was quiet when he finished.
Then Ajit said: "The opening sequence. The enormous spacecraft coming across the screen. The camera holds still and the ship moves. Does it fill the screen completely at any point?"
"Yes," Karan said. "It should fill the screen completely. The audience should feel that they are looking at something whose scale is beyond their ability to fully comprehend."
"How long is the ship?"
Karan thought. "Several kilometres."
"A several-kilometre spacecraft photographed so that it fills the full width of the cinema screen. To achieve that scale we need a model at sufficient size that the detail is visible without enlargement, photographed close enough that the full width of the model fills the frame, with motion control allowing the camera to track along the model's length." Ajit had a pencil out and was drawing. "The model would need to be at least three metres. Probably four. The tracking system would need to move the camera along four metres of model length in a trajectory that was precise to—" He looked at Suresh.
"Millimetre tolerance," Suresh said. "For the compositing to work."
"A four-metre spacecraft model with millimetre-tolerance tracking." Ajit looked at his drawing. "That's a different order of complexity from the thirty-centimetre model."
"Yes," Karan said. "That's why we're building what we need to build before we film."
The model on the table in the corner was getting looks. The Mos Eisley cityscape, its streets and structures and the accumulated visual logic of a place that had been lived in for centuries. Suresh, who had been looking at it since the meeting began, said: "That's what the film looks like."
"That's the texture of the film's world," Karan said. "Everything that exists in this universe exists because people or beings have been using it for a long time. Nothing is clean. Nothing is new. The spacecraft are dented and dirty and patched. The cities are old and layered. The costumes are worn. The only things that are clean and new are the things the empire makes, because the empire produces things for the projection of power rather than for use."
Vikram had been listening to this with the expression of someone fitting a technical requirement to an aesthetic principle. "The surface detail on the spacecraft models," he said. "For this to work, the surface detail has to be at sufficient scale that it reads as texture rather than as noise at the camera distances we're working at. That's a model construction problem."
"It's a model construction problem that requires people who know how to build model surfaces," Karan said. "Find them. International if necessary. I don't want the best people India currently has for this work. I want the best people for this work, wherever they are."
He looked around the room.
"I'm going to describe what we're building," he said. "And I want everyone to be clear about what it is before we leave this room."
He looked at the notes. "We are building a visual effects division of a kind that does not currently exist anywhere in India and that does not fully exist anywhere in the world. We are building it for a specific purpose — to make a film that requires capabilities that no studio currently possesses. We are building it now, before the film, because the film cannot be made without what we build." He paused. "The division will be called Indian Motion Labs. IML. It is not public. It does not exist in any external communication until I say it exists. Inside this warehouse it is the name of the programme. Outside this warehouse it does not yet have a name."
He looked at Vikram. "You lead it. You report to me directly. Your first three months: the motion control specification finalised and submitted to Gorakhpur for engineering, the blue-screen technique development accelerated to full priority, and a talent identification programme for the miniature construction, creature design, and optical specialties we need. International talent search. Quietly."
He looked at Suresh and Ajit. "Your first priority: the motion control system. Working prototype within six months. Production system within twelve."
He looked at the animation leadership. "The animation division continues its current programme. The IML work is separate. There will be resource sharing — some of the optical work, some of the engineering — but the animation programme does not slow."
He stood.
"There's one more thing," he said. "The director problem."
He looked at the room. "India has directors who can do every kind of film we have made. India does not currently have a director who can do this film. Finding that person — or developing that person — is a problem that I am not solving in this meeting. I am naming it so that everyone in this room understands it exists. The technology can be built. The story is written. The team is being assembled. The director is the constraint. When we find the director, everything moves to production. Until then, we build."
He picked up the legal pad.
"Questions?" he said.
Vikram asked: "The sound design. You mentioned that the sound design is as critical as the visuals. Is that something IML addresses or something separate?"
"Separate," Karan said. "The sound design of this film is a creative problem before it is a technical problem. The technical problem is significant — we need a sound infrastructure that doesn't exist here. But the creative problem is primary. I'm not solving it today."
Vikram nodded. "The music."
"Not today," Karan said. "The music is also not today. The film needs a score of a specific quality and ambition that I haven't found a composer for. That composer exists or will exist. Finding them is another problem that is not today's problem."
The meeting ended.
The room emptied. Karan stood with Vikram after the others had gone, looking at the Mos Eisley cityscape model on the table.
"The engineers who built this," Karan said. "The ones who named it."
"Bashir and Rajan," Vikram said. "Bashir did the structure design, Rajan did the surface detail work."
"Tell them they named it correctly," Karan said. "And tell them I want them on the IML miniature team."
Vikram smiled slightly. "They'll want to know what the full project is."
"They'll find out. Give them the opening sequence description. The enormous spacecraft. Tell them to start thinking about what a several-kilometre spacecraft looks like at the surface level — what the panels are, what the exhaust ports are, what the antennas and sensors and access hatches look like. Tell them to start thinking about what a thing that was built to last and has been flying for decades looks like."
"And the team they'll need around them?"
"Build it," Karan said. "Whatever you need. I'll approve it."
He picked up the legal pad. He looked at the thirty-seven pages of notes and the list of technical requirements and the name at the top of the fresh page.
Project STAR WARS
He put the pad in his bag.
He looked at the warehouse around him — the background painters finishing for the day, the optical printer department still running its tests, the engineering team in its corner with the camera rigs in various states of assembly, the Mos Eisley cityscape on the table, the model table along the south wall with its spacecraft shapes and its vehicle shapes and the accumulated experimental ambition of a group of engineers who had been building things without fully knowing what they were building toward.
Now they knew.
He walked to the warehouse door.
At the door he stopped.
He turned back to Vikram, who was still standing by the model table.
"Begin," Karan said.
He walked out into the Bombay evening.
That night, lying awake at one in the morning with Sakshi asleep beside him, he thought about the director problem.
It was the problem that everything else depended on and that nothing he had done today had solved, and it was the problem that kept him awake when the other problems did not, because the other problems were technical problems and technical problems had solutions and the director problem was a human problem and human problems were harder.
What the film needed from its director was not one thing but a combination that was difficult to find combined. The mythology — the director needed to understand the deep grammar of hero's journey stories, to feel where the story's emotional truth was and to trust it rather than decorating it. The spectacle — not the spectacle of emotion, which Indian film had developed to an extraordinary level, but the spectacle of physical reality at impossible scale. The technology — the director needed to be not merely comfortable with effects work but genuinely curious about it, needed to see the effects as creative tools rather than as practical problems that other departments solved. The simplicity — the director needed to be able to look at a universe of enormous complexity and ask: what does the story need, and what does it not need?
He thought about this.
He thought about the fact that this director might not exist yet in the form the film required. George Lucas had not been the director of Star Wars until Star Wars had made him the director of Star Wars — the film had required of him capabilities that his previous work had not fully demonstrated, and he had developed those capabilities in the making of the film itself. The process of making the film was part of what created the director the film needed.
Was there someone in India who could be that person? Who could grow into it?
He did not know. He did not know enough about the current generation of Indian filmmakers to know. He knew the directors whose work he had seen, but his knowledge was selective and his assessment of their work was based on what they had made, which was not necessarily an accurate representation of what they were capable of making given the right conditions.
He would need to look. Carefully, systematically, without announcing what he was looking for.
He thought about whether the director might not be Indian. He held this thought for a while without resolving it. The film's universe was not specifically Indian. The story was universal — it was the hero's journey, which was every culture's story. The specific texture of the film he had in his head was not culturally specific in the way that required an Indian director. But making this film as an Indian production, funded by Indian capital, produced by an Indian studio — there was a value in having an Indian director that went beyond the practical. The claim that India could build this thing, could tell this story at this scale — that claim was stronger with an Indian director than without one.
He would look for an Indian director first.
If the search failed—
He left the thought unfinished. The search had not yet begun.
He thought about George Lucas at USC film school in the late 1960s, a student making short films with a technical curiosity about what cinema could do that his peers did not fully share. He thought about Walt Disney in 1928 with a drawing and an idea and a stubbornness that was partly personality and partly the specific stubbornness of someone who has seen something clearly and cannot settle for the lesser version.
He thought: I have seen the film. I know what it is. The task now is to build from what I know toward what I've seen. One problem at a time. Motion control first. Blue-screen second. Miniatures third. Sound fourth. Director when the other problems are far enough along that the director can see what the film is becoming and understand what it requires.
The task.
He turned over.
In the morning, the task would continue.
Project STAR WARS had begun.
End of Chapter 124