Updated RGUI (markdown)
parent
8ce322571e
commit
7338b8aa20
20
RGUI.md
20
RGUI.md
|
@ -154,21 +154,29 @@ In some cases, Cg shaders cannot be supported. This goes for OpenGL ES drivers,
|
|||
## Configuring input
|
||||
Currently you can configure two settings per player (on PC):
|
||||
|
||||
- **Device**: Picks which gamepad to use for player N. A description of the pad is currently only available on Linux.
|
||||
- **Device**: Picks which gamepad to use for player N. The name of the pad is available.
|
||||
- **Device Type**: Picks which device type to use. This is relevant for the libretro core itself, and mostly useful for PlayStation, which needs to know if you're using a DualAnalog device or not.
|
||||
|
||||
Android and Wii ports allow you to configure binds more directly.
|
||||
### Configuring joypad input
|
||||
Configuring joypad input is supported from within RGUI.
|
||||
Normal gameplay binds as well as RGUI hotkey binding is supported. It is possible to bind everything in succession for convenience.
|
||||
|
||||
### Expanding
|
||||
This part of RGUI is still somewhat immature on PC. We would ideally like a more direct way to configure input binds on PC here.
|
||||
### Configuring keyboard input
|
||||
Configuring keyboard input is currently not supported. To configure keyboard binds, it must be done outside RGUI.
|
||||
|
||||
### Configuring input outside of RGUI
|
||||
There are a couple of options available to configure input outside RGUI.
|
||||
|
||||
- **RetroArch-Phoenix**: This is probably the most convenient option at the moment if you like point-and-click GUIs.
|
||||
- **RetroArch-Phoenix**: This is probably the most convenient option at the moment if you like point-and-click GUIs. Note that Phoenix frontend is deprecated and won't receive support anymore.
|
||||
- **retroarch-joyconfig**: A command-line tool (part of RetroArch package) which lets you get input from a joypad and update or create a config file. To update a config with new binds for player 1 using joypad #0, you would for example do `retroarch-joyconfig --player 1 --joypad 0 --input ~/.config/retroarch/retroarch.cfg --output ~/.config/retroarch/retroarch.cfg` (see `--help` or man page for more help). By default, only RetroPad binds are bound. You can use `--misc` to bind other hotkeys as well. If you want to use `retroarch-joyconfig`, you should build latest from Git (after 0.9.9-wip1) as a couple of needed changes were made to improve usability.
|
||||
|
||||
## Setting up joypad autoconfiguration (Linux)
|
||||
## Joypad autoconfiguration
|
||||
|
||||
### XInput (Windows)
|
||||
When using XInput driver on Windows, XInput-enabled gamepads will be automatically configured for you.
|
||||
Ideally, you shouldn't have to configure input at all with this.
|
||||
|
||||
### Setting up joypad autoconfiguration (Linux)
|
||||
Linux port recently (after 0.9.9-wip1) got support for joypad hotplugging.
|
||||
This allows joypad to be plugged in and out of your machine while running.
|
||||
To have a more console-like experience, RetroArch supports joypad autoconfiguration, where the input config is updated depending on which devices are plugged in.
|
||||
|
|
Loading…
Reference in New Issue