> For the complete documentation index, see [llms.txt](https://docs.m-xr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.m-xr.com/marso-measure/requirements/processing-requirements.md).

# Processing Requirements

Please contact us if you have any questions regarding processing requirements.

Processing PBR textures with Marso Measure usually requires a desktop workstation, with a GPU available.

<table><thead><tr><th>Minimum Specification</th><th>Recommended Specification</th><th data-hidden></th><th data-hidden></th></tr></thead><tbody><tr><td><ul><li>OS: Windows 10+</li><li>RAM: 16+ GB</li><li>GPU: OpenGL 4.6+ Compatible</li><li>Hard Drive: ~256 GB available</li></ul></td><td><ul><li>OS: Windows 10+</li><li>RAM: 32+ GB</li><li>GPU: Nvidia (CUDA enabled), 8+ GB VRAM</li><li>Hard Drive: ~1TB available</li></ul></td><td></td><td></td></tr></tbody></table>

***

### Scratch Directory

Marso Measure makes use of a “Scratch Directory”, where intermediary files are written during processing, and will be deleted once no longer needed. The size of these files depends on the output texture resolution.

Faster R/W speeds on the scratch directory will greatly improve processing times, so it is recommended to use an internal SSD for the scratch directory. Results can be written to a different drive such as a network share.

{% hint style="info" %}
Recommended: 180000+ IOPS, 3000+ MiB/s
{% 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.m-xr.com/marso-measure/requirements/processing-requirements.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.