> 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/getting-started/early-access-brief.md).

# Early Access Brief

Marso Studio is in **early access**. The core pipeline works today — you can take an asset from upload to exported PBR maps — but you'll meet rough edges, and your feedback is what sharpens the product.

### What to expect

* **Generation in minutes** — most PBR runs complete in a few minutes.
* **Viewable results** — preview the textured asset in the 3D viewer before you download.
* **Downloadable maps** — every successful run gives you albedo, metallic, roughness and IOR.
* **A renderer still being refined** — the web viewer is improving. If something looks off *in the viewer*, check the exported maps before assuming the result is wrong.

### Getting the best results

* Start with clean inputs — see Sourcing & preparing assets.
* Check your UVs, and that the base colour reads correctly.
* Try several assets — some material types predict more reliably than others.
* Keep files under 100 MB.
* Run one generation at a time during early access.

### When something goes wrong

Tell us — with detail, it gets fixed faster. Include:

* The asset you used (and where it came from)
* What you expected vs what actually happened
* A screenshot of the result, plus any error message

Check Troubleshooting first for the common cases, then Contact & support to reach the team.

### Feedback earns credits

Early-access feedback is rewarded: submitting feedback through the in-app form earns you credits to keep generating. See [Credits & billing](/marso-studio/reference/credits-and-billing.md).

***

#### Example Assets

We provide 10 example assets, already loaded into any new projects. You can get started with these to understand how Marso Studio works.

The assets provided are all Gen3D models.

<div align="left"><figure><img src="/files/I8IlWz0X7yN8aieMMjjs" alt="" width="188"><figcaption></figcaption></figure></div>

{% hint style="success" %}
The quality of your output is directly tied to the quality of your input. Marso Studio enhances materials — it doesn't repair bad geometry or compensate for poor scans.
{% endhint %}

More information on supported file types can be found [here](broken://pages/tF7LBtaeYrA0R07t7Wmz).

#### What makes a good input?

A well-captured photogrammetry scan is ideal — clean geometry, well-defined surfaces, no mesh "boiling" or sloppy reconstruction artefacts. If you have your own scans, start there.

{% tabs %}
{% tab title="Good Mesh" %}

<figure><img src="/files/d4tmGS0be7BbgqzFd7gY" alt="" width="375"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Bad Mesh" %}

<figure><img src="/files/sFk9vvs411M2tZIWScl1" alt="" width="375"><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

If you don't have a mesh at hand, you can browse Sketchfab for downloadable .glb assets. We've also put together a curated collection of objects that work well with Marso Studio — feel free to pick from those below, or find your own.

<details>

<summary>Our Sketchfab Collections</summary>

* [Auto PBR Results](https://sketchfab.com/m-xr/collections/auto-pbr-imagetomaterial-4137cee2eca94d4b9eb3376dbac359a0)
* [Test Data](https://sketchfab.com/m-xr/collections/img2mat-test-data-ed113062403d410f85138cffdac018fc)

</details>

#### Evaluating a Mesh

When evaluating a mesh on Sketchfab, switch to MatCap view mode — this strips the textures and lets you inspect the geometry directly. You want to see clean, well-defined surfaces without noise, holes, or overlapping faces.

<div><figure><img src="/files/QK1SspgfHkuChZjadbDL" alt=""><figcaption></figcaption></figure> <figure><img src="/files/XcD5F5GkSwt77kov5xbP" alt=""><figcaption></figcaption></figure> <figure><img src="/files/Nvx5MCToVhn8pHm6ObSy" alt=""><figcaption></figcaption></figure></div>


---

# 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/getting-started/early-access-brief.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.