> 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/v3.2/general-troubleshooting/running-motive-on-high-dpi-displays.md).

# Running Motive on High DPI Displays

## Running Motive on High-resolution Displays

When running Motive on displays with high pixel density, (e.g. 4K resolution displays) the software UI may not be scaled properly and some of the buttons may appear to be very small on the screen. In these cases, you can simply adjust the windows configuration to prevent the scaling on high-resolution displays. Follow the below steps for configuring this.

### Steps

1. Right click on the Motive Icon > Select Properties
2. Navigate to the Compatibility tab
3. Under *Settings* section, click *Change high DPI settings*. This will bring up the properties window.
4. On the new pop-up window, click and check the box next to **Override high DPI scaling behavior. Scaling performed by:** setting.
5. Lastly, make sure “System” option is selected in the drop-down menu as shown in the image below.
6. Click *OK* to apply. This will override any incorrect scaling behavior when using Motive on high DPI displays.

![](https://content.gitbook.com/content/4ne9bLcvxMzpZqIc5yuj/blobs/tmmHPerNYt5zI3KruUHo/image.png)


---

# 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/v3.2/general-troubleshooting/running-motive-on-high-dpi-displays.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.