> For the complete documentation index, see [llms.txt](https://docs.optitrack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optitrack.com/v2.3/motive-ui-panes/reference-view-pane.md).
# Reference View pane
The Reference View pane is used to monitor captured videos from the reference cameras. Up to two reference cameras can be monitored on each pane. This pane can be accessed under the *View tab* → *Reference Overlay* or simply by clicking on one of the reference view icons from the main toolbar ([](https://v23.wiki.optitrack.com/index.php?title=File:ToolBar_ReferenceView_20.png)).
Cameras can be set to a reference view from the [Devices pane](/v2.3/motive-ui-panes/devices-pane.md) or by configuring video type to grayscale modes.
## Assets Overlay
In this pane, cameras, markers, and trackable assets can be overlayed over the reference view. This is a good way of monitoring events during the capture. All of the assets and trajectory histories under the Perspective view pane can be overlayed on the reference videos from this pane.
**Note:** that the overlayed assets will not be rendered into exported reference videos.
---
# 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.optitrack.com/v2.3/motive-ui-panes/reference-view-pane.md?ask=&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.
