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

# Editor Tools

Async Auto Exposure includes two editor tools under:

`Tools > Async Auto Exposure`

It also includes a custom Inspector for the `AsyncAutoExposure` component.

## AsyncAutoExposure Inspector

The Inspector is organized into:

* Shader
* Exposure Response
* Clamp Range
* Performance
* Presets
* Runtime Monitor

In Play Mode, the Runtime Monitor shows measured brightness, applied exposure, target exposure, and output texture size.

### Presets

| Preset           | Changes                                                 |
| ---------------- | ------------------------------------------------------- |
| Low Light        | Brighter target and wider upper exposure range          |
| Balanced         | General-purpose exposure response                       |
| Bright Source    | Lower target and lower maximum exposure                 |
| High Performance | Higher downsample factor and higher readback frame skip |
| High Quality     | Lower downsample factor and more frequent readback      |
| Reset            | Restores package defaults                               |

## Brightness Calculator

Use this tool to analyze the average brightness of a texture.

It can help you:

* Choose a good `targetBrightness`
* Classify test images as dark, normal, or bright
* Debug why exposure is changing too much or too little

### Workflow

1. Open `Tools > Async Auto Exposure > Brightness Calculator`.
2. Assign an input `Texture2D`.
3. Optionally assign the auto exposure shader. If empty, the tool loads `Resources/Shaders/AutoExposure`.
4. Enable `Consider Alpha Channel` when transparent pixels should be ignored.
5. Set `Downsample Factor`.
6. Click `Calculate Brightness`.
7. Use `Copy Settings to Clipboard` for a C# settings snippet.

If the texture is not readable, the tool can enable Read/Write on that asset through its import settings.

### Brightness Classes

| Brightness | Class       |
| ---------: | ----------- |
|    `< 0.2` | Very Dark   |
|    `< 0.3` | Dark        |
|    `< 0.5` | Normal      |
|    `< 0.7` | Bright      |
|   `>= 0.7` | Very Bright |

## Brightness Adjustment

Use this tool to preview exposure multipliers on a texture.

It can help you:

* Test `minExposure` and `maxExposure`
* Preview correction strength before entering Play Mode
* Save adjusted preview textures for inspection

### Workflow

1. Open `Tools > Async Auto Exposure > Brightness Adjustment`.
2. Assign a texture.
3. Adjust `Target Brightness`, `Speed`, `Min`, `Max`, and `Downsample`.
4. Click `Preview`.
5. Inspect brightness, exposure multiplier, and estimated corrected brightness.
6. Optionally click `Save Image`.

The preview uses the same exposure shader path as the runtime component.

## Notes

* Editor brightness tools use synchronous readback because they are one-off authoring tools.
* These tools are in the `AsyncAutoExposure.Editor` assembly and are not included in builds.
* Saved images from Brightness Adjustment are PNG files written to the path you choose in the save dialog.


---

# 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:

```
GET https://morningheartgames.gitbook.io/docs/asyncautoexposure/tools-and-shipping/editor-tools.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.