> For the complete documentation index, see [llms.txt](https://flora.magneticarcade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flora.magneticarcade.com/rendering/motion-vectors.md).

# Motion Vectors

Flora supports per-instance motion vectors for effects like TAA and motion blur.

## What This Affects

* Visual quality for moving instances.
* Memory usage (previous transform storage).
* Per-frame update cost for moving instances.

***

### Enabling Motion Vectors

1. In [Runtime Settings](/scripts/runtime-settings.md), ensure `DisablePerObjectMotionVectors` is **off**.
2. In [Scene Settings](/scripts/scene-settings.md), enable `AllowPerObjectMotionVectors`.
3. For terrain-specific paths, enable tree/detail motion vector toggles as needed.

***

### How It Works

If prefab renderers request per-object motion vectors, Flora stores previous transforms and emits motion-vector data for those instances.

> Tip: enable this only where needed to avoid unnecessary memory cost.

***

### Terrain Trees and Details

`SceneSettings` can separately enable motion vectors for terrain trees/details. These still depend on `AllowPerObjectMotionVectors`.

## How To Verify

* Enable motion vectors and confirm moving Flora instances contribute to motion blur/TAA.
* Disable either project or scene gate and confirm contribution stops.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://flora.magneticarcade.com/rendering/motion-vectors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.