The big problems are that license cost doesn’t outweigh the pain points. In production I can get support from Autodesk for specific bugs without rediverting my production resources to fixing it.
Blender has no C++ API and even the Python api is not stable version to version. Studios live by maximizing their competitive advantage and that takes the form of extending the DCCs with custom pipelines and high performance plugins. With blender I’d have to maintain a full fork.
Also blender’s ghost UI system is significantly worse than Qt. It also means I can’t share the Qt tools I built for the rest of the apps with blender.
And while Ton was still CEO he heavily told studios he didn’t want their business. He believed blender shouldn’t be part of a pipeline but be the whole pipeline. These were his explicit words in a presentation blender gave at SIGGRAPH.
For background, I was a lead engineer in the film industry and still am quite involved with industry development while also contributing to blenders code base. My partner also works for one of the big animation studios.
I think blender is great and it’s seeing adoption professionally but there’s a lot of fundamental things that need solving before it displaces the current status quo DCCs.
Note: Blender might have this too. I haven't tried. But, my impression so far is Blender didn't start this way and trying to add it in after the fact is difficult. Maya stays clean because any UI feature needs to buildable from scripts. By enforcing that rule on themselves, they keep it customizable.
I’m not an animator but I do know that mayas rigging support is second to none; we’re often working on characters with 100+ bones and 200k triangles being driven by said bones. The standards stay standard for a reason when working at that complexity.
That said, Blender is respected. I think it'll get there but still has to battle through momentum.
I've worked in the animation and currently the VFX realm.