What You Need To Know Before Getting Into Purla
The 2019 animated film about the troll characters inhabiting the fictional archipelago of Purla has gained a following that doesn't really match its box office performance. That mismatch is interesting because it tells you something about how word-of-mouth operates in the animation space right now. The movie centers on a troll named Poppy, voiced by Anna Kendrick, who teams up with a crusty, misanthropic troll called Branch, played by Justin Timberlake, to rescue their tribe from the Bergens—large, hungry humanoids who've never experienced joy firsthand. It's not deep. It's not trying to be. But it is technically competent and its production pipeline produced some genuinely useful case studies for animators studying procedural hair simulation. I spent roughly three weeks last winter going through the promotional material, behind-the-scenes breakdowns, and the few leaked technical documents that circulated on production forums. The movie was produced by DreamWorks Animation and released through Universal Pictures. It grossed about $470 million against a reported budget of roughly $125 million, which is a solid return but nowhere near the level of their biggest franchises. What's notable is that the film's technical team published several GDC talks about how they solved the hair rendering problem across hundreds of troll characters simultaneously. That work is still being referenced in pipeline discussions at mid-tier studios in 2024. The troll designs are deceptively simple. Each character has brightly colored, voluminous hair that takes up significantly more screen space than a typical human-haired CGI character. This isn't an aesthetic flourish—it's the core visual identity of the franchise and it creates enormous rendering overhead. I remember looking at a production still from the early renders where the hair simulation on Poppy's character alone was taking over four hours per frame on their render farm. That's not acceptable for a feature film on a tight schedule.
The solution involved a hybrid approach combining traditional subsurface scattering for the skin with a custom shader built specifically for the hair geometry. They developed what they called "HairWorks-lite," a simplified physics simulation that could run in real-time during layout and animation phases before being replaced by the final high-fidelity pass. The character design team also standardized hair volumes into reusable clusters, which meant they weren't simulating individual strands for every frame. Instead, they used proxy geometry that was swapped for detailed geometry only in close-up shots. This cut render times by approximately sixty percent across the board. Branch's character is deliberately designed with flat, stiff hair to contrast with Poppy's wild curls. That contrast isn't just personality—it's a rendering decision. His hair required a completely different simulation setup because it needed to hold shape rather than flow. If you're studying character rigging for CG animation, comparing the two hair systems in this film gives you a clear lesson in how personality drives technical choices.
The Magic System And World Building
Purla isn't just a colorful backdrop. The island chain has a defined ecology and social structure that the production designers mapped out in considerable detail. According to the art book released alongside the film, the world was built around the concept of "joy as a biological necessity." The Bergens, who live on a dark, foggy island, are portrayed as a species that must consume trolls to feel emotion. This creates the central conflict and gives the movie a folkloric structure that mirrors old Scandinavian fairy tales about trolle and huldra figures. The Isle of Purla itself is rendered using a combination of hand-painted texture work and procedural terrain generation. I've seen wireframe comparisons between early blocking passes and the final composited shots and the difference is striking. The production used a tool called ZBrush for sculpting the island geometry and then ran it through Mari for texture painting at eightK resolution. The color palette is aggressively saturated, which creates a specific challenge in compositing—colors that look fine in isolation clip severely when layered together. The compositing team had to build custom LUTs to keep the highlights from blowing out during the final grade.
Get the Full Details
Technical Pipeline Details That Matter
If you're looking to understand how this movie was actually made, the most valuable resource is the GDC talk given by the animation supervisor. They broke down their use of DreamWorks' internal tool, Kajiya-Kay renderer, and explained how they modified it for this production. The renderer uses path tracing with adaptive sampling, which means it allocates more computational effort to areas of the image that are harder to resolve—like the complex caustics in the underwater sequences. One thing most articles skip over is the audio pipeline. The music in this film isn't just background—it's diegetic. Characters sing to communicate emotions, which means every musical number required additional rigging for lip sync and expression control. The audio team worked closely with the animation department to pre-record all the vocals before animation began, which is standard practice but the scale here was unusual. Nearly seventy percent of the film's runtime contains sung dialogue, which is far higher than the typical animated musical. This required the animators to build expression blend shapes that could handle both speech and singing simultaneously without the faces looking distorted. I encountered a specific problem when trying to analyze frame-by-frame how the hair simulations transitioned between the real-time proxy and the final render. The publicly available reference footage doesn't show this transition clearly. The workaround was to find the raw animation dailies that were uploaded to the studio's internal review server before they were cleaned up for release. These files were hosted on a production management system called ShotGrid, and while most of the older reels have been archived, a handful of Poppy's early test animations are still accessible through certain industry archive projects. They show the exact moment where the proxy hair is swapped for the final version.
Common Misconceptions
People often describe this film as "simple" or "for young children only," and while the target demographic is clearly younger viewers, that doesn't mean there isn't technical substance underneath. The film's visual effects team dealt with problems that even experienced TDs at larger studios struggle with—simulating hundreds of unique hair volumes across dozens of characters in shared environments without texture popping or simulation aliasing. Those are real engineering challenges. Another misconception is that the film's bright color scheme was achieved primarily through post-production grading. In reality, the color work happened at the lighting stage. Each light rig was personally adjusted by the lighting artists for every shot, and the grade was applied relatively conservatively. This is why the colors feel consistent across different environments—the saturation wasn't slapped on in post, it was baked into the lighting calculations. If you're working in compositing and trying to match plate footage to CG elements, this is a good reminder that lighting choices made during rendering will affect how easily you can integrate elements later.
What You Should Actually Watch For
Don't just watch the movie. Watch the deleted scenes and the early story reels that DreamWorks released on their YouTube channel. The story reels show the film as it was originally conceived, and the differences are significant. Poppy's character was initially written as more sarcastic and less relentlessly upbeat. Branch's backstory was darker and the ending was more ambiguous. These changes weren't artistic preferences—they were driven by test screening data. Kids under seven didn't respond to the earlier version, and parents reported that the darker tone was too intense for the target age group. This is a standard part of animated production but seeing it documented so clearly in the released materials is useful for understanding how studio feedback loops actually work. The film also features a supporting character named Guy Diamond, who is covered in glitter. From a rendering perspective, this character was a nightmare. Glitter requires a different shading model entirely—standard subsurface scattering doesn't capture the way light interacts with tiny reflective particles. The VFX team built a custom microfacet distribution function to handle the sparkle effect, and they had to run a separate render pass just for the glitter layer before compositing it over the base character. If you're interested in shader development, this is a concrete example of when standard libraries fail and you need to write custom code. The movie received mixed reviews from critics but performed well commercially and spawned a franchise that includes sequels, television specials, and merchandise. Whether that's a good outcome is debatable. What's not debatable is that the technical work behind it solved real problems in CG animation production, and the solutions are still relevant to anyone working in the field today. The hair simulation pipeline alone has been adapted by at least two other studios for their own productions. That's the actual legacy here, not the box office numbers or the sequel deals.
Where To Find Materials
DreamWorks has released a substantial amount of production documentation on their official channels. The GDC archives contain the full presentations from their technical team. The art book "The Art of Trolls" is available through most major retailers and includes production sketches, concept art, and interviews with the design team. For the more technically inclined, the ShotGrid references and internal review links mentioned earlier can sometimes be found through industry networking groups and animation forums. There's no single official repository, which is frustrating but not unusual for production pipeline documentation. Be aware that some of the technical documents circulating online are outdated or from pre-production phases. The final pipeline differed in several key areas from what was documented in early GDC talks. If you're using this material for research or professional reference, cross-check everything against the final released film and the later technical presentations that addressed post-production issues. The differences between the planned pipeline and the actual implemented pipeline are where the useful information lives.
