> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/prepare-your-scene/houdini-and-solaris.md).

# 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](/docs/prepare-your-scene/caching-simulations.md) and configure your [AOVs](/docs/prepare-your-scene/aovs.md) before exporting.

1. In the Octane ROP, enable **Export ORBX and Alembic Files**.
2. Set **Export Mode** to **Full ORBX Scene**.
3. Set **Base File Name** to the destination folder and file name. Octane adds the `.orbx` extension.
4. Enable **Export without Render Scene** to export without rendering the frames locally.
5. 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**.
6. Click **Render to Disk** to run the export.

See OTOY's [Houdini export guide](https://help.otoy.com/hc/en-us/articles/28391052123419-Setting-up-for-the-Render-Network-in-Houdini) for the control locations and its [Octane ROP guide](https://docs.otoy.com/houdini/OctaneROP.html) for frame-range settings.

## Export from Solaris

1. Add an **Octane Render Settings** node and connect it to a **USD Render ROP**.
2. On the Octane Render Settings node, enable **Export ORBX and Alembic Files**, choose **Full ORBX Scene**, and set **Base File Name** without the `.orbx` extension.
3. On the USD Render ROP, set **Render Settings** to the scene-graph path of the render settings created by the Octane node.
4. 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**.
5. Click **Render to Disk**. SideFX's [USD Render guide](https://www.sidefx.com/docs/houdini/nodes/out/usdrender.html) 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](https://help.otoy.com/hc/en-us/articles/28430101507227-Setting-up-for-the-Render-Network-in-Solaris).

## Check the exported scene

Follow the [ORBX check in Octane Standalone](/docs/prepare-your-scene/octane-standalone-and-orbx.md#check-an-exported-orbx). 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](/docs/web-app/upload-scenes.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://know.rendernetwork.com/docs/prepare-your-scene/houdini-and-solaris.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.