> For the complete documentation index, see [llms.txt](https://docs.kouch.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kouch.dev/playing/graphics.md). # Graphics Every graphics setting an emulator has, for one game or for every game, with presets, defaults and restart-to-apply. The **Graphics** sheet gathers every graphics setting an emulator's profile describes, so you can change resolution, filtering, V-Sync and more without opening the emulator. ## Where to open it | From | Changes | Title | | ------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ------------------------- | | A game's menu (**Start** on the game) › **Graphics…** | This game only. *What you don't change follows the emulator's own settings.* | **Graphics: \** | | **Settings › Emulators › Graphics** on an emulator | Every game on that emulator. *A game can still change them for itself.* | **Graphics: \** | | The [Quick Menu](/playing/quick-menu.md) during a game › **Graphics** (*Resolution, filtering, V-Sync*) | The running game. | **Graphics: \** | ## The sheet ![The Graphics sheet for one game](https://3008865259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiaV8VKDYJngjWWkPZx0Q%2Fuploads%2Fgit-blob-51f47d0073bf6d353ca57d2c41d28fdd1f5a2870%2Fgraphics-sheet.png?alt=media) * **Automatic** or **Manual** comes first; see [below](#automatic-or-manual). * **Quality preset** comes next, for example **Performance**, **Balanced** or **Quality**, each with a line saying what it does. A preset sets several options at once; each stays adjustable afterwards. Once any option differs from the preset, it reads **Custom**. * Then the settings, in sections: **Renderer**, **Resolution**, **Image quality**, **Display**, **Screens and modes**, and any section the emulator's profile adds. For a dual-screen handheld system, **Screens and modes** holds the screen layout (by default a large main screen with the small one beside it), the main screen's size, where the second screen goes, and a swap; the Quick Menu can swap screens or change the layout mid-game. **LB / RB** jump between sections. * A setting you've changed says so underneath, for example **Changed · emulator default: Off**. * **X** (**Reset**) puts the highlighted setting back. **Reset to emulator default** at the end (for an emulator: **Reset to defaults**) puts them all back. V-Sync is off by default in Kouch's profiles. If the emulator's profile describes no graphics settings, the sheet says **This emulator's profile has no graphics settings.** The profile's author can add them; see [Write an emulator profile › Graphics settings](/for-creators/creators/emulator-profiles.md#graphics-settings). When another emulator for the same system does have them, the sheet adds **Another emulator for this system has them:** and a **Run this game with \** row for each. Choosing one switches the game to that emulator and shows its settings. ## During a game Some settings only take effect when the game starts. After changing one in the Quick Menu, the sheet says: **Changes apply the next time the game starts. Kouch closes it gracefully and starts it again; save first if the game needs it.** Choose **Restart game to apply**, or press **Y** (**Restart to apply**). The other buttons there are **Change**, **Reset** and **Back**. ## How it relates to Options Graphics settings are the **Graphics** group of a game's [options](/playing/game-options.md), laid out for easy changing. The same rule applies: a game's own setting wins over the emulator-wide one, which wins over the profile's default. ## Automatic or Manual At the top of the sheet you choose how an emulator's graphics are set. The first time, the sheet asks: *First time here: let Kouch set these for this device, or set them yourself.* * **Automatic:** *Kouch sets them for this PC* (or *this laptop*, *this handheld*, *the display it's docked to*), *again at every launch.* Kouch looks at the screen and the PC or handheld you play on and picks the resolution, anti-aliasing, texture filtering, renderer and docked mode to suit it. It never renders above what your display can show, and in the hand on a handheld it stays at 800p or less. * **Manual:** *Exactly what you set, on every device.* The choice is per emulator: on a game's sheet it says *For every game on \.* A setting Automatic picked says **Set by Automatic** underneath. Change any setting by hand and that emulator switches to **Manual**, keeping what Automatic had picked plus your change. Choose **Automatic** again to go back. A game's own settings always win over both. When the screen changes between launches, for example when you dock a handheld, Kouch says so as the game starts: **Docked: Automatic graphics now suit the display**, **In your hands: Automatic graphics now suit the handheld** or **Another display: Automatic graphics follow it**. --- # 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://docs.kouch.dev/playing/graphics.md?ask=&goal= ``` `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.