Chapter 148: The Director
Date: 7 March 1974
Location: Gorakhpur — Shergill Group Headquarters; Bombay — Indian Motion Labs Warehouse; Hyderabad — Various
(Editors note-sorry guys ,had physics exam today ,thats why late chapter today,will work on next today,not sure if delivarable,if god bless me ,then second chapter today too.ENJOY THE CHAPTER)(ALSO IK MANY DONT UNDERSTAND MOVIE STUFF ,NO problem focus on what is hapenning rather than what happened even if you are more political or military novel lover you should understand how diverse country is ,how connected it is,i am not changng india buy making better jet or weapons,those 1 iq authors from chingi countries may hink industries and army is all that country needs but truth is movie has bigger effect on country ,living is difference ,culture is more necssary,today rightly thaught child will become much better human for our country than a jet of today ,thanks do understand me)
The phone on Karan's desk in Gorakhpur rang at 11:22 on a Thursday night.
He was still at his desk because the Arjuna programme's engine specification review had produced three open questions that he had committed to resolving before the end of the week and that he had discovered, at approximately nine in the evening, were not going to resolve themselves by Friday morning without tonight's work. The questions were technical and demanding and required the specific quality of attention that nighttime work in a quiet building produced more reliably than daytime work in a building full of people moving around with their own questions.
He picked up the phone expecting Pillai about the combustion chamber numbers.
"Karan," Priya Verma said. "I found the director."
He set down the pen he had been holding.
"Say that again," he said.
"I found the director," Priya said. "For Star Wars. I found him."
There was something in her voice that was not quite excitement and not quite hysteria and not quite the professional composure she normally maintained under conditions of considerable professional pressure. It was a combination of all three, which was unusual enough that Karan sat back in his chair and gave the call his complete attention.
"Tell me," he said.
"Tell you which part first?" Priya asked. "The part where I found him, or the part where I found him?"
"Those are the same part."
"They're not," Priya said. "The part where I found him is the outcome. The part where I found him is the story of how I found him and I genuinely cannot tell you whether it's a triumph of the human spirit or a complete disaster that happened to produce a good result."
Karan was quiet for a moment.
"Start at the beginning," he said.
"I started at the beginning six months ago," Priya said. "I went everywhere the recipe said to go. Film schools. Theatre directors. Television. Advertising. Young commercial directors. I watched four hundred hours of film in the past six months, Karan. Four hundred hours. I have opinions about the cinematographic choices of every working director in India between the ages of twenty-two and thirty-eight and most of those opinions are not favourable."
"I know," Karan said. "You sent me the reports."
"I sent you the reports," Priya confirmed. "All forty-three of them. And in forty-three reports across six months of looking, what I found was: technically competent people who made conventional films conventionally well, or technically incompetent people who made unconventional films incompetently, or occasionally technically competent people who were making something interesting but small — interested in character and dialogue and the spaces between things, not in the scale of things. Not one person who had the specific combination I was looking for."
"Which is?"
"Visual thinking at large scale combined with mythology and a camera that sees the world as though the world is surprising," Priya said. "That's what Star Wars needs. Not a director who makes good films about people in rooms. Not a director who is technically brilliant but makes films that feel like homework. Someone who looks at a frame and understands that what's in it should be astonishing — not emotionally astonishing but physically astonishing, spatially astonishing, in the specific way that a world you have never seen before and cannot entirely believe is real is astonishing."
"Did you find that person?"
"In the most improbable location imaginable," Priya said.
"Tell me."
"Three weeks ago," Priya said, and her voice took on the slightly strained quality of someone beginning a story that they have already told several times and that gets more improbable with each telling, "I was in Hyderabad. I went to Hyderabad because the casting director at Ramoji Film City mentioned that there was a young man who had been making something called a Science Fiction film in Telugu which was so spectacularly bad that everyone who worked on it talked about it constantly as the worst professional experience of their lives."
Karan was quiet.
"I went to see the worst science fiction film in Telugu," Priya said, "because I thought: whoever is making the worst science fiction film in Telugu is at least making a science fiction film in Telugu, and in 1974 in India, the person making a science fiction film in Telugu regardless of quality is the only person in the country with the specific category of ambition that Star Wars requires."
"That's—" Karan started.
"Unhinged," Priya said. "Yes. I know. But I had been through forty-three reports and I was running out of conventional approaches."
"What did you find?"
"A disaster," Priya said. "An absolute, magnificent, completely inexplicable disaster. The film was called — I cannot make this up — Antariksha Veerudu. Space Hero. It was about an alien invasion of Hyderabad. The aliens looked like men in suits because they were men in suits. The spaceship was a Rajdoot motorcycle with cardboard fins attached to it. The hero defeats the aliens by playing a specific raag on the veena which apparently causes their technology to malfunction, which is actually a completely original piece of narrative logic that I have not seen in any other science fiction film."
"How old is the director?" Karan asked.
"Twenty-four," Priya said. "His name is Arjun Reddy Chakravarti. Not the Arjun Reddy — different person, different spelling — he's from Warangal originally, did his BA at Osmania University in Hyderabad, spent two years at the Film and Television Institute in Pune where he was described to me by his teachers as 'brilliant but ungovernable.'"
"Ungovernable," Karan repeated.
"His thesis film at FTII was forty-three minutes long when it was supposed to be twenty. It was a documentary about a waterfall. He had filmed the waterfall at sixty-three different times of day across one week and edited the entire sixty-three angles into a single sequence that is either the most extraordinary piece of cinematographic patience ever produced at that institute or a complete misunderstanding of the assignment. Two of his professors told me it was genius. One told me it should have failed him. The fourth professor told me he should have been failed AND hired immediately by a major studio."
"What happened to him after FTII?"
"He returned to Hyderabad," Priya said. "He had no money, no connections, and a vision of cinema that was completely incompatible with the Telugu film industry as it currently exists. He spent eight months trying to get a job as an assistant director at any of the major studios in Hyderabad and being rejected by all of them because his only credit was an overlong waterfall documentary. He then decided to make Antariksha Veerudu on a budget of eleven thousand rupees which he raised by convincing his uncle, his two cousins, a classmate from Osmania who runs a printing business, and the owner of the Rajdoot motorcycle to invest in what he described to each of them as 'a commercial Telugu film with entertainment value.'"
"The motorcycle owner invested in a film?" Karan said.
"The motorcycle owner was under the impression his motorcycle would be returned," Priya said. "It was not returned in the condition it left in. The cardboard fins were attached with a form of adhesive that proved to be more permanent than anticipated."
Karan pressed his hand to his mouth. He was laughing. He had not intended to laugh but the image — a Rajdoot motorcycle with permanently attached cardboard fins and an investor waiting for its return — had arrived with such specific improbability that laughing was the only appropriate response.
"The film took eleven months to make," Priya continued. "Three of those months were spent on a single scene where the hero's veena plays the alien-defeating raag, which Arjun Reddy apparently refused to shoot until he had found a way to make the sound of the veena feel physically present in the frame. His solution — and this is real, I saw the footage — was to build a rig that suspended multiple small mirrors around the camera lens and to light the veena so that its reflection multiplied through the mirrors, which created a visual effect where the sound of the instrument seemed to be radiating outward from the image itself."
She paused.
"It worked," she said. "It looked insane, but it worked. In the middle of a film with cardboard spaceship fins and men in polyester alien suits, there is one scene that is genuinely extraordinary — a four-minute sequence in which a young man playing a veena in a field at dusk is surrounded by light that moves as though it can hear the music, photographed with a mirror rig that its creator invented in a studio in Hyderabad on a budget of eleven thousand rupees."
The phone was quiet for a moment.
"Tell me you met him," Karan said.
"Of course I met him," Priya said. "I tracked him down to the editing room where he was cutting the film on a borrowed editing table that the facility owner had lent him for free because he felt sorry for him. He was working on the climax — the scene where the alien leader is defeated — and he was arguing with himself about the pacing."
"Arguing with himself," Karan said.
"He was speaking the two sides of the argument out loud," Priya said. "I stood in the doorway of the editing room for approximately four minutes before he noticed I was there because he was too absorbed in the argument to look up. The argument, as far as I could tell from listening, was about whether the defeat of the alien leader should be faster than the logical pace of the sequence required, because speed would feel more satisfying even though it would technically be wrong, and whether technical wrongness in service of emotional rightness was acceptable or whether it was the beginning of a slope down which all cinematic discipline eventually disappeared."
"What was his conclusion?" Karan asked.
"He decided that the technically wrong but emotionally right version was acceptable in this instance because the audience had invested two hours in wanting the alien leader to be defeated and their investment deserved to be honoured faster than logic required," Priya said. "Then he looked up and saw me standing in the doorway and asked who I was."
"What did you tell him?"
"I told him I was a film producer from Bombay and that I had come to see Antariksha Veerudu because I had heard it was the worst science fiction film in Telugu."
A pause.
"What did he say?" Karan asked.
"He said, 'It's not the worst science fiction film in Telugu. It's the only science fiction film in Telugu, so by definition it is also the best.' Then he asked me if I wanted to watch the footage of the veena scene."
Karan exhaled slowly. "And you watched it."
"I watched it three times," Priya said. "The first time to understand what I was seeing. The second time to understand how it had been done. The third time because I wanted to see it again."
"And then what happened?"
"And then he told me about the rest of the film he actually wanted to make," Priya said. "Not Antariksha Veerudu. The film that had been in his head since he was seventeen years old and that he had been unable to make because nobody had ever given him the budget to make it and that he had been circling around with inadequate resources for seven years, making the waterfall documentary and Antariksha Veerudu and two other short films that nobody ever saw, trying to develop the specific visual language he needed for the film that was actually in his head."
"What is the film in his head?" Karan asked.
"An epic," Priya said. "An Indian epic. He wants to make the Mahabharata — not as it has been made before, not as a mythological with the standard visual language of Indian religious cinema, but as an actual war epic with scale and spectacle and the specific physical reality of a world where the impossible and the real exist simultaneously. He's been working on the visual approach for seven years. He knows exactly what he wants every scene to look like. He has filled six notebooks with shot lists and lighting diagrams and camera movement descriptions for a film he does not have the money to make."
Karan was looking at the wall of his Gorakhpur office. At nothing in particular. At something that was forming in his mind that was not a specific thought yet but was the shape of one.
"He's been building toward scale," Karan said.
"He's been building toward scale on eleven thousand rupees," Priya said. "Imagine what he builds toward with actual resources."
"How did the conversation end?"
"I told him I worked for Shergill Films," Priya said. "He knew who Shergill Films was — everyone in the industry knows who Shergill Films is — and he immediately asked whether we were looking for directors. I told him we might be, for a specific project. He asked what the project was. I told him it was science fiction. He looked at me as though I had said something simultaneously wonderful and terrifying and said, 'How much science fiction?'"
"What did you tell him?"
"I told him I couldn't discuss the details without a confidentiality agreement. He signed the confidentiality agreement I had in my bag — I had been carrying confidentiality agreements for six months in case I ever actually found someone — and then I told him about the project."
"You told him?" Karan said. He was not alarmed, exactly — Priya's judgment was the reason she had been running the studio for two years — but the Star Wars project had been compartmentalised for six months, known only to the IML technical team and to himself.
"I told him enough," Priya said. "A space epic. Epic scale. Multiple worlds. An empire. A hero. Battles between spacecraft. The most ambitious visual effects programme that any Indian studio has ever attempted. I showed him the IML briefing document — the technical one, not the creative one — and I watched his face."
"And?"
"His face did the thing that faces do when a person sees something that matches something they have been carrying in their head for a long time and did not expect to find in the external world," Priya said. "Which is to say: nothing dramatic. The opposite of drama. A kind of very still recognition, the way you look when something arrives that you were not expecting to arrive but that you immediately understand."
She paused.
"He was quiet for about a minute. Then he said: 'The spacecraft — they're not clean and shiny, are they. They look like they've been used.'"
Karan was very still.
"He hadn't been told that," Priya said. "He hadn't been told anything about the design philosophy. He looked at the technical briefing document — which doesn't contain any creative information, just the capabilities we're building — and he understood from that alone that the world being built was not a clean future world but an old used one. Because that was the only kind of world that would require the specific effects capabilities in the document."
The phone was quiet.
"How did you leave it?" Karan asked.
"I told him I would need to consult with the project lead before making any further commitments," Priya said. "He said he understood and that he would like to show me something before I left. He took me to his apartment — he lives in a very small apartment near the Film Studios — and he showed me the six notebooks."
"What are in the six notebooks?"
"Shot lists," Priya said. "Lighting diagrams. Camera movement descriptions. Visual reference sketches. For every major sequence in the Mahabharata he wants to make. He has worked out, in precise detail, how he would shoot the Kurukshetra battle. How he would handle the scale of the armies. How he would make the divine weapons feel physically real without making them look decorative. He has been developing this visual vocabulary for seven years."
"It's the wrong project," Karan said.
"It's the wrong project," Priya agreed. "But the thinking is right. The approach is right. The understanding of how to put large-scale impossible things in the real world in a way that feels true rather than decorative — that's right. The specific project he wants to make is not Star Wars. But the directorial intelligence that project requires is exactly the directorial intelligence that Star Wars requires."
Another pause.
"Also," Priya said, "he told me he's been thinking about space as a visual environment since he was twelve years old, when he read Arthur C. Clarke's 2001 in an English translation and became completely preoccupied with the question of what space actually looks like — not the way science fiction magazines draw it, not the way American films show it, but what it physically looks like as an environment that a person inhabits. He told me he had been trying to develop a visual language for space for years and had no resources to test it."
"Give me his number," Karan said.
"I thought you might say that," Priya said. "I have it. But I want to warn you that he is extremely direct and will not be polite about things he disagrees with. He told me, in the middle of our conversation about the project, that the most common mistake in Indian commercial cinema is confusing visual busyness with visual richness, and that half the decisions made in the Indian film industry are made by people who have never looked at anything carefully enough to know what they're seeing."
"Good," Karan said.
"He also told me that he would only take a directing assignment if he had absolute creative control over the visual approach of the film," Priya said. "Which is a significant demand for a twenty-four-year-old with one uncompleted Telugu science fiction film to his name."
"It's the correct demand for the director of this film," Karan said.
Priya was quiet for a moment. "You're going to call him tonight, aren't you."
"What time is it there?"
"Same time it is in Gorakhpur," Priya said. "Almost midnight."
"Give me the number," Karan said.
The number Priya gave him rang seven times before it was answered.
The voice that answered was awake — not drowsy, not the voice of someone pulled from sleep, but the voice of someone who had been awake and had been thinking about something and who answered the phone with the specific quality of a mind that was already in motion.
"Yes?" it said. In Telugu-accented Hindi, which shifted immediately to English when Karan gave his name. "Mr. Shergill. Priya Verma said you might call."
"She told you I would call tonight?" Karan asked.
"She told me you would call within twenty-four hours of when she called you," Arjun Reddy Chakravarti said. "And that she would call you tonight. So tonight seemed the most likely time."
"You're awake," Karan said.
"I'm editing," Arjun said. "I'm always editing. Sleep is something I do when the editing is finished and the editing is never finished."
"Are you editing Antariksha Veerudu?"
A pause. Then: "Did she tell you about the motorcycle?"
"She told me about the motorcycle," Karan said.
"The cardboard fins are still attached," Arjun said. "The owner has accepted this as the permanent state of his motorcycle. He has decided it gives the motorcycle character. I think he may be correct."
"I want to meet you," Karan said.
"Priya Verma told me about the project," Arjun said. "Not all of it. Some of it. The scale."
"What did you think about the scale?" Karan asked.
"I thought: this is either the most serious thing I have ever heard described or a very elaborate way of identifying directors who will claim to be capable of anything," Arjun said. "Then I thought: the technical briefing document is real. The investment in the effects capabilities is real. The equipment being built is real. Nobody builds a motion control system and a blue-screen compositing programme as an elaborate way of identifying directors."
"No," Karan said. "Nobody does."
"So the project is real."
"The project is real," Karan said.
"The spacecraft," Arjun said. "They're old. They've been used."
"Yes," Karan said.
"The world has been inhabited for thousands of years and it looks it," Arjun said. It was not a question.
"Yes," Karan said.
"And you don't have a director," Arjun said.
"I have been looking for a director for six months," Karan said. "Priya Verma has been looking for a director for six months. We have not found one. She believes she may have found one in an editing room in Hyderabad."
"The waterfall documentary," Arjun said. "She told you about the waterfall documentary."
"She did."
"People always use the waterfall documentary to decide whether I'm a genius or a fool," Arjun said. "The two options are not mutually exclusive. A person can be both simultaneously."
"I'm aware of that," Karan said. "I'd like to meet you this week. Can you come to Bombay?"
"I am already in Bombay," Arjun said.
Karan paused. "Priya told me you were in Hyderabad."
"I was in Hyderabad when she found me," Arjun said. "I finished the edit of Antariksha Veerudu three days ago and came to Bombay because I had been meaning to come to Bombay and the edit being finished was the appropriate moment. I am currently staying with my FTII classmate Dilip Mathur, who edits commercial films, and who has a sofa that is exactly as comfortable as a sofa that belongs to a film editor in Bombay is comfortable."
"Which means not very comfortable," Karan said.
"It means I have been sleeping better than I deserve to at this stage of my career," Arjun said.
"Come to the IML warehouse on Monday," Karan said. "March eleventh. Priya will send the address."
"The Indian Motion Labs," Arjun said. The name had been in the technical briefing document. "The name suggests a degree of institutional ambition that is either completely justified or completely unearned."
"Come Monday and decide which one," Karan said.
"Yes," Arjun said. "I will come Monday."
The call ended.
Karan sat at his desk in Gorakhpur for a moment after putting the phone down.
Through the window the winter night was still and cold. The fields were dark. The compound's security lighting was on. Somewhere in the factory the third shift was running — the sound of it barely audible at this distance, a low continuous hum that was the background noise of a facility that did not stop.
He thought about a twenty-four-year-old director in a borrowed apartment on an editor's sofa in Bombay who had been developing a visual language for large-scale impossible things for seven years on budgets that did not allow him to test anything he had worked out.
He thought about motion control systems and blue-screen processes and six notebooks of shot lists for the Mahabharata.
He thought about the veena scene.
He picked up the phone and called Priya back.
"Monday," he said. "March eleventh. IML warehouse. I want Vikram Bose there. I want Suresh there. I want the motion control prototype operational. I want the blue-screen test footage ready for screening."
"Done," Priya said.
"And Priya."
"Yes?"
"Good work," Karan said. "Six months of forty-three reports and four hundred hours of film and the worst science fiction film in Telugu. Good work."
"The motorcycle," Priya said. "The image of the motorcycle is never going to leave my brain."
"Come Monday," Karan said. "I need you there."
He put the phone down and looked at the Arjuna engine specification still open on his desk.
He picked up his pen.
There was still tonight's work to finish.
Indian Motion Labs Warehouse, Eastern Bombay
Monday, 11 March 1974 — 10:00 Hours
The Indian Motion Labs had expanded significantly since its designation seven months earlier.
In June 1973, when Karan had stood at the folding table in the south end of the animation warehouse and written Project Star Wars in large letters on a new page, the IML had been more idea than infrastructure — a name for a programme that was beginning to organise itself around a vision that only he and Vikram Bose and the handful of people in that afternoon meeting fully understood.
Seven months later, the programme had accumulated mass and capability.
The warehouse itself had been reorganised. The animation division still occupied the eastern end — the background painters and the multi-plane camera work and the projects like Ganesha and other animated films were still there, still running at their established pace. But the other three quarters of the warehouse had been transformed into something entirely new.
The optical printer department had grown from two machines to eight. What this meant in practical terms: an optical printer was a specialized machine that could take multiple pieces of film — say, a shot of an actor, a shot of a background, a shot of an explosion — and combine them onto a single piece of film so they appeared to exist in the same space. It was the fundamental tool of visual effects work. The six additional printers that Vikram's team had built themselves represented not just more machines but better machines — each one an improvement on the previous, learning from what didn't work, refining what did. The newest printer could align multiple pieces of film with an accuracy of less than a tenth of a millimetre, which was better than anything available from European manufacturers. This level of precision was essential because if the alignment was off even slightly, the audience would see a visible line where the different pieces of film joined together, breaking the illusion.
The motion control section occupied what had been part of the south end and had expanded into a purpose-built annex. Motion control was the solution to a specific problem: if you wanted to film a miniature spacecraft from different angles and then combine those shots, the camera had to move in exactly the same path every time. Exactly. Not approximately. Human camera operators, no matter how skilled, could not achieve this level of repeatability. The solution was a computer-controlled system — a machine that could move a camera along a track in a precise pattern, record that pattern, and repeat it as many times as needed with perfect consistency. Suresh's fourth-generation system could now repeat a three-metre camera movement within three-tenths of a millimetre tolerance. This meant that a shot of a spacecraft model filmed today could be perfectly matched with a shot of the same spacecraft filmed tomorrow, or next week, allowing multiple elements to be combined seamlessly.
The miniature construction section was the newest and most surprising development. In June, miniature capability had meant Bashir and Rajan building experimental models from cardboard and resin out of personal curiosity. By March, the miniature section occupied four workbenches and employed eleven people. This growth represented a fundamental shift in capability — from being able to build rough test models to being able to build production-quality miniatures that would appear in the actual film. The team now included specialists who understood not just how to build models but how to make them appear real when photographed — understanding of scale, of surface texture, of how real metal and machinery weathered with use. This distinction mattered enormously: a model that looked good sitting on a workbench might look fake when photographed, while a model built with proper understanding of how cameras saw things could convince an audience it was looking at a real object hundreds of metres long.
The blue-screen section represented perhaps the most challenging technical problem the IML was solving. The blue-screen process — also called chroma key or travelling matte — worked on a simple principle: film an actor against a bright blue background, then use optical processes to separate the actor from that blue background so they could be placed against any other background you wanted. In theory, simple. In practice, extraordinarily difficult. The challenge was the edge where the actor met the blue — the "matte line." Hair, fabric texture, anything with fine detail created complex edges that were difficult to separate cleanly. If the separation wasn't perfect, you'd see a blue fringe around the actor, or worse, parts of them would become transparent, with the background showing through. Vikram's team had spent seven months developing techniques to make this separation cleaner and more consistent, moving from test footage that demonstrated the principle to a process that was approaching production quality.
This was the facility that Arjun Reddy Chakravarti walked into at 10:17 on Monday morning.
He was twenty-four years old and slight of build, with the specific physical economy of someone who had spent considerable time in small rooms where space was limited and who had learned to be precise about how much space they occupied. He wore a kurta that showed signs of long use. He carried a cloth bag from which the spine of a notebook was visible.
He walked into the warehouse and stopped.
He stood still for approximately thirty seconds — the behaviour of someone who understood how to look at a space, who knew that moving while looking was how you missed things. He was taking in not just what was in the warehouse but how it was organized, what the relationships between different sections suggested about the workflow, what the presence of certain equipment meant about the kinds of problems being solved.
Then he began to walk toward the miniature section, which was nearest the door.
He stopped in front of what the working notes called a Corellian Freighter — a spacecraft model perhaps thirty centimetres long that showed the accumulated modifications of long use. The design had the specific logic of something that had been built for one purpose and then modified repeatedly over decades of operation, with added components and patches and the visual evidence of continuous practical use rather than pristine construction.
He looked at it for a long time without touching it.
Karan watched this from across the warehouse. Watched him examine the model with the attention of someone reading it — not just seeing it but understanding what its construction revealed about the builders' thinking and capabilities.
"The exhaust ports," Arjun said to Bashir, who was at the nearby workbench. "The size relative to the engine housing is wrong. If this were a real ship and this were a real engine, the exhaust geometry would be different. You've made it look right visually but not right physically, and the camera will know the difference even if no audience member can articulate why."
This was an interesting observation. What Arjun was noting: the exhaust ports — the openings where a spacecraft's engines would vent their thrust — had been sized to look good on the model. But if you thought about the actual physics, about how much thrust would be needed to move a ship of this apparent size, the exhaust ports would need to be larger relative to the engine housing. The model looked good sitting on the workbench, but when filmed and presented as a real object, something about it would feel slightly wrong even if viewers couldn't identify what. The camera captured these inconsistencies. An audience might not consciously notice, but the accumulation of small physical impossibilities would undermine the believability of the whole.
Bashir looked at him, then at the model, then at Karan, who had walked over.
"He's right," Karan said.
"I know he's right," Bashir said, with the mild exasperation of a craftsman who has been shown a problem they were aware of and had been planning to address. "We've been meaning to go back to the exhaust section for two weeks."
Arjun looked at Karan, taking a measure of him. Not unfriendly. Not deferential. Attentive.
"Mr. Shergill," he said.
"Mr. Chakravarti," Karan said.
"You can call me Arjun," Arjun said. "Mr. Chakravarti is what people call my father."
"Karan," Karan said.
They shook hands. Arjun's grip was firm and brief — the handshake of someone for whom handshakes were formalities that served their function and no more.
"Show me everything," Arjun said.
The tour of the IML took three hours.
Vikram Bose conducted it, which made sense — Vikram understood the technical language of every system in the facility and could explain each component at whatever level of detail the questions required. Arjun's questions were specific and numerous and demonstrated an understanding that went beyond casual interest.
At the optical printer section:
The machines themselves looked industrial and purposeful — large metal frames supporting film transport mechanisms, optical lenses, and exposure systems. To the uninitiated, they might have resembled oversized projectors or printing presses. The core function: taking multiple pieces of film and optically combining them onto a single output film strip, with precise control over how each element was positioned, exposed, and timed.
"The registration tolerance on the newest printer," Arjun said, looking at the machine. "What's the drift over a 200-frame sequence?"
Registration tolerance — this was about how precisely the film could be positioned in the same spot, frame after frame. Film moved through these machines at twenty-four frames per second. If each frame wasn't positioned in exactly the same spot, images would jitter and shift. Over 200 frames — about eight seconds of film — even tiny positioning errors would accumulate.
Vikram checked his data. "Less than 0.1 millimetres accumulated over 200 frames."
"Good," Arjun said. "For the space battle sequence there are shots where I need to composite six separate passes — two spacecraft, the starfield, the weapons fire, the planet surface in the background, and a reactive light effect on the lead spacecraft's surface from the weapons fire nearby. Six passes needs each pass to be within 0.1 millimetres of the others across 200 frames or the composite breaks. Your printer can do this."
What he was describing: to create a single shot of a space battle, they would need to film each element separately and combine them. The spacecraft models filmed against neutral backgrounds. The starfield — the background of stars — filmed or created separately. The weapons fire — likely animated or created as separate glowing elements. The planet surface — another miniature or painted element. The reactive lighting on the spacecraft — additional passes showing how the light from nearby weapons affected the ship's surface. Six separate pieces of film, all needing to align perfectly when combined. If any element was even slightly misaligned, the shot would fail — you'd see gaps or overlaps, the illusion broken.
"The six-pass composite," Vikram said carefully, "is at the limit of what we've tested."
"Test it," Arjun said. Not as a demand — as a logical conclusion. "Not for this meeting. Before I agree to anything. I need to see a six-pass composite of something to know whether your system can do what this project requires."
At the motion control section:
The motion control rig looked like industrial equipment meeting precision engineering — a camera mounted on a motorized track, with cables running to a control system that Suresh had built and programmed. The track itself was three metres long, with the possibility of extension.
Arjun watched Suresh run a test trajectory — a slow arc across the track, the camera moving at a specific rate. Suresh ran it three times, identical each time.
Arjun watched all three runs carefully.
"The deceleration at the end of the arc," he said. "It's slightly inconsistent between the second and third run. Not in position — in velocity profile. The camera slows down at a different rate on the third run."
Velocity profile — this was about how the camera's speed changed. Position was about where the camera ended up. Velocity profile was about how fast it was moving at each point along its path. Why this mattered: when a camera moved past an object, the object appeared blurred in the direction of movement — motion blur. The amount of blur depended on how fast the camera was moving at that moment. If the velocity changed between runs, the blur would be different, and when you tried to combine multiple passes, the blur wouldn't match. The eye might not consciously notice, but it would see that something was wrong.
Suresh looked at his readout. "The position is within tolerance."
"The position is within tolerance," Arjun agreed. "The velocity profile is not. For most compositing work the velocity profile doesn't matter as long as the position is correct. But for the shot I have in mind where the camera flies past the main spacecraft in a continuous arc, the motion blur on the spacecraft model changes with the camera's velocity. If the velocity profile is inconsistent between passes, the motion blur is inconsistent, and you can see the join in the composite because the blur edges don't match."
Suresh was quiet for a moment, then checked his velocity data.
"That's correct," Suresh said, with the tone of an engineer shown a problem in his own system by someone who wasn't an engineer. The tone was interested, not defensive. "The motor controller has a deceleration curve that isn't perfectly reproducible because it's temperature-dependent. I didn't — I hadn't thought about the blur implication."
"Temperature," Arjun said. "Can you temperature-stabilize the controller?"
They discussed solutions — insulation versus feedback systems — with Arjun suggesting that a feedback loop that adjusted behavior based on measured temperature would be more reliable than simple insulation, which could drift over time.
At the blue-screen section:
Vikram had prepared test footage. This was the fundamental challenge of putting actors into impossible environments: film them against a uniform blue background, then optically separate them from that background and place them against whatever background you wanted. The test footage showed a man standing against blue, then the same man composited against various backgrounds.
What you looked for: the edge where the person met the background. The "matte line." If the process worked perfectly, you couldn't see where the real person ended and the new background began. If it didn't work, you'd see a blue fringe around the person, or worse, parts of them would seem to glow or become slightly transparent.
Arjun watched the footage twice.
"The matte fringe," he said. "Along the subject's hair. You can see it."
"We know," Vikram said. "It's the hardest part of the process. Fine detail — hair, fabric texture — creates matte boundaries that are too complex for clean separation."
What made hair difficult: each strand was thin and partially transparent, with complex curves and overlaps. When the optical process tried to separate "blue background" from "not blue background," these fine details created edges that were neither clearly one nor the other. The result: a visible fringe, a blue halo, a failure of the illusion.
"You need a different blue," Arjun said. "Your current blue is too saturated. A less saturated background blue separates more cleanly from fine detail because there's less colour contrast doing the work and more density doing it. The matte reads density rather than hue."
This was colour theory applied to practical effects work. The blue-screen process worked by identifying "this is blue" versus "this is not blue" and creating a boundary. But identifying blue could be done two ways: by colour (hue) or by brightness (density). A highly saturated blue — a very vivid, pure blue — created a strong colour difference but made it harder to read subtle density differences. A less saturated blue — closer to grey-blue — reduced the colour difference but made density differences more apparent. For fine detail like hair, density-based separation worked better because hair created subtle density variations that were easier to read than colour variations.
Vikram looked at him carefully. "Where did you learn this?"
"I read everything," Arjun said simply. "Every technical publication on optical compositing from every country that produces one. I've been reading them for four years."
He looked at the test footage on the screen, then at his notebook, then began explaining the calculation that supported his analysis — the relationship between colour saturation, density reading, and matte edge quality.
Karan stood back and watched this exchange.
He watched Vikram Bose — who was thirty-four years old and had spent seven months becoming highly knowledgeable about optical compositing — being shown something about his own process by a twenty-four-year-old director from Warangal who had made a science fiction film on eleven thousand rupees.
He watched Vikram's expression shift from cautious professional reception to focused attention — the recognition of someone who understood they were learning something genuinely useful.
He watched Arjun's expression, which remained completely focused on the content of what he was explaining, showing no awareness of or concern for the effect he was producing on his audience. This quality — this apparent constitutional inability to perform — marked him as either entirely genuine or remarkably disciplined. Probably both.
The distinction was important: Arjun wasn't showing off his knowledge. He was solving a problem that he saw in front of him, using tools he had developed through years of study. The knowledge was in service of the work, not in service of his status. This was the temperament the project needed — someone who cared about getting it right more than about being seen to be right.
The lunch break was in the warehouse's small conference room.
Priya had arranged food from a good restaurant nearby — not the closest one, which was mediocre, but a better one two streets away. She understood that the quality of a meal affected the quality of the conversation that followed.
Five people at the table: Karan, Priya, Vikram Bose, Suresh, and Arjun.
Arjun ate efficiently, finishing about eight minutes before everyone else. Not rushing — simply not delaying. When he finished, he opened his notebook and put it on the table.
"The shot list," he said, pushing it toward Karan. "Not for Star Wars. I don't have a shot list for Star Wars yet. This is the shot list for the film I've been building toward."
Karan opened it. The pages were dense with handwriting and sketches. The handwriting was small and precise. The sketches were quick but specific — the kind drawn not for showing others but for fixing ideas in the mind, capturing them before they slipped away.
He turned pages slowly.
The Kurukshetra battlefield. The armies on the plain — sketched first from above, showing the overall arrangement of forces, then from ground level, showing how mass could be conveyed while maintaining individual human presence. The camera was everywhere in these sketches — not fixed like theatre, but moving through the world as though discovering it.
The divine weapons — the astras of mythology. But not depicted symbolically. The fire astra wasn't cartoon flames but the visual quality of heat at enormous scale, the way a forest fire from above looks more like a moving landscape than individual flames. The rain astra wasn't animation rain but the quality of water falling at such volume that it became a substance. The sketches showed each weapon as a problem of physics and light rather than symbolic decoration.
Krishna and Arjuna on the battlefield. The Bhagavad Gita conversation. Multiple sketches trying to solve the visual problem of two people having a philosophical conversation at the centre of mythology's most consequential battle without making it static or falsely dynamic. Each sketch was annotated with what was wrong about it — the intelligence visible not just in the attempts but in the understanding of why they failed.
"The conversation problem," Karan said, pointing at the Gita sketches.
"It's the hardest sequence in the film," Arjun said. "Everyone who has tried to visualize the Gita has either made it static — two people talking, essentially filmed theatre — or has made it visually elaborate in ways that overwhelm the text. Both approaches fail. The visual approach has to hold the same weight as the text without competing with it."
"What's your solution?" Karan asked.
"I don't have one yet," Arjun said. "These are wrong. They're wrong in different ways and the different ways of being wrong tell me something about the shape of the right solution, but I haven't found it."
This honesty was notable. Many directors, especially young ones trying to prove themselves, would have claimed to have the solution or would have defended their attempts. Arjun simply stated that these attempts had failed and explained what that failure taught him. This was the professional approach — understanding that failure was information, not shame.
"You know it when you see it," Karan said.
"I know it when I make it," Arjun said. "Not before."
He looked at Karan directly.
"The film in your project," he said. "The Star Wars. Priya Verma showed me the technical requirements and told me the general story. The hero on the desert planet. The empire. The mythology. The spacecraft battles."
"Yes," Karan said.
"Tell me about the mentor and the hero," Arjun said. "The conversation between them. Before the mentor dies."
This was interesting — Arjun going immediately to what he perceived as a central problem, the same problem he was wrestling with in his own work.
Karan outlined it: the mentor teaching the hero about the Force, about an energy that connects all living things, about learning to feel it and use it. The hero doesn't understand it initially — it seems impossible, mystical. The mentor's job is not to give the hero something but to help the hero discover what they already have.
Arjun was quiet for a moment, looking at nothing, seeing something inside his own head.
"The mentor is pointing at something," he said. "Pointing at the Force, which exists in the world independently. The camera can't show the Force directly — you can't photograph invisible energy — but it can show what the mentor is pointing at. It can follow where they're pointing instead of looking at them explaining. Because the Force isn't in the mentor. It's in the world. The mentor is just showing the hero where to look."
The table was quiet.
Vikram was looking at Arjun with recognition — the recognition of someone seeing a problem solved that they hadn't fully articulated.
Suresh had stopped eating.
Priya was watching Karan's face.
"The waterfall documentary," Karan said.
Arjun looked at him.
"At FTII," Karan continued. "The waterfall documentary that was supposed to be twenty minutes and was forty-three. One waterfall, sixty-three angles, one week. You weren't trying to film the waterfall as a subject. You were trying to learn how to point the camera at something that existed independently of being looked at."
Arjun was quiet.
"Yes," he said. "That's what it was for. The waterfall doesn't care about the camera. The camera has to adjust to the waterfall. Not the other way around. Most films make the world adjust to the camera. I was trying to learn how to make the camera adjust to the world."
"The Force doesn't care about the camera either," Karan said.
"No," Arjun said. "It doesn't."
They looked at each other for a moment — a moment of mutual recognition between two people who understood the same thing about how to approach a problem.
"I'm not going to tell you that you're the right person for this film," Karan said. "I don't know that yet. Neither do you. We won't know until we see what you can do with real resources and real scale. What I know is that the way you think about visual problems is the way the visual problems in this film need to be thought about."
"And?" Arjun said.
"And I want to run a test," Karan said. "Not an audition. A genuine test. I want to give you the resources to solve one problem — one specific visual problem in the film — and see what you produce."
"What problem?" Arjun asked.
"The opening sequence," Karan said. "An enormous spacecraft enters the frame. The camera holds still. The spacecraft moves across from one side of the screen to the other, and keeps moving, and keeps moving. The audience understands, in those thirty seconds, that the universe of this film is at a scale they have never encountered before."
He looked at Arjun.
"How do you shoot that sequence?" he asked.
Arjun was quiet, thinking.
He looked at the table.
He looked at his notebook.
He looked back at Karan.
"The model needs to be at least four metres long," he said. "Possibly six. The surface detail at that length has to be at a resolution that reads as real from the shooting distance — panel lines, mechanical details, weathering, all at a scale where the camera can resolve them. The camera tracks along the length of the model. Slowly. Slower than feels comfortable, because discomfort is how you create the sense of scale. The audience needs to feel that the ship is still arriving when they expected it to have already passed."
He paused.
"The sound arrives before the image," he said. "You hear the ship before you see it. The sound establishes scale first — if the sound is right, the image can exceed it. But if the image arrives first, you've defined the scale before the audience can feel it for themselves."
He looked at Karan.
"I would need two days with the motion control system and two days with the model team and one day shooting tests before I could tell you whether the approach is achievable," he said. "Give me a week."
"You have a week," Karan said. "Starting tomorrow."
Arjun nodded once. The gesture of someone accepting work, not receiving permission.
The Week — 12 March to 17 March 1974
What happened over the next six days became, in the IML team's internal history, simply "the week" — discussed for months afterward not for its productivity, though it was productive, but for the quality of intensity it introduced to the facility.
Arjun arrived Tuesday morning at eight o'clock.
He left Tuesday evening at midnight.
He arrived Wednesday morning at seven-thirty.
He left Wednesday evening at eleven-fifteen, during which interval he had not eaten lunch because he had forgotten lunch existed.
On Thursday he arrived at eight and left at midnight again and ate lunch only because Priya physically placed food in front of him while he was mid-sentence about camera angles.
The week had three distinct phases.
Phase One: Learning the constraints
The first two days were Arjun systematically learning each system in the IML — not the external tour he'd done Monday, which had been observation, but deep engagement, learning not just what was possible but how each system failed. Understanding failure was how you understood capability.
With Vikram, he spent four hours at the optical printer, running test sequences and examining failures. Not "this doesn't work" but "this fails in this specific way under these specific conditions." This knowledge defined the working envelope — the boundary of what could be achieved.
With Suresh, he spent six hours on the motion control system. Not just watching it move but understanding the controller software — why the temperature dependency existed, what would be required to fix it. By day two's end, they had designed a feedback loop together — Suresh providing engineering knowledge, Arjun providing specification of what the system needed to produce for the blur profile to be consistent.
"You've written code before," Suresh observed during this process.
"I taught myself to program because I couldn't afford to hire programmers," Arjun said. "The programming is bad. The logic is correct."
"The logic is very correct," Suresh said. "The programming is also acceptable."
"It's not acceptable, it works," Arjun said. "Those are different things."
Phase Two: The model problem
Day three, Arjun went to the miniature section.
He spent the day examining the existing Corellian Freighter model and asking questions. Not about the model as it was but about what it would need to be for the opening sequence shot. Specifically: at four metres of length, with the camera tracking from one end to the other at a distance of approximately sixty centimetres, what did the surface detail need to be to read as real?
The answer: extremely fine. The camera at sixty centimetres from a four-metre model was equivalent to a person standing six metres from a three-hundred-metre spacecraft. At that distance, panel lines and mechanical details and the patina of use all needed to be present at a resolution the human eye could resolve.
"We need a different approach to the weathering," Arjun told Bashir and Rajan. "You've been weathering the models with paint — applying grime and wear as a surface coat. At the scale we're working at, surface-coat weathering reads as paint, not as real grime."
What he was describing: the difference between painting something to look old versus making something that showed the actual marks of use. Real grime accumulated in recesses and along edges and where surfaces met — following physics, following the flow of fluids and the accumulation of particles over time. Painted grime was applied where it looked good. The difference was subtle but visible to the camera.
"Real grime accumulates according to fluid dynamics and time," he explained. "It has to be modelled structurally, not applied as colour."
"How?" Rajan asked.
"I'll show you," Arjun said.
Over the next two days, he worked with Bashir and Rajan to develop a new weathering process. It involved applying weathering in stages corresponding to different types of accumulation: operational wear first (where surfaces were in contact or in motion), environmental deposits second (where liquids had flowed and evaporated), maintenance marks last (where things had been repaired, leaving specific traces).
The test section Rajan built looked not old but used — which was a different quality. Used implied specific history. Old just implied time.
Bashir examined it carefully. "This is different."
"Yes," Arjun said.
"Can you do this at four metres?" Bashir asked.
"We can if the team has two weeks on the model after structural construction is complete," Arjun said. "The weathering process takes longer than the construction. That's normal. It should take longer. Reality takes longer than construction."
Phase Three: The shot
On day six — Saturday — Arjun shot the test.
Not the actual opening sequence. The model wasn't at four metres yet. The motion control hadn't incorporated the temperature-feedback upgrade. The blue-screen wasn't involved.
But he shot a proof of concept: the existing thirty-centimetre Corellian Freighter model on the motion control rig, tracked by the camera across a starfield background.
He shot it with the specific logic of the opening sequence — camera stationary, model moving through frame, timing calibrated to produce that specific quality of arrival he was after. The spacecraft arriving and continuing to arrive beyond when you expected it to have finished arriving.
Seven takes.
The first three were wrong in ways he could describe precisely and that the team corrected between takes.
The fourth was close.
The fifth was closer.
The sixth take was what he was looking for.
On the sixth take, the thirty-centimetre model crossing the starfield produced something that wasn't what the opening sequence of Star Wars would eventually look like — it was too small, too rough, too limited by the prototype system's capabilities. But it had the quality he was after: the model moved across the frame and the frame was not big enough for it. Not because the model was physically large but because the camera's relationship to its motion made it feel larger than the frame could contain.
Vikram watched the sixth take on the playback monitor.
He watched it twice.
Then he said, in the voice of a technician who has just seen something exceed his expectation: "This is what it's supposed to feel like."
Arjun was already studying the footage, seeing both what was right and what was still wrong.
"The motion," he said. "At the end of the take. The model decelerates slightly as it exits frame because the rig decelerates at the end of its travel. You can see it."
"The feedback loop," Suresh said from across the room. "The upgrade I'm building will fix that."
"When is it ready?" Arjun asked.
"Three weeks," Suresh said.
"I'll be back in three weeks," Arjun said.
He looked at Vikram. "The blue-screen density adjustment. The less-saturated background — have you had time to test it?"
"I tested it Wednesday night after you left," Vikram said. "You were right. The matte is cleaner."
"Show me."
Vikram showed him. The new test footage had the matte fringe reduced by approximately forty percent compared to previous results.
"Keep going," Arjun said. "The saturation level you used is still slightly too high. Drop it another step."
"How do you know where to stop?" Vikram asked.
"You don't stop at a number," Arjun said. "You stop when you can't see the fringe. You'll know when you've stopped."
The Decision — Sunday Evening, 17 March 1974
Sunday, Arjun came to the warehouse not to work on systems but to write.
He sat in the conference room with his notebook and wrote for two hours.
Karan came in at eleven.
Arjun looked up.
"I'm in," Arjun said.
"I haven't offered you the job," Karan said.
"I know," Arjun said. "You said you were running a test. The test is finished. The test told me two things." He turned the notebook to Karan. "First: your technical programme is real and is achieving real things. The motion control is solvable. The blue-screen process is solvable. The miniature construction — with the weathering approach — is achievable. The effects this film requires can be built."
"And second?" Karan asked.
"Second: I know how to make this film," Arjun said.
He said it without drama. A statement of what the week's test had confirmed, delivered with flat certainty.
"Tell me how," Karan said.
Arjun opened the notebook. He had spent the two hours articulating the visual philosophy — not a shot list but the approach that the test had confirmed. He read it clearly and specifically.
"The Star Wars universe is old," he said. "It has been inhabited for thousands of years. Nothing in it is new. This means the camera approaches it the way you approach something that has been real for a long time — not with the wonder of discovery but with the familiarity of being in a world that simply is. The camera doesn't marvel at the spacecraft. The camera moves through space the way a person moves through a familiar environment — purposefully, without ceremony. The marvel is produced in the audience by the cumulative weight of detail, not by the camera's attitude toward that detail."
This was important: in most science fiction films, the camera movements and music signalled "look at this amazing thing!" But if the world of the film was supposed to be ancient and lived-in, the camera should treat it as ordinary. The audience would find it amazing not because the camera told them to but because the accumulated detail of age and use was inherently astonishing.
"The scale is established by relationship," he continued. "Not by size alone. The opening spacecraft is enormous because the camera's motion relative to it communicates that the ship is still arriving when it should have already passed. Scale is duration, not dimension. This applies to every large thing in the film — the Death Star, the planetary surfaces, the armies. Scale is communicated by how long it takes for things to arrive and how long it takes for them to pass."
Again: scale wasn't about telling the audience "this is big." It was about making them experience the bigness through time — through how long they spent watching something move, through the rhythm and pacing that made them feel duration, which made them understand size.
He looked at Karan.
"The Force," he said, "is not shown. It is implied. The camera shows the effect of the Force — objects moving, energy flowing — but never shows the Force itself, because the Force is the underlying reality that everything exists within, and you can't photograph the thing everything exists within. You can only photograph what it does."
This resonated with what they had discussed about the waterfall — not filming the thing itself but its presence, its effects, the evidence of its existence.
He closed the notebook.
"You've been looking for someone who can hold the mythology and the spectacle simultaneously. I can do that. Not because I have done it yet. Because the way I think about visual problems is the same way the problems in this film need to be thought about."
He looked at Karan directly.
"You knew this on Monday," he said.
"I suspected it on Monday," Karan said. "I'm more confident now."
"When do we start?" Arjun said.
"We've started," Karan said. "We started when you told Bashir the exhaust ports were wrong."
Arjun almost smiled — the kind of almost-smile that preceded a question.
"The story," he said. "I need to read all of it. The complete notes you have."
"I'll have them sent to you," Karan said.
"And I need to be here," Arjun said. "Not visiting. Here. Working with the IML team. The shot list has to develop from the capability — I can't develop it separately and bring it to the capability. The capability tells me what's possible, the story tells me what's necessary, and the shot list is what happens when possible and necessary intersect."
"There's a room in the facility," Karan said. "A small office on the second floor. Used to be storage."
"Good," Arjun said. "I don't need much room. I need a desk and a window."
"There's a window," Karan said.
"Does it have a view of anything?" Arjun asked.
"The street," Karan said. "And a piece of the harbour if you lean."
"That's enough," Arjun said.
Three Weeks Later — Karan Returns
By early April, the IML warehouse had a different quality.
Not louder or more active — it had been loud and active since July. But more directed. The difference between a team working toward capability and a team working toward specific shots.
The difference was Arjun.
He was present every day. Not managing — he had no authority over anyone's schedule or workload. But his presence organized the space around purpose. The technical teams had always known what they were building. Now they knew what they were building it for.
When Suresh upgraded the motion control feedback loop, he knew it was so the camera could track past the opening spacecraft without deceleration at the exit.
When Vikram adjusted the blue-screen saturation, he knew it was so the edge of a lightsaber blade would separate cleanly from the background.
When Bashir spent two weeks on the exhaust section of the rebuilt model, he knew it was so the model would read as real at the specific camera distance the opening sequence required.
Purpose changed pace. The team had always moved at the pace technical problems required. But knowing why you were doing something changed the quality of how you did it.
Arjun worked on the shot list — not alone, which surprised the team. Most directors produced shot lists privately, delivering them as instructions. Arjun developed his in conversation with every technical team member, learning from each what was achievable and incorporating that understanding into the sequences he was designing.
The shot list wasn't finished. It would take months. But it was developing, sequence by sequence, from the back of Arjun's notebook into a document that was simultaneously creative vision and production plan.
Karan's Evening — 14 March 1974
Karan drove back to his Bombay hotel at eleven in the evening after spending the day at the IML. He sat in the car with the window slightly open, the March Bombay night coming in with its specific quality — salt and warm air and the distant sound of the city.
He thought about eight months.
Eight months since the afternoon in the warehouse when Vikram Bose had said we could fake space itself and the connection had formed.
Eight months since he had written Project Star Wars in large letters on a new page.
The IML had grown from designation to programme to infrastructure to — now — the beginning of a production. Not yet in production. There was enormous work between now and production. The four-metre model was weeks out. The blue-screen was still being refined. The shot list was months from completion. Casting was still a problem. The script — which was not yet a script but his thirty-seven pages of notes and Arjun's weeks of conversations with those notes — was still a problem.
But the director problem was solved.
And the director problem had been the problem everything else depended on. Without a director, the technical infrastructure was capability without purpose. Capability without purpose was expensive and interesting and ultimately inert.
With Arjun, the capability had purpose.
With Arjun, the motorised mirror rig wasn't just a clever technical solution. It was the visual language of the Force made physical.
With Arjun, the motion control upgrade wasn't just precision engineering. It was the mechanism by which the opening spacecraft arrived with the quality of something that was still arriving when it should have already passed.
With Arjun, the IML was becoming a film.
He thought about the six notebooks of Mahabharata shot lists. About a twenty-four-year-old with a waterfall documentary and an eleven-thousand-rupee Telugu science fiction film and seven years of thinking about how to put large-scale impossible things in the world and make them real.
He thought about finding the worst science fiction film in Telugu to find the director of Star Wars.
He thought: India had directors. India did not have architects of spectacle.
Until it did.
He picked up the phone in the back of the car and called Gorakhpur.
"It's me," he said when Sakshi answered.
"How was the IML?" she said. She knew where he had been.
"We found the director," he said.
A pause.
"Tell me the story," she said.
"The story involves a Rajdoot motorcycle," he said.
"Obviously it does," she said.
He told her the story.
The car moved through Bombay's late-night streets. The harbour was out there somewhere in the dark, and somewhere beyond it the Arabian Sea and the old trade routes that had made this city. And above, if you could see them past the light pollution, the stars that were the background of the film he was building.
A long time ago in a galaxy far, far away.
He had the director.
The work continued.
End of Chapter 148
IML Status — March 1974
Motion Control System (Suresh): Fourth generation operational. Temperature-feedback loop designed. Velocity profile consistency being implemented. Positional tolerance: 0.3mm. Camera track length: 3 metres current, 6 metres extension planned — 6 weeks.
Optical Printer System (Vikram Bose): Eight printers operational (2 original, 6 IML-built). Best registration tolerance: 0.08mm. Six-pass composite tested successfully. Blue-screen matte improvement: 40% cleaner from saturation adjustment. Status: Interior shots ready, exterior/space compositing — 4 weeks.
Miniature Construction (Bashir and Rajan + 9 staff): Weathering methodology rebuilt. Structural reality approach replacing surface-coat approach. 30cm Corellian Freighter model rebuilt to new standard. 4-metre primary spacecraft model structural frame under construction — 8 weeks to completion, 4 weeks weathering.
Director: Arjun Reddy Chakravarti (24). Shot list in development. Visual philosophy established. On-site full-time from 12 March 1974.
Open Problems: Full cast (not yet begun). Complete screenplay (notes stage, requires development with director). Production timeline: Principal photography earliest estimate 1976.