> 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-studio/help-and-support/contact-support.md).

# Contact Support

Before reaching out, check [Troubleshooting](https://docs.m-xr.com/marso-studio/help-and-support/troubleshooting.md) — it covers the most common file and generation issues.

### Discord *(fastest)*

Accept your Discord invite and post in the **#marso-studio** channel. To get help quickly, include:

* A **screenshot** of the result or error
* The **asset** you used, and where it came from
* What you **expected** vs what happened

### Email

You can also reach us at [**support@m-xr.com**](mailto:support@m-xr.com).

### Reporting an issue

Marso Studio is in active development and your reports directly shape it. The more detail, the faster it gets fixed: the asset or scene prompt you used, what you expected against what actually happened, and a screenshot of the result with any error message.


---

# 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-studio/help-and-support/contact-support.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.
