

If you swap out your device with another model, the mapping will Numbers have generally no relation to the physical placement of the game padīuttons.

The above configuration is not suited for this, because button Similarly, you can useīutton_0 (first button), button_1 (second button) and so on:įor most game pads you can use universal event names instead and make theĬonfiguration work identically even with different types of game padsĬonnected. joystick_0 is theįirst joystick connected, joystick_1 is the second, etc. Here are the different types of event names you can use. I have put the list of available actions on its own pageĭue to the large number of actions. The primary Amiga joystick (joy_1 is the joystick in joystick port 1): keyboard_key_q = action_joy_1_fire_buttonĮxamples of input actions are: action_joy_1_fire_button (fire button on joystick in port 1)Īction_key_z (press amiga keyboard key Z)Īction_drive_0_insert_floppy_0 (insert disk from floppy image list) Here is a specific example, mapping the keyboard key q to the fire button on To map an action, you add a line like this to your configuration file: devicename_eventname = actionname Gamepad? You can map game pad buttons to the Amiga keyboard F1, F2, F3, F4,Ĭursor down, left shift and right shift keys.
