mirror of
https://github.com/holub/mame
synced 2025-04-26 18:23:08 +03:00
6432d66037
* Case sensitivity training for INI (nw) The world is not 100% Windows, so case sensitvity is needed. * Further standardization of the formatting (nw) More to go... * Pass 2 of new formatting wave (nw) More to go, though. * wave 3 of formatting cleanup (nw) Further adjustments and cleanups, including unwanted tabs. * Correct filtering instructions (nw)
77 lines
4.8 KiB
ReStructuredText
77 lines
4.8 KiB
ReStructuredText
Stable Controller IDs
|
|
===============================
|
|
|
|
By default, the mapping between devices and controller IDs is not stable. For instance, a gamepad controller may be assigned to "Joy 1" initially, but after a reboot, it may get re-assigned to "Joy 3".
|
|
|
|
The reason is that MAME enumerates attached devices and assigns controller IDs based on the enumeration order. Factors that can cause controller IDs to change include plugging / unplugging USB devices, changing ports / hubs and even system reboots.
|
|
|
|
It is quite cumbersome to ensure that controller IDs are always correct.
|
|
|
|
That's where the "mapdevice" configuration setting comes into the picture. This setting allows you to map a device id to a controller ID, ensuring that the specified device always maps to the same controller ID in MAME.
|
|
|
|
Usage of mapdevice
|
|
------------------
|
|
The "mapdevice" xml element is specified under the input xml element in the controller configuration file. It requires two attributes, "device" and "controller".
|
|
NOTE: This setting only take effect when added to the **ctrlr** config file.
|
|
|
|
The "device" attribute specifies the id of the device to match. It may also be a substring of the id. To see the list of available devices, enable verbose output and available devices will then be listed to the console at startup (more on this below).
|
|
|
|
The "controller" attribute specifies the MAME controller ID. It is made up of a controller class (i.e. ``JOYCODE``, ``GUNCODE``, ``MOUSECODE``) and controller index. For example: ``JOYCODE_1``.
|
|
|
|
Example
|
|
-------
|
|
Here's an example:
|
|
|
|
| <mameconfig version="10">
|
|
| <system name="default">
|
|
| <input>
|
|
| **<mapdevice device="VID_D209&PID_1601" controller="GUNCODE_1" />**
|
|
| **<mapdevice device="VID_D209&PID_1602" controller="GUNCODE_2" />**
|
|
| **<mapdevice device="XInput Player 1" controller="JOYCODE_1" />**
|
|
| **<mapdevice device="XInput Player 2" controller="JOYCODE_2" />**
|
|
|
|
|
| <port type="P1_JOYSTICK_UP">
|
|
| <newseq type="standard">
|
|
| JOYCODE_1_YAXIS_UP_SWITCH OR KEYCODE_8PAD
|
|
| </newseq>
|
|
| </port>
|
|
| ...
|
|
|
|
|
|
In the above example, we have four device mappings specified:
|
|
|
|
The first two mapdevice entries map player 1 and 2 lightguns to Gun 1 and Gun 2, respectively. We use a substring of the full raw device names to match each devices. Note that, since this is XML, we needed to escape the ``&`` using ``&``.
|
|
|
|
The last two mapdevices entries map player 1 and player 2 gamepad controllers to Joy 1 and Joy 2, respectively. In this case, these are XInput devices.
|
|
|
|
Listing Available Devices
|
|
-------------------------
|
|
How did we obtain the device id's in the above example? Easy!
|
|
|
|
Run MAME with -v parameter to enable verbose output. It will then list available devices include the corresponding "device id" to the console.
|
|
|
|
Here an example:
|
|
|
|
| Input: Adding Gun #0:
|
|
| Input: Adding Gun #1:
|
|
| Input: Adding Gun #2: HID-compliant mouse (**device id: \\?\HID#VID_045E&PID_0053#7&18297dcb&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}**)
|
|
| Input: Adding Gun #3: HID-compliant mouse (**device id: \\?\HID#IrDeviceV2&Col08#2&2818a073&0&0007#{378de44c-56ef-11d1-bc8c-00a0c91405dd}**)
|
|
| Input: Adding Gun #4: HID-compliant mouse (**device id: \\?\HID#VID_D209&PID_1602&MI_02#8&389ab7f3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}**)
|
|
| Input: Adding Gun #5: HID-compliant mouse (**device id: \\?\HID#VID_D209&PID_1601&MI_02#9&375eebb1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}**)
|
|
| Input: Adding Gun #6: HID-compliant mouse (**device id: \\?\HID#VID_1241&PID_1111#8&198f3adc&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}**)
|
|
| Skipping DirectInput for XInput compatible joystick Controller (XBOX 360 For Windows).
|
|
| Input: Adding Joy #0: ATRAK Device #1 (**device id: ATRAK Device #1**)
|
|
| Skipping DirectInput for XInput compatible joystick Controller (XBOX 360 For Windows).
|
|
| Input: Adding Joy #1: ATRAK Device #2 (**device id: ATRAK Device #2**)
|
|
| Input: Adding Joy #2: XInput Player 1 (**device id: XInput Player 1**)
|
|
| Input: Adding Joy #3: XInput Player 2 (**device id: XInput Player 2**)
|
|
|
|
|
|
|
Furthermore, when devices are mapped using mapdevice, you'll see that in the verbose logging too, such as:
|
|
|
|
| Input: Remapped Gun #0: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#9&375eebb1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
|
|
| Input: Remapped Gun #1: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#8&389ab7f3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
|
|
| Input: Remapped Joy #0: XInput Player 1 (device id: XInput Player 1)
|
|
| Input: Remapped Joy #1: XInput Player 2 (device id: XInput Player 2)
|
|
|
|