> For the complete documentation index, see [llms.txt](https://sylvl.gitbook.io/panoramake-release/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sylvl.gitbook.io/panoramake-release/setting-up-instance/biomes-workflow.md).

# Biomes Workflow

For the Double and Multi preset, you have access to multiple biomes. A biome is the combinaison of the automatic layer, **which defines where the biome is,** and the manually paintable sub-layers.

Just like in the initial setup, you have to assign a **Weight-Blended** LayerInfo for the BIOME and **Correction Layers**, and a **Non Weight-Blended** LayerInfo for the individual Sub-Layers that you want to paint.

The correction layers are layers are are set on top of all the biomes.

{% hint style="danger" %}
Be aware that using multiple biomes is heavy, in terms of shader compilations, complexity, edition time in the Builder, etc. 

It's recommended to stick to the "Single" preset unless you really need to use multiple Biomes !
{% endhint %}

![All 6 Biomes and a Correction layer going on top of them all.](/files/FYFTYuf7W9MqYqSGWeHh)

Each of these Biomes work as expected, with their own filters, Grass support, etc.

![Grass & Filters on the Sub-Layer 2.](/files/edceXr3mQ6vBfsg4N95C)


---

# 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://sylvl.gitbook.io/panoramake-release/setting-up-instance/biomes-workflow.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.