> 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/play-a-game.md). # Play a game Start a game, choose which emulator plays it, and what happens while it starts. ## From a game's page 1. Highlight a game in Home or Library and press **A**. Its page opens. 2. Press **A** on **Play**. ![A game's page](https://3008865259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiaV8VKDYJngjWWkPZx0Q%2Fuploads%2Fgit-blob-b5819b55bac6c963e1ad4066129736f903a5e635%2Fgame-page.png?alt=media) The page also shows the system, when you last played and how many times. Its tabs are covered in [The game page](/playing/game-page.md). ## Straight from a card **Hold A** on a game card in Home or Library to play it without opening its page. ## Before it starts: the pre-launch sheet **Hold A on Play** on a game's page to open the pre-launch sheet, **Play \**, before the game starts. It has: * **Emulator:** which emulator to use this time, when more than one can play the game. * **Quick options:** the game's first few [options](/playing/game-options.md), like resolution. * Which mods are on. Change them in the game's **Mods** tab. * **Play**, and **Play online** (see [Remote Play Together](/online/online/remote-play-together.md)). **B** or the **✕** closes it without playing. ## While it starts Kouch shows **Starting \** with its cover while the emulator opens. Then the emulator takes over the screen, with your players already set up. There's nothing to set up inside the emulator: Kouch gives it every seated controller in seat order, with motion where it's on. Emulators start **fullscreen**, in borderless fullscreen so the Quick Menu can show over them. If an emulator's window doesn't cover the screen, Kouch makes it fill the screen. You can open the [Quick Menu](/playing/quick-menu.md) at any time by holding **Select + Start**. ## If it doesn't start * **Couldn't find the game file.** The game file isn't where it was. If it's on a drive you unplugged, plug it back in. See [Unplugged drives](/library/library/unplugged-drives.md). * **No emulator for this system. Add one in Settings.** No emulator you've added plays this game's system. See [Add an emulator](/emulators/emulators/add-an-emulator.md). * **The emulator needs your own system files.** Kouch names the folder to copy them into. See [Your own system files](/emulators/emulators/system-files.md). * **Couldn't start the game. Check the emulator path in Settings.** The emulator isn't where its profile says. Check it in **Settings › Emulators**, or reinstall it from there. When a start fails, Kouch shows the reason and a **Back to library** button. ### If the emulator closes right away ![The emulator closed right away](https://3008865259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiaV8VKDYJngjWWkPZx0Q%2Fuploads%2Fgit-blob-cdf8f01d1bd12fcfb8e2dca56ab3cb9fe3f89543%2Fquick-exit.png?alt=media) Sometimes the emulator opens and closes again within seconds, often because of a graphics setting the PC doesn't support. Kouch then says **The emulator closed right away.** with how it ended (**Exit code …, after … s**, or **Stopped by the system, after … s**) and offers: * **Try again.** * **Try with \:** starts the game once with another renderer the emulator has. Your settings don't change; it's for this one launch. * **Close.** Kouch never retries by itself. ## Which emulator plays a game When only one of your emulators plays a system, Kouch uses it. When several do, choose one for each game with **Change emulator profile…** in its [game menu](/playing/game-page.md#the-game-menu) (**Start** on the game), or on its page in **Options › Emulator**. **Default for its system** follows the emulator set for the system. Kouch remembers the choice for that game. --- # 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/play-a-game.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.