Houdini to Any 3D Software: Exporting a Rigged Character as FBX

This short workflow exports a bound character from Houdini and reimports it to check that a joint can still deform the mesh. The round trip matters: the existence of an FBX file on disk is a weaker test than loading that file and checking its skinning behavior.

The starting scene already contains character geometry and a skeleton with capture weights. The recording has no animation clip to export. It discusses transfer to other applications, but the demonstrated validation takes place inside Houdini.

Supply the character’s three inputs

The instructor adds ROP FBX Character Output and connects rest geometry, capture pose and the animation input. In this example, there is no animated motion; he connects the pose stream for convenience rather than claiming to export a finished performance.

Keep those roles distinct. Rest geometry is the bound surface; the capture pose describes its reference skeleton; the animated pose would supply changing transforms when animation is present. SideFX’s ROP FBX Character Output reference confirms that the node exports a skinned character using a geometry-based skeleton. Its current reference supports the node terminology, not a certification of the recorded file.

Choose the output destination and use Save to Disk, as in the recording. Keep that exact path available for the next step. A remembered filename in another directory would test a different export.

Reimport the file that was just written

Create FBX Character Import and enter the exported FBX path. The instructor first displays the empty import, then adds the path and sees the character appear. This separates a successful file load from whatever was already visible in the original rig.

Add Joint Deform, matching the geometry, capture-pose and animated-pose streams to their corresponding inputs. Display the deform output. Merely loading a character is not yet the skinning test: the next operation must change its pose and show that the surface follows.

The instructor adds Rig Pose, selects a joint and rotates it. The mesh responds. That demonstrates a working pose/deformation relationship in this Houdini round trip. It does not demonstrate every joint, a complete animation range or successful import in another application.

Inspect the destination’s axis and unit expectations

The final part points to export compatibility settings for axis orientation and unit conversion. The instructor contrasts an up-axis choice used for Blender with the Houdini setup and discusses centimetres and metres as output units.

The practical question is what the receiving scene expects. Axis conversion and unit conversion address different mismatches: which direction is up, and how a distance is represented. The source does not establish a universal export preset for Maya, Blender or another receiver, and this article does not supply one.

Before treating a cross-application handoff as verified, the receiving application would need its own scale, orientation and deformation check. That additional test is editorial guidance beyond the Houdini-only demonstration, not work already completed in the video or for this article.

What this check establishes

The completed demonstration confirms that this exported character can be reloaded and posed in Houdini. It leaves animation export and external-application behavior untested. If the mesh loads but does not deform, revisit the three stream connections and the posed branch before concluding that the file is valid for delivery.

Caption-based revisit ranges are 01:02–02:00 for output inputs and saving, 02:00–03:00 for reimport and deformation setup, and 03:00 onward for the pose test and compatibility discussion. They are reading references, not added playback controls. The exact Houdini build is not established by the source captions.

For the preceding capture workflow, see Bind a Skeleton to a Character Mesh.

Keep exploring

• Import FBX Characters into Houdini | 4 Methods You Need to Know ↗