> For the complete documentation index, see [llms.txt](https://docs.v-nova.com/technologies/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v-nova.com/technologies/v-nova.presenz/v-nova-presenz-documentation/motion-vectors-and-animation.md).

# Motion vectors and animation

**Motion vectors and animation**

![](https://2927645607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1djoRwqtVhAs0LOpvzC9%2Fuploads%2FHafmiMEDLCwfXSMStrCQ%2F17.png?alt=media)

**Motion vectors** are used by V-Nova PresenZ to smooth the motion of animated objects in the volumetric image at display time. They hold local information about the motion of each point for each frame. The motion vectors can be computed by most rendering engines and can be incorporated into a compositing software. 

V-Nova PresenZ requires a specific type of motion vector that describes the trajectory of objects from the current frame to the next frame. Basically for each point: motion vector(frame) = position  (frame+1) - position (frame)

![](https://2927645607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1djoRwqtVhAs0LOpvzC9%2Fuploads%2FJZYYe3n4DJ4OxiN5DSr8%2F18.png?alt=media)

{% hint style="info" %}
***Note:** Our authoring plugins can detect when the rendering is in an animation context and will prompt the user to apply the motion vector settings automatically.*
{% endhint %}

{% hint style="warning" %}
**Warning:** Attention, don't confuse the motion vector concept with the "velocity" in simulation dynamics.\
The motion vector we are looking for is the vector pointing to the position at the next frame\
, while the velocity is the current speed of the object at the beginning of the frame simulated before any external force is applied (gravity, wind, etc). 
{% endhint %}


---

# 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://docs.v-nova.com/technologies/v-nova.presenz/v-nova-presenz-documentation/motion-vectors-and-animation.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.