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
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:
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.