> 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/troubleshooting.md).

# Troubleshooting

Most issues fall into one of the categories below. If none of these solve it, see Contact & support.

### My file was rejected

| Cause                                          | Fix                                                                                                       |
| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| No base-colour texture                         | Add an image-based base-colour texture before uploading                                                   |
| Coloured with vertex data only                 | Vertex colours aren't textures — bake to a texture map                                                    |
| Textures referenced externally (URI/file path) | Embed textures in the file, or bundle them (see below)                                                    |
| FBX zip not following the naming convention    | Name the base-colour map `game.color.png`, `color.png`, `albedo.png`, `basecolor.png` or `base_color.png` |
| A material with no texture                     | Make sure every material has a base-colour texture                                                        |

Full rules: [3D file support](/marso-studio/preparing-your-assets/3d-file-support.md).

### My results don't look right

* **Check the input first.** Marso Studio enhances materials but can't fix bad geometry, overlapping UVs, or a poor scan.
* **Remove any existing PBR.** Bring a clean, base-colour asset — assets that already carry PBR work against the prediction.
* **Flat-shaded AI assets predict poorly.** Generative meshes work best when shading and lighting cues are baked into the base colour.
* **Complex geometry** can produce coverage artefacts on some surfaces — try a cleaner or simpler asset to compare.

See [Sourcing & preparing assets](/marso-studio/preparing-your-assets/sourcing-and-preparing-assets.md).

### It looks wrong in the viewer

The web viewer is still being refined during early access. If a result looks off **in the viewer**, download and check the exported maps before assuming the generation failed.

### Generation failed or timed out

* Keep files **under 100 MB**.
* Run **one generation at a time** during early access.
* Retry once — if it fails again, grab a screenshot of any error and contact us.

***

Still stuck? → [Contact & support](/marso-studio/help-and-support/contact-support.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.m-xr.com/marso-studio/help-and-support/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.