Why We Recommend Blender: A Pipeline Decision, Not a Fanboy Take

 Production case study — Mad Saturn Interactive

When we started what's now Mad Saturn (back then under the name Mantra Animation), the software question wasn't philosophical — it was financial. Maya and 3ds Max cost more per license, per year, than most indie studios bring in over several months. But cost alone doesn't make a good recommendation — plenty of free software is free because it's incomplete. After five years producing Nodisea 2000 in Blender, here's what actually convinced us, with real examples from that production.

The unified pipeline isn't marketing — it's saved time

Modeling, sculpting, UVs, shading, rigging, animation, simulation, and compositing all live in one application. For a two- or three-person studio, that means not having to export a rig from one program to another and hope the deformation doesn't break along the way. On Nodisea 2000, a character's entire workflow — from initial blocking to final render — never leaves Blender. That cuts down on points of failure, and with a small team, every point of failure is time you don't have.

A concrete example: MakeHuman and the problem no tutorial covers

For character generation on Nodisea 2000 we use MPFB2 (MakeHuman Plugin for Blender), which lets you build an editable human base directly inside the program instead of modeling every secondary character from scratch. On Windows, the plugin failed silently during installation — not because of a bug in the addon, but because the system was missing certain base assets that MakeHuman expects to find locally. The fix wasn't documented on the addon's page: we had to go straight to the MakeHuman community site and manually download those assets before the plugin would work normally.

This kind of friction is real, and it's worth naming, because it's exactly what a generic "10 reasons to use Blender" article won't tell you. The upside of an open ecosystem is that even when a problem isn't in the official documentation, it's usually already solved somewhere in a forum or repository — often the same day you go looking for it.

Geometry Nodes changed what a small team can pull off alone

Procedural workflows that used to require a dedicated TD or a paid plugin now ship built in. For a studio without that role on payroll, the difference is significant: generating set variations or populating a scene procedurally in minutes, instead of placing every asset by hand.

Eevee and Cycles cover different needs without extra licenses

Nodisea 2000 uses Eevee for fast iteration during scene blocking, and Cycles for final renders where photorealistic quality matters more than render time. Having both engines included, with no separate purchase and no switching software, simplifies decisions that in other pipelines mean extra budget.

Where Blender still falls short

Being honest about the limitations is part of why we trust this tool instead of just promoting it. Pipeline compatibility with larger studios working in Maya or Houdini is still more friction than it should be (interchange formats, complex rigs). For heavy VFX work involving match-move or studio-scale simulations, dedicated tools still have the edge. And some community addons, while they solve real problems like the MPFB2 case above, don't always come with the level of support or documentation a commercial tool would.

The takeaway after five years

Blender wasn't the "free because we had to be" option we ended up tolerating. After a multi-year project involving character rigging, animation, and renders across two different engines, it's still the choice we'd make again — not because it has no friction, but because the friction it does have is solvable, documented by an active community, and doesn't come with a license invoice attached.

---

This article is part of our pipeline analysis series, where we document real technical decisions made during the production of Nodisea 2000 and other Mad Saturn projects.

☕ Enjoyed what you saw? We're a small independent team building this universe project by project — if you'd like to help fuel the next one, buy us a coffee!

☕ Buy Us a Coffee