> 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/getting-started/quick-start.md).

# Quick Start (10 Minutes)

This gets you from a fresh install to a working, on-screen settings menu. No C++ required for any of these steps.

## 1. Create a Preset

Content Browser → right-click → **Auto Quality Switcher → AQS Graphics Preset**. Name it `GP_Test`. Open it — every field is already pre-filled with sensible defaults. You don't need to change anything to continue.

## 2. Bake the Descriptors

Content Browser → right-click → **Auto Quality Switcher → AQS Baked Descriptors**. Name it `DA_AQS_Descriptors`. Open it, and click the teal **Bake Now** button at the top.

This reads every field on the preset data struct and builds the row list your menu will render. You'll do this once now, and again any time you add or remove a setting field later.

## 3. Build the 9 Row Templates (If You Haven't Yet)

Each control type (slider, toggle, dropdown, etc.) needs one small Widget Blueprint. See [**The 9 Row Templates**](/aqs-doc/building-menus/the-9-row-templates.md) for the exact spec of each — they're small, and you only build them once per project, ever.

> **Already have them from a previous AQS project?** Copy the `Content/WidgetTemplates/` folder over and skip to Step 4.

## 4. Create the Auto Panel

Content Browser → create a Widget Blueprint, parent class **AQSAutoPanel**. Name it `WBP_AQS_AutoPanel`.

In its Class Defaults:

* **BakedDescriptors** → `DA_AQS_Descriptors`
* **RowTemplateClasses** → map all 9 control types to your row templates ([see the map-editing gotcha](/aqs-doc/advanced/troubleshooting.md#cant-add-a-new-key-to-the-map) if you hit an error here)

In the Designer, add a **Vertical Box** or **Scroll Box** inside it named exactly `RowContainer`, with **Is Variable** checked.

## 5. Drop It Into a Menu

Create any Widget Blueprint to act as your menu shell — even a blank one works for testing. Drag `WBP_AQS_AutoPanel` into it.

## 6. Get It On Screen

The fastest way to test: open your level's **Level Blueprint** → **Event BeginPlay**:

```
Get AQS Subsystem (self)
  → Setup AQS (Presets: [GP_Test], bAutoApplyOnInit: true)

Create Widget (your menu shell)
  → Add to Viewport
```

## 7. Press Play

You should see one row per setting. Drag a slider, flip a toggle — it should apply live immediately.

## What's Next

* [**Core Concepts**](/aqs-doc/getting-started/core-concepts.md) — understand why the system is shaped this way before you customize it
* [**Descriptor Overrides**](/aqs-doc/building-menus/descriptor-overrides.md) — hide fields, rename labels, change control types, build a minimal vs. full-control menu
* [**Grouping & Ordering Rows**](/aqs-doc/building-menus/grouping-and-ordering.md) — organize rows into named sections like "Lighting" or "Shadows"


---

# 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/getting-started/quick-start.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.