Houdini and Solaris
Export an Octane scene from Houdini or Solaris as an ORBX package.
Export from Houdini
Use the Octane ROP for a scene set up with Octane. Cache simulations and configure your AOVs before exporting.
In the Octane ROP, enable Export ORBX and Alembic Files.
Set Export Mode to Full ORBX Scene.
Set Base File Name to the destination folder and file name. Octane adds the
.orbxextension.Enable Export without Render Scene to export without rendering the frames locally.
For animation, set Valid Frame Range to Render Frame Range and set Start/End/Inc to the frames and interval you need. For a still, use Render Current Frame.
Click Render to Disk to run the export.
See OTOY's Houdini export guide for the control locations and its Octane ROP guide for frame-range settings.
Export from Solaris
Add an Octane Render Settings node and connect it to a USD Render ROP.
On the Octane Render Settings node, enable Export ORBX and Alembic Files, choose Full ORBX Scene, and set Base File Name without the
.orbxextension.On the USD Render ROP, set Render Settings to the scene-graph path of the render settings created by the Octane node.
For animation, set Valid Frame Range to Render Frame Range, then set Start/End/Inc to the frames and interval you need. Enable Render All Frames With a Single Process.
Click Render to Disk. SideFX's USD Render guide explains these frame-range and render-settings controls.
For AOVs saved to the final output, use Octane_raster as the Product Type under AOV Settings. Raster is for viewing AOVs in the Octane viewport. See OTOY's Solaris export guide.
Check the exported scene
Follow the ORBX check in Octane Standalone. For Pyro or other VDB simulations, check that the expected volume grids are present and render correctly.
If exporting a large Houdini scene stalls or crashes, use the Octane ROP's Objects filters to export smaller parts. Turning off a geometry node's Display flag also excludes it from the export.
When the exported scene renders correctly, follow Upload Scenes.
Last updated