From c739e65ff3cf7f6e8736426e647e36cef1fa54d6 Mon Sep 17 00:00:00 2001 From: David Hedlund Date: Wed, 31 Jul 2024 04:39:00 +0200 Subject: [PATCH] Update controller-autoconfiguration.md improved "Understanding controller names" --- docs/guides/controller-autoconfiguration.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/guides/controller-autoconfiguration.md b/docs/guides/controller-autoconfiguration.md index c4249f617e..2ee6f24502 100644 --- a/docs/guides/controller-autoconfiguration.md +++ b/docs/guides/controller-autoconfiguration.md @@ -164,9 +164,12 @@ In RetroArch, the management of controller configurations is essential for ensur #### Understanding controller names -When you configure a controller in RetroArch, you can save its profile through the following path: -**Settings > Input > RetroPad Binds > Port 1 Controls > Save Controller Profile**. -This action generates a configuration file (e.g., "udev/Foo.cfg") that includes an `input_device` entry reflecting the controller's name (e.g., `input_device = Foo`). Notably, this name remains consistent across different controller drivers, including udev, sdl2, and linuxraw, as defined in **Settings > Drivers > Controller**. +When you save a controller profile (**Settings > Input > RetroPad Binds > Port 1 Controls > Save Controller Profile**), RetroArch generates a controller name (e.g., "Foo"). This name serves two purposes: + +1. It becomes part of the configuration file name (e.g., "udev/Foo.cfg"). +2. It's used as the value for the `input_device` variable within the configuration file (e.g., `input_device = "Foo"`). + +Importantly, this name remains consistent across various controller drivers, such as udev, sdl2, and linuxraw, as specified in **Settings > Drivers > Controller**. #### Variability of controller names