> For the complete documentation index, see [llms.txt](https://stylizededge-devs.gitbook.io/aqs-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stylizededge-devs.gitbook.io/aqs-doc/readme.md).

# Introduction

**A complete, data-driven graphics settings system for Unreal Engine 5.**

Auto Quality Switcher (AQS) gives you everything needed to ship a real graphics settings menu — from a single named struct of settings, to a fully working, restylable, drag-and-drop menu — without writing C++ for each new game you ship it in.

## What AQS Actually Does

* **Detects hardware** on first launch (GPU, VRAM, RAM, or a custom benchmark scene) and assigns a device tier
* **Filters presets** by that tier, so weak devices never see options they can't run
* **Applies presets** live, with a fade, or on next launch — your choice per preset
* **Generates a full settings menu automatically** from your preset's data — no hand-built sliders, no per-field wiring
* **Lets you restyle that menu freely** — 9 swappable row templates, grouping, reordering, custom labels and descriptions — all without touching C++
* **Remembers the player's choice** across launches
* **Exposes raw console variables** as menu rows too, for settings that don't fit the named preset fields (Ray Tracing, etc.)

## Who This Is For

If you've ever built a settings menu by hand — wiring a slider to a CVar, copy-pasting that pattern twenty times, then doing it all again for the next project — AQS replaces that entire workflow with: author your preset data once, drop in one widget, done.

Works identically whether you're a programmer who wants full C++ control or a designer who's never opened a graph node. Everything in this doc set is achievable through the Unreal Editor's Details panels and the UMG Designer alone.

## Where to Start

New to AQS? Go to [**Installation**](/aqs-doc/getting-started/installation.md), then [**Quick Start**](/aqs-doc/getting-started/quick-start.md) — you'll have a working menu in about 10 minutes.

Already installed and just need a specific answer? Use the sidebar — everything is organized by what you're trying to do, not by when a feature was added.

Something not working the way you expect? Check [**Troubleshooting**](/aqs-doc/advanced/troubleshooting.md) first — it documents every real gotcha we've hit while building this plugin ourselves, written up so you don't have to rediscover them.

## Need the Full CVar List?

The in-doc [CVar Reference](/aqs-doc/reference/cvar-reference.md) covers the essentials. For the complete categorized reference — 86 CVars split into Engine, Gameplay, and Mobile stability, with a curated menu-safe subset — download the full PDF:

[**📄 Download: Understand Your Console Variables (PDF)**](https://github.com/KimsFerdy/AutoQualitySwitcherDoc/blob/main/docs-assets/AQS_Understand_Your_CVars.pdf)


---

# 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://stylizededge-devs.gitbook.io/aqs-doc/readme.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.