QFX LABMADE UP. MADE REAL. Send a brief

HOME / TRICKS[N° T02] · UPDATED 2026-11-19

Blender to Houdini Solaris through USD, without the axis fights

Model and animate in Blender, light and render in Solaris. These export settings keep the scene upright, the UVs named and the materials out of the way.

BlenderUSDHoudini5 MIN READ

BY · PUBLISHED

Blender is fast for modelling and blocking animation. Houdini Solaris is better for effects, look-dev and Karma rendering. USD is the bridge. Most of the pain is in a handful of export flags.

The export call

BLENDER 5.2, RUN HEADLESS WITH BLENDER -B --PYTHON
bpy.ops.wm.usd_export(
    filepath=USD_PATH,
    selected_objects_only=True,
    export_animation=True,
    export_uvmaps=True,
    rename_uvmaps=True,              # UV map becomes 'st', what Solaris expects
    export_normals=True,
    export_materials=False,          # look-dev happens in Solaris (MaterialX)
    export_subdivision='BEST_MATCH',
    evaluation_mode='RENDER',        # modifiers at render settings, not viewport
    convert_orientation=True,
    export_global_forward_selection='NEGATIVE_Z',
    export_global_up_selection='Y',  # Houdini is Y-up
)
  • Y-up, −Z forward. Blender is Z-up. Converting on export means nothing needs a rotate node in Houdini, and cameras keep working.
  • No materials. Blender materials do not survive the trip well. Exporting none keeps the stage clean, and you assign MaterialX shaders in Solaris by primitive path.
  • Render evaluation. Subdivision and bevel modifiers export the way they render, not the cheaper viewport levels.

Points Houdini has to attach to

Sometimes Houdini needs to know where an animated part is on every frame, for example where a cable plugs into a moving panel. Instead of rebuilding that in Houdini, bake it in Blender to JSON with the same axis conversion:

BAKE PER-FRAME ANCHOR POSITIONS
def blender_to_yup(v):
    """Blender (X, Y, Z) -> USD Y-up, -Z forward: (X, Z, -Y)."""
    return [round(v.x, 6), round(v.z, 6), round(-v.y, 6)]

data = {"frames": {}}
for f in range(scene.frame_start, scene.frame_end + 1):
    scene.frame_set(f)
    data["frames"][str(f)] = [blender_to_yup(e.matrix_world.translation) for e in anchors]
json.dump(data, open(JSON_PATH, "w"))

In Houdini a Python SOP or a wrangle reads the file and pins the Vellum cable ends to those positions frame by frame. The cables in QX-Core are attached this way.

Bake after the last timing changeIf you retime the animation (see this trick), bake the JSON again afterwards, or the cables will follow the old timing.
++++
QFX-BRIEF · ASYNC INTAKEWRITTEN · NO CALLS

Want something like this built for your product?

Send a short brief by email: the product, where the video or game will run, and when you need it. I reply in writing within a day with an approach and a quote for that project.

[email protected] · REPLY WITHIN 1 WORKING DAY