> 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/troubleshooting/common-problems.md). # Common problems Fixes for the problems testers run into most. ## Controllers
Controllers don't work, or only some do * **Start Kouch from Steam.** Steam only gives controllers and motion to programs it starts. If Kouch says **For controllers, start Kouch from Steam**, close it and start it from your Steam library. See [Start Kouch from Steam](/getting-started/start-from-steam.md). * Press **A** on each controller to join. Kouch doesn't seat controllers until you do, unless you turn on **Settings › Players › Seat new controllers automatically**. * On the Players screen, **Start** shows **Controller not connecting?** with more tips.
Every button press happens twice * **Kouch was started outside Steam.** Steam's desktop controller layout then also turns your controller into a mouse and keys. Start Kouch from Steam. * **In a game, with the keyboard as a player:** the emulator reads the keyboard too. Turn off the emulator's own keyboard input. See [Keyboard and mouse as a player](/controllers/keyboard-and-mouse.md).
Motion drifts, or the game thinks the controller is tilted Put the controller on a flat surface, then **Settings › Controllers › Test a controller › Recalibrate motion**, or **Controller tools › Recalibrate motion** in the Quick Menu. See [Motion](/controllers/motion.md).
The wrong person is Player 1 Press **LT** on your controller on the Players screen. See [Players and seats](/controllers/players-and-seats.md).
## Games and emulators
My games don't show up * Check they're in the right folder: `Emulation\roms\`, or a folder in **Settings › Paths** set to the right system. * You need an emulator that plays that system. **Settings › Storage** lists **Game folders no emulator uses yet**. * Kouch looks for games when it starts, after you add a folder and after you import an emulator. Added games while it was open? Start it again.
A game won't start Kouch says why. The most common reasons: * **The emulator needs your own system files:** copy them into the folder Kouch names. See [Your own system files](/emulators/emulators/system-files.md). * **Couldn't find the game file:** it moved, or it's on an unplugged drive. * **Couldn't start the game. Check the emulator path in Settings.** The emulator isn't where its profile says. Check **Settings › Emulators**, or **Update** it there to reinstall it. * **The emulator closed right away.** Choose **Try with …** to start it once with another renderer. If that works, change the renderer for good in the game's [Graphics](/playing/graphics.md). See [If the emulator closes right away](/playing/play-a-game.md#if-the-emulator-closes-right-away).
The Quick Menu doesn't show over a game * Hold **Select + Start** together for a full second. * The emulator is probably in **exclusive** fullscreen. Set it to **borderless** fullscreen, which is what Kouch's profiles use.
Save state, load state or screenshot does nothing These press the emulator's own shortcut keys, which come from its profile. An emulator added by hand doesn't have them. Import a profile for it instead. See [Save states and screenshots](/playing/save-states-and-screenshots.md).
An emulator hangs when quitting Kouch closes it by itself after a few seconds. If it's still there after 10 seconds, hold **A** on **Force quit**. See [Quit a game](/playing/quit-a-game.md).
A game has no cover art Check **Settings › Game art**: **Find art online** should be on, and the system needs an **Art source name**. Or add your own SteamGridDB key and choose **Look again for every game**. See [Game art](/library/library/art.md).
## Windows
Kouch says it's running as administrator That's because Steam was started as administrator. It works, and the emulators Kouch starts run as administrator too. Two side effects: * **Dropping files on the Kouch window does nothing**, because Windows blocks it. Use **Settings › Emulators › Import profile**, or a `kouch://` link. * Kouch mentions it once; **Settings › About** keeps showing it. To avoid both, start Steam normally.
Dropping a .kod file does nothing See above: Steam, and so Kouch, runs as administrator. Use **Settings › Emulators › Import profile** instead.
## Steam Deck
Kouch takes a few seconds to appear That's normal for the first start after an update. Later starts are quick.
Steam's keyboard doesn't open when I type In Game Mode Steam's keyboard can't open over a non-Steam game, so Kouch opens its own. You can still open Steam's with **Steam + X**. See [Typing with a controller](/controllers/typing.md).
"Add games to Steam" won't run In Game Mode, use the Kouch Decky plugin from the Quick Access menu. See [Your games in Steam's library](/steam/steam/steam-library.md).
## Linux
Settings › Controllers says "this user can't open /dev/uinput" Kouch's virtual controllers (for emulators whose profile asks for them) need access to `/dev/uinput`. SteamOS already allows it. On other Linux systems: 1. Install your distribution's **steam-devices** package. It gives the signed-in user access to `/dev/uinput`. 2. Log out and back in. If your distribution has no such package, add the rule yourself. Create `/etc/udev/rules.d/60-kouch-uinput.rules` containing: ``` KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", OPTIONS+="static_node=uinput" ``` Then run: ``` sudo udevadm control --reload-rules && sudo udevadm trigger ``` and log out and back in. Games still get your controllers the usual way in the meantime.
## Still stuck? [Create a report](/troubleshooting/create-a-report.md) and send it to the Kouch team with what you did, what you expected and what happened. --- # 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/troubleshooting/common-problems.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.