libretro/docs
1
0
Fork 0
mirror of https://github.com/libretro/docs.git synced 2024-11-23 08:49:57 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update controller-autoconfiguration.md

Browse Source 
minor
This commit is contained in:
David Hedlund 2024-08-21 09:36:49 +02:00 committed by GitHub
parent 758825e877
commit 5bcd8b8fb2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/guides/controller-autoconfiguration.md
View File

@ -167,7 +167,7 @@ If your joypad is not recognized by RetroArch even after updating the profiles,
1. To avoid other controllers from interfering with your mapping when starting RetroArch, follow these steps: Disconnect all joypads by unplugging their cables or disconnecting them from any wireless connections.
2. Connect the controller intended for autoconfiguration. Ensure your system supports the selected connectivity method. If your joypad supports both wired and wireless connections and the initial attempt (e.g., via USB) fails, try the alternative option (e.g., Bluetooth). For example, the Nintendo Switch Pro Controller does not support USB connection on Linux 5.15 and older but does support Bluetooth.
3. For Android, run the [Android](#android) steps first.
4. **Important: Remove Previously Set Manual Bindings**: Manual bindings take precedence over autoconfig files, so it's crucial to remove them if you've previously used the Save Controller Profile command. To do this, navigate to Settings -> Input -> RetroPad Binds -> Port 1 Controls -> Reset to Default Controls. Failing to reset these bindings might result in outdated configurations being applied to a new controller file, especially if the new controller has fewer buttons. Additionally, if you're creating autoconfig files for various controller drivers (such as sdl2, udev, etc.), it's important to clear manual bindings. Neglecting this step could lead to incorrect responses from both the Remote RetroPad and games tested in cores.
4. **Important: Remove Previously Set Manual Bindings**: Manual bindings take precedence over autoconfig files, so it's crucial to remove them if you've previously used the Save Controller Profile command. To do this, navigate to `Settings -> Input -> RetroPad Binds -> Port 1 Controls -> Reset to Default Controls`. Failing to do so will result in incorrect responses from cores, such as Remote RetroPad and console emulators, if you have created autoconfig files for different controller drivers like SDL2 or UDEV, as they have varying bindings.
5. Use `Settings` -> `Input` -> `RetroPad Binds` -> `Port 1 Controls` -> `Set All Controls`. If automatic mapping fails for any button (e.g., due to lack of driver support), the process will be interrupted. In case of interruption, manually map the remaining buttons, starting from the one that caused the interruption and continuing through the rest of the list.
6. If applicable, then also set the menu button binding in `Settings` -> `Input` -> `Hotkeys` -> `Menu Toggle`
7. Use `Settings` -> `Input` -> `RetroPad Binds` -> `Port 1 Controls` -> `Save Controller Profile`