For all the extravagant things that happen in RRR, one of its production stories begins with a tool anyone can download. Hyderabad-based Makuta Visual Effects used Blender as its principal 3D creation tool while working on S. S. Rajamouli’s film.
The interesting part is not a promise that a laptop can reproduce a blockbuster. It is the distance between access to a tool and the judgement required to build a convincing world with it.
A switch inside a huge production
Makuta co-founder Pete Draper described the studio’s transition in an account published by Blender. After completing a major introductory sequence, the team moved its workflow towards Blender in late 2019. Makuta delivered 700 shots for RRR; that is the studio’s contribution, not a count of every effects shot in the film. Draper’s production account documents the work.
The specificity matters. A blockbuster can involve multiple companies and tools. Turning this into “RRR was made in Blender” would hide the collaboration that makes the story interesting in the first place.
The world around the event
Among the work Draper describes are the street exteriors outside Scott’s Palace in the Komaram Bheem song sequence. For the intermission sequence, assets supplied by another company were brought into Makuta’s workflow and given new lighting and shading. Crowds and foliage were also part of the work.
These details shift attention away from the usual effects conversation, which gravitates towards the most conspicuous creature or explosion. An action sequence also needs a place to happen. Buildings, vegetation, crowds and the relationship between them give the extraordinary event a world to disrupt.
That supporting world has a dramatic job. If everything around the hero feels disconnected, the action has little weight. When the surroundings cohere, exaggeration can feel like a property of the film’s universe rather than an interruption of it.
Free software, skilled work
Blender is free and open-source software, and its licensing information explicitly permits commercial artwork made with it. The project explains those freedoms here. That makes this production story a useful challenge to the idea that a prestigious image must always begin with an inaccessible tool.
It does not make the labour free. Modelling, lighting, revision and coordination still require people capable of deciding what an image needs. A tool’s availability tells us very little about the time, expertise or production resources behind the result.
The democratic promise is access to a starting point, not instant equivalence between a beginner and an experienced studio.
Give the collaborators a name
MPC also lists RRR in its filmography, another reminder that the finished film should not be flattened into a single-company achievement. Rajamouli’s spectacle reaches the screen through a network of contributions.
Looking at Makuta’s account lets us admire something more specific than “good CGI”: a team making decisions about how an imagined place holds together. The software is accessible. The accomplishment is what the artists managed to build between it and the screen.