> 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/advanced-pipelines/lmi-tools.md).

# LMI Tools for Houdini

Use LMI's Houdini tools to prepare assets, scatters, and cameras for an Octane assembly workflow.

The [LMI Octane Pipeline](https://lmi.london/tools/lmi-octane-pipeline), developed by Andrey Lebrov's studio, provides tools for building an [assembly pipeline in Octane Standalone](/docs/advanced-pipelines/assembly-pipelines.md).

| Tool               | Use it for                                                                            |
| ------------------ | ------------------------------------------------------------------------------------- |
| LMI Pointbaker     | Export scatter placement and animation, with separate connections for asset variants. |
| LMI Octane Library | Build shaded OCS asset libraries from geometry and textures.                          |
| LMI Octane Motion  | Transfer object motion separately from the geometry.                                  |
| LMI Camera         | Transfer a camera to Octane Standalone.                                               |

{% hint style="info" %}
Tutorials using **Octane Shot Manager** and **OctaneTag** describe the legacy toolset. Those tools are no longer included in the main LMI Octane Pipeline release.
{% endhint %}

## Install and check the requirements

Get the package matching your Houdini build and operating system. Use the [LMI installation instructions](https://lmi.london/docs) to install it through Houdini Packages Manager or manually, and set the path to Octane Standalone.

The requirements vary by tool. Check LMI's dependency list and [Render Network's supported software](/docs/get-started/supported-software.md) before choosing versions for a production.

## Export a scatter with Pointbaker

1. Connect your scatter points to **LMI Pointbaker**. Check the rotation, scale, and variant assignments in Houdini.
2. Export the points, then drag the generated `.lua` file into Octane Standalone.
3. Connect the corresponding geometry to the scatter's variant inputs and check the animation.

Keep the companion export files with the Lua file. Re-exporting the points and refreshing in Standalone updates the scatter without reconnecting its geometry.

{% hint style="warning" %}
For export on one machine and assembly on another, follow LMI's **Known Limitations** guidance: enable **Packed Export** in **Advanced** to produce an ORBX. Packed exports do not retain the live reference to your Houdini exports.
{% endhint %}

The [Pointbaker manual](https://lmi.london/docs) covers its attributes, example scenes, and export options.

## Render the assembled shot

Finish the shot in Octane Standalone, then follow [Submit the assembled scene](/docs/advanced-pipelines/assembly-pipelines.md#submit-the-assembled-scene). The LMI export prepares the scene content; you choose the render job's settings and delivery through the Manager or web app.

Start with a small test using the actual assets, animation, and output settings before submitting a full sequence. Use [LMI's documentation and support](https://lmi.london/docs) for tool installation or export problems, and [Render Network support](/docs/help/get-support.md) for upload or rendering problems.


---

# 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/advanced-pipelines/lmi-tools.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.