> For the complete documentation index, see [llms.txt](https://motogege-atelier.gitbook.io/motogege-atelier-maps-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://motogege-atelier.gitbook.io/motogege-atelier-maps-wiki/motogege-atelier-wiki/capozzo-cardealer-mlo/identify-conflict-maps.md).

# Identify conflict maps

## Capozzo occlusions.

As we start capozzo we find that from inside, and outside near the cardealer, everything starts flickering, or disappears. 

This problem is caused by having 2 ymaps with occlusion positioning in the same \[maps] folder. This means that everytime the server find that file, it overrides the other one he found before into another folder. So it ends in having the incorrect ymap loaded for Capozzo.

What we do is identify the ymaps, this way we know what resource is having the same file.

<figure><img src="/files/ENlYm7W45YsCwVsXiqjQ" alt=""><figcaption><p>Capozzo Folder scheme</p></figcaption></figure>

into the mappe folder you'll find all the ymaps. We search for occ\_ymaps

<figure><img src="/files/S3Tq5z6F6pBwFvEpU4Mk" alt=""><figcaption><p>Capozzo occlusion ymap</p></figcaption></figure>

Once i identify that, i copy the name and start a search into the \[maps] folder to locate the other ymaps with the same name.

<figure><img src="/files/Ml77CubpwaLyQbu6xaRx" alt=""><figcaption><p>The path for the other resource sharing the same file</p></figcaption></figure>

In this case, there is just one ch1\_occl\_01.ymap. This is the result you wanna obtain.

So you follow the path of all the other resources that shares this file, and erase the ymap from there.

Insidde the Atelier ticket just write the resource conflicting and wait for the new, packed file to be released into the ticket for you.

Overwrite the new ch1\_occl\_01.ymap into your Capozzo folder and restart the server.


---

# 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:

```
GET https://motogege-atelier.gitbook.io/motogege-atelier-maps-wiki/motogege-atelier-wiki/capozzo-cardealer-mlo/identify-conflict-maps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.