> 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/build-in-the-node-editor.md).

# Build in the node editor

This guide takes you from a blank canvas to a fully textured asset. Pick the route that matches what you have.

The first time you sign in, onboarding opens a quickstart for the work you chose: see [Quickstarts](https://docs.m-xr.com/marso-studio/quickstarts/how-quickstarts-work.md). After that you land on **Home**.

**Want a finished asset without building a graph?** Pick one from **Quickstart** in the sidebar, give it a prompt, an image or a 3D model, and it runs every stage for you. See [Quickstarts](https://docs.m-xr.com/marso-studio/quickstarts/how-quickstarts-work.md).

To build it yourself, click **Create Project** on **Home** and choose how to start. That choice decides your route:

| Option           | For           | You start with                                                                     |
| ---------------- | ------------- | ---------------------------------------------------------------------------------- |
| **Scene**        | A whole scene | The full scene chain, from **Generate Image** to **Generate PBR Textures (Group)** |
| **Single asset** | One asset     | **Load 3D Model** → **Generate PBR Textures**                                      |
| **Blank**        | Anything else | An empty canvas                                                                    |

> **Bringing your own mesh?** Check that your asset meets the [file requirements](https://docs.m-xr.com/marso-studio/preparing-your-assets/3d-file-support.md) first. Most early problems come from inputs that were never going to work.

## Route A: I want a whole scene

Create a new project and choose **Scene**. This is the main route, and every node it needs is already on the canvas. Scenes need a paid plan or the trial: see [Plans](https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md#plans).

1. In **Generate Image**, on its **Scene** tab, describe an environment, a place rather than a single object: *"a cluttered mechanic's workshop, tools on the bench, oil drums in the corner"*.
2. Pick at least one category to look for, then run **Detect Objects**. The scene is broken into its individual objects.
3. Open the object viewer. **Everything is selected by default.** Deselect walls, floors, backdrop, duplicates, and anything small or distant. Every object you keep is charged for all three generation stages, so this is the step that controls your spend. Your plan also sets how many you can keep ([Plans](https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md#plans)). Confirm the selection.
4. Run **Generate Reference Images (Group)**.
5. Run **Generate 3D Models (Group)**.
6. Run **Generate PBR Textures (Group)**.
7. **Preview** objects in the 3D viewer as they arrive, then **export** the scene or individual assets.

Full detail in [Generate a scene](https://docs.m-xr.com/marso-studio/reference/scene-generation.md).

## Route B: I already have a 3D model

Create a new project and choose **Single asset**. You land on **Load 3D Model → Generate PBR Textures**.

1. In **Load 3D Model**, upload your `.glb`, `.usdz` or `.fbx`. Uploading is free.
2. Run **Generate PBR Textures**. The model predicts your materials, usually in a few minutes.
3. Inspect the result in the **3D viewer**.
4. **Export** the textured asset and its individual maps.

## Route C: I want one asset from an idea or an image

Create a new project and choose **Blank**, then build the image → 3D route: **Generate Image → Generate 3D Model → Generate PBR Textures**.

1. In **Generate Image**, enter a prompt. Prefer your own image? Use a **Load Image** node instead. It's free.
2. **Generate 3D Model** turns that image into a mesh. Need a specific face count? Set a custom polycount.
3. **Generate PBR Textures** applies materials.
4. **Preview** in the 3D viewer, then **export**.

> Make sure your object fills most of the image. Sparse or distant subjects are the most common cause of a failed 3D generation.

## What you get

Every successful run gives you the textured asset plus its individual maps: **albedo, metallic, roughness, IOR and normal**. Scene runs give you each object as its own asset with its own material set. Downloading them needs a paid plan or the trial.

## Next steps

* Run a scene properly → [Generate a scene](https://docs.m-xr.com/marso-studio/reference/scene-generation.md)
* Understand the full pipeline → [Nodes reference](https://docs.m-xr.com/marso-studio/reference/nodes-reference.md)
* Budget a big run → [Credits & billing](https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md)
* Get better results → [Sourcing & preparing assets](https://docs.m-xr.com/marso-studio/preparing-your-assets/sourcing-and-preparing-assets.md)
* Something not working? → [Troubleshooting](https://docs.m-xr.com/marso-studio/help-and-support/troubleshooting.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 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/getting-started/build-in-the-node-editor.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.
