# Interface Overview

***

<p align="center"><strong>The user interface is divided into three key sections.</strong></p>

***

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

***

### Settings Panel

<div align="left"><figure><img src="/files/l56kfmKnMa7LYAKq0ikr" alt=""><figcaption></figcaption></figure></div>

Located at the top, this section controls the global parameters for the optimization pass.

* **Target Texel Density (px/cm)**: Defines the desired pixel density. For example, 10.24 represents a standard for high-quality First Person assets (1024px per meter).
* **Allow Upscale Textures**: If checked, textures with a density lower than the target will be upscaled.

***

### Optimization Status

<div align="left"><figure><img src="/files/OIGlC8PHeELl1ABLQ1gK" alt=""><figcaption></figcaption></figure></div>

A visual summary of the current folder:

* **Optimized**: Assets that currently meet or are below the target budget.
* **Non-Optimized**: Assets exceeding the target density that require optimization.

***

### Asset Data Grid

<figure><img src="/files/6RebT9o0l8KYqZ0bFT4q" alt=""><figcaption></figcaption></figure>

A comprehensive table detailing every loaded asset. You can sort by any column by clicking the header.

* **Asset Name**: The file name of the static mesh.
* **Texel Density**: The current calculated density (px/cm).
* **Surface Area**: The total world-space surface area of the mesh.
* **Texture Size**: The current resolution of the textures.
* **Textures**: The count of unique textures referenced by the mesh.
* **Total Size**: Estimated memory size of the asset's texture data.

***


---

# Agent Instructions: 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://ark-kra.gitbook.io/tcup/setup/interface-overview.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.