> For the complete documentation index, see [llms.txt](https://upland-3d.gitbook.io/upland-3d/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upland-3d.gitbook.io/upland-3d/go-karts/lod2.md).

# LOD2

<figure><img src="/files/PVafneUgaZ5uETGijs8o" alt=""><figcaption></figcaption></figure>

## Specifications

* File type: GLTF
* File size: < 500kb
* Triangles limit 3,000 max

### Hierarchy

Should be a single mesh object. Be sure to keep the names even.

<figure><img src="/files/K6L6upq0gEe37GTBUjnb" alt="" width="288"><figcaption></figcaption></figure>

### Materials

This trim is the only one that holds all mesh characteristics into one single texture image. Note that compared with LOD 0 and 1, this one has together both wheels and car body design.

<figure><img src="/files/hkJA7gBp6h6HHNtlY1h3" alt=""><figcaption></figcaption></figure>

* Images texture should be 256x256 for chasis\_LOD\_2
* Principled Shader
* Metallic == 0.0
* Roughness == 1.0

### Deliverable files for LOD\_2

* GLTF file request

When exporting the GLTF be sure to pick the following values:

<figure><img src="/files/peWpfPGU5wbjEAjk7gYQ" alt="" width="375"><figcaption></figcaption></figure>

* Do not include the texture image inside the GLTF, share it as a separate JPG file


---

# 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://upland-3d.gitbook.io/upland-3d/go-karts/lod2.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.