> For the complete documentation index, see [llms.txt](https://reblium.gitbook.io/reblium-studio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reblium.gitbook.io/reblium-studio-docs/performance-and-optimization.md).

# Performance and Optimization

## System requirements explained:

***

Reblium requires a powerful CPU, GPU, and sufficient RAM to ensure smooth performance. However, different optimizations for different performance scenarios are available from the settings menu.

[System Requirements](/reblium-studio-docs/system-requirements.md)

***

## Performance settings menu:

The settings menu allows you to adjust quality and performance settings.

***

**Quality**: Adjusts the rendering quality of the engine.

**Resolution**: Determines the output display resolution of the render engine.

**FPS: C**ounter is included to help estimate performance. Note that performance may vary depending on the selected groom or character outfit.

**DirectX**: DX12 is default. For low end GPU cards, option to select DirectX 11 for minimal requirements, visual quality may not be guaranteed using DirectX 11.

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

***


---

# 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://reblium.gitbook.io/reblium-studio-docs/performance-and-optimization.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.