Houdini 22 plugs AI agents into character rigging

SideFX released Houdini 22 in July with a preview of MCP-powered AI agents built into the KineFX character rigging toolset. The agents generate and explain Apex Script code for rig construction while the artist reviews and controls every output. It's not a black box, it's code you can read, edit, and iterate on.

For character animation teams, rig scaffolding has always been the friction point. Procedural workflows reduce manual setup time, but writing and maintaining Apex Script demands specialists. MCP agents lower that barrier. A rigger describes a rig behavior in natural language, the agent drafts the code, then they refine it in context. The artist stays in the driver's seat.

Three things shipped in Houdini 22

KineFX updates are procedural-first, which means faster iteration and easier handoffs between riggers and animators sharing the same rig graph. Copernicus, the image-processing framework, gained new tools for character animation and USD world building. And SideFX bundled a full Gaussian splatting toolkit, so you can train splats from reference photos or generate them from 3D scenes without jumping to a separate application.

The MCP agents are marked preview, not production-ready yet. SideFX is being careful about how it ships AI into the pipeline, which reads as respect for artists who need to trust the code they're running.

Why procedural rigging matters

Larger studios have been sideloading procedural logic into Houdini for years, building custom tools to automate rig setup. SideFX is making that pattern built-in, with AI assistance handling the boilerplate. For shops doing character animation at scale, that cuts iteration cycles. You're not waiting for a specialist to rewrite rig logic; you teach the agent the pattern once and apply it across variants.

Vision For Xperiences has built character work for product and cinematic clients, and the bottleneck is usually not the rig itself but the setup labor and communication overhead between modeling, rigging, and animation. Procedural workflows with agent-assisted code generation compress that gap. If this holds up outside the demo, it changes how we would quote and scope character-heavy projects.

The splatting integration

The bundled Gaussian splatting toolkit keeps the entire pipeline inside Houdini. Train splats, animate them with standard deformation nodes, relight them to match the environment, render them with Karma. For work involving photogrammetry or reference-based 3D capture, that's one fewer tool handoff.

We are watching this closely because our environment and set extension work is exactly where training time and render cost matter most. Native Houdini integration removes the friction of jumping to a separate splat application, running training, exporting, and re-importing. The question is whether splatting stays useful as a full production layer or settles into its actual niche, supplementary to raster geometry for specific shots.

What still needs proving

AI in creative tools carries a trust tax. Riggers need to understand what the agent produced before shipping it. SideFX positioned MCP as preview, not finished, which is the right move. Early adopters will spot edge cases and limitations. By the time it's stable, there will be a clear set of workflows where it saves time without introducing hidden failure modes.

The procedural KineFX updates and the splatting toolkit are solid on their own. The MCP agents are a bonus layer to experiment with if your pipeline has room for it. We want to get close to a production version before treating it as a blocker for an upgrade decision.

For teams with heavy animation workloads, this release is worth tracking either way. Procedural-first rigging and in-house splatting are real gains, even if the AI agents stay experimental for another cycle.

Quick answers

Do I need to retrain my team to use MCP rigging agents?

Not heavily. Riggers still write rig logic in Apex Script; the agent just scaffolds the code faster. The artist reviews and edits every line. If your team already uses procedural rigging in Houdini, MCP accelerates what you're already doing.

Can I export splats from Houdini 22 to other renderers?

SideFX's toolset is optimized for Karma, Houdini's native renderer. For external renderers, you'd export splat geometry or point clouds and rely on third-party splat plugins. The native integration is a strength if you render in-house.

Is Houdini 22 backward compatible with older rigs?

Yes. KineFX enhancements are additive. Existing character rigs continue to work. The procedural and AI features are new patterns you adopt when starting fresh builds or refactoring legacy setups.

Referenced

Image: “Digital Character Animation Campus at VFS” by vancouverfilmschool, via source. Licensed CC BY 2.0.