You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/input-and-controls.md
+63-55Lines changed: 63 additions & 55 deletions
Original file line number
Diff line number
Diff line change
@@ -7,62 +7,71 @@ RetroArch is intended to be easily controlled with a controller. RetroArch uses
7
7
RetroArch allows users to configure a controller once for many cores instead of having to configure each core individually. RetroArch also provides the freedom to configure specific cores and even individual games differently if the user wants.
8
8
9
9
### What is a RetroPad?
10
-
RetroArch controls map real-world controller inputs to a virtual controller called a "RetroPad". A RetroPad does not exist in real life, it's a concept only within RetroArch. A RetroPad has an ABXY layout like a SNES gamepad plus four shoulder buttons and dual analog sticks like a Sony DualShock.
10
+
RetroArch maps real-world controller inputs to a virtual controller called a `RetroPad`. A RetroPad resembles the common modern controller layout, and has:
11
11
12
-
You don't have to map all of the RetroPad buttons to a real world button. If your real controller has less buttons than a DualShock, then the virtual RetroPad also has less buttons, that's perfectly fine.
12
+
- a D-pad
13
+
- 4 face buttons with an ABXY layout like a SNES gamepad (that is: A-right, B-bottom, X-top, Y-left)
14
+
- Select / Start buttons
15
+
- two shoulder buttons (L1, R1)
16
+
- two trigger buttons (L2, R2)
17
+
- dual analog sticks like a Sony DualShock, which can also be used as a button (L3, R3).
You don't have to map all of the RetroPad buttons to a real world button. If your real controller has less buttons than a DualShock, then the virtual RetroPad will have some unmapped buttons, that's perfectly fine. If your real controller has more buttons, the extra buttons may be used as freely configurable hotkeys.
22
+
23
+
Conceptually, all RetroPad buttons can behave as analog (pressure sensitive), but the hardware typically only supports this for the trigger buttons. Gyroscope, acceleration, and illumination sensors may be supported, very much depending on the driver and the core.
24
+
16
25
### Controller autoconfiguration
17
-
Many controllers should work out of the box via the RetroArch autoconfiguration profile database. If the controller can be autoconfigured the OSD will inform you of the autoconfiguration event.
26
+
Most well-known controllers should work out of the box via the RetroArch autoconfiguration profile database. If the controller can be autoconfigured, the OSD will inform you of the autoconfiguration event. The menu hotkey is often pre-defined in the autoconfiguration profile.
18
27
19
28
!!! info "Manual RetroPad binding"
20
-
Not all controllers have autoconfigs. If that is the case for your controller, please refer to the **Manual RetroPad binding** section below.
29
+
Not all controllers have autoconfigs. If that is the case for your controller, please refer to the [Manual RetroPad Binding](#manual-retropad-binding).
21
30
22
31
## Keyboard controls
23
-
RetroArch provides a remappable set of bindings between a keyboard and the RetroPad abstraction as well as between a keyboard and RetroArch's hotkeys. Please refer to **Default RetroArch keyboardbindings** in this doc as a reference.
32
+
RetroArch provides a remappable set of bindings between a keyboard and the RetroPad abstraction as well as between a keyboard and RetroArch's hotkeys, details are [below](#default-retroarch-keyboard-bindings).
24
33
25
34
### Cores with direct keyboard input
26
-
Please be aware that some cores, for example arcade emulator cores and vintage computer emulator cores, can also be configured to directly read the keyboard or controls that use a keyboard interface. **If you are using a core configured for direct keyboard access, it is recommended that users unbind the RetroArch keyboard-to-RetroPad and hotkey bindings or use the `Game Focus` mode to disable those bindings while using the keyboard device.** Otherwise, keyboard input may result in multiple conflicting simultaneous actions by the core.
35
+
Please be aware that some cores, for example arcade emulator cores and vintage computer emulator cores, can also be configured to directly read the keyboard or controls that use a keyboard interface. **If you are using a core configured for direct keyboard access, it is recommended to use the `Game Focus` mode (default: Scroll Lock) to disable those bindings while using the keyboard device,**or unbind the conflicting RetroArch keyboard-to-RetroPad and hotkey bindings if only a few keys are needed. Otherwise, keyboard input will be captured by the RetroArch hotkeys and the core will not get the input.
27
36
28
37
!!! tip
29
-
Controls with keyboard interfaces can also benefit from defining a **Hotkey Enable** button in RetroArch which is required to be held down in order to activate the other hotkeys.
38
+
Controls with keyboard interfaces can also benefit from defining a **Hotkey Enable** button. If this hotkey is defined, other hotkeys will not be activated unless it is pressed.
30
39
31
40
## Manual RetroPad binding
32
41
33
-
If your gamepad does not have an autoconfiguration or if you would like to change its default RetroPad binding, use the **Input** settings menu.
42
+
If your gamepad is not recognized by autoconfiguration or if you would like to change its RetroPad binding, use the **Input** settings menu.
34
43
35
44
36
45
37
46
- Navigate to **Settings**
38
47
- Navigate to **Input**
39
-
- Navigate to **Input User 1 Binds**
40
-
- Select **User 1 Bind All**
41
-
- Press the buttons as required
48
+
- Navigate to **RetroPad Binds**
49
+
- Navigate to **Port 1 Controls**
50
+
- Select **Set All Controls**
51
+
- Press the buttons as required.
42
52
43
53
!!! tip
44
-
If you have several different controller types you may want to use the **User 1 Save Autoconfig** followed by **User 1 Bind Default All** options after binding in order to achieve hotplug functionality
54
+
If you have several different controllers, do **Save Controller Profile** after each binding so that controllers will be recognized next time automatically.
45
55
46
56
## Controls for multi-player
47
57
48
58
If you want to set-up local multi-player with games that support it:
49
59
50
60
- Navigate to **Settings**
51
61
- Navigate to **Input**
62
+
- Navigate to **RetroPad Binds**
52
63
53
-
Here you will find the option to set binds for multiple users, "Input User 1 Binds", "Input User 2 Binds" and so on.
54
-
55
-
So lets set-up User 1's controller:
64
+
Here you will find the option to set binds for multiple users. Let's set-up User 1's controller:
56
65
57
-
- Navigate to **Input User 1 Binds**
58
-
- Select **User 1 Device Index**
66
+
- Navigate to **Port 1 Controls**
67
+
- Select **Device Index**
59
68
60
-
From here using the left/right buttons, select which currently plugged-in controller will be assigned to what player. While here you should also bind the controls to this player by pressing them on the assigned controller, Select**User 1 Bind All**to do this.
69
+
Select which currently plugged-in controller will be assigned to this player. After you finish, go back, select**Port 2 Controls**and repeat for user 2.
61
70
62
-
After you finish, go back, select **Input User 2 Binds** and repeat for user 2.
71
+
In case of multiple controllers, RetroArch will assign them by default in the order they are presented by the operating system. For more customization, use the device reservation options to explicitly assign a controller to a player.
63
72
64
73
## Hotkeys
65
-
Hotkeys are combinations of buttons you can press in order to access options such as saving, loading, and exiting games. Hotkey binds can be configured at `Settings` → `Input` → `Input Hotkey Binds`. If you map `Enable Hotkeys` to a button, it will require that button to be held in order to trigger any hotkeys.
74
+
Hotkeys are combinations of buttons you can press in order to access options such as saving, loading, and exiting games. Hotkey binds can be configured at `Settings` → `Input` → `Hotkeys`. If you map `Enable Hotkeys` to a button, it will require that button to be held in order to trigger any hotkeys.
66
75
67
76
!!! tip
68
77
To unbind (effectively, disable) a hotkey, press **Del** on your keyboard or the **Y button** (the left one of the 4 buttons) on the RetroPad. To reset a hotkey to its default, press **Space** on your keyboard or the **Start** button on the RetroPad.
@@ -80,53 +89,52 @@ Core Controls Remapping alters how the core receives input rather than how the g
||| Help |
109
+
||| (see next section) |
99
110
100
111
### Menu controls
101
112
102
-
The keyboard inputs shown here are active only when `Settings` → `Input` → `Unified Menu Controls` is disabled (default). Otherwise, only Retropad inputs are used.
113
+
While in the menu, there are additional navigation keys defined for convenience.
||| Move cursor up |
107
-
||| Move cursor down |
108
-
||| Move cursor left |
109
-
||| Move cursor right |
110
-
||| Scroll one page up |
111
-
||| Scroll one page down |
112
-
||| Return to the previous screen |
||| Help |
117
-
||| Reset to default |
118
-
||| Scroll to top |
119
-
||| Scroll to bottom |
117
+
||| Return to the previous screen |
118
+
||| Select Item (note: Enter key is mapped to Select button in-game) |
||| Reset to default |
122
+
||| Scroll to previous letter |
123
+
||| Scroll to next letter |
124
+
||| Scroll to top |
125
+
||| Scroll to bottom |
126
+
127
+
Analog sticks are also able to control the menu. If needed, additional hotkeys can be disabled in `Settings` → `Input` → `Menu Controls`, along with several other customization options.
120
128
121
129
### Hotkey controls
122
130
123
-
Hotkey binds can be configured at `Settings` → `Input` → 'Input Hotkey Binds'. If you map `Enable Hotkeys` to a key, it will require that key to be held in order to trigger any hotkeys. This can be useful in avoiding keyboard mapping conflicts between RetroArch and cores cores that use the keyboard for input.
131
+
Hotkey binds can be configured at `Settings` → `Input` → `Hotkeys`. If you map `Enable Hotkeys` to a key, it will require that key to be held in order to trigger any hotkeys. This can be useful in avoiding keyboard mapping conflicts between RetroArch and cores cores that use the keyboard for input.
0 commit comments