FS-UAE Input Actions

Here are all the valid names for input actions listed. See Custom Input Mapping for information about how to use these action names.

Please note that not all actions are supported, and only digital actions are support for now (you cannot yet control the Amiga mouse properly with custom input mapping). The list will be updated later with more description (and actions that are not supported will be purged)

action_none
action_screenshot
action_mouse_0_horiz
action_mouse_0_vert
action_mouse_0_horiz_inv
action_mouse_0_vert_inv
action_mouse_0_up
action_mouse_0_down
action_mouse_0_left
action_mouse_0_right
action_mouse_0_wheel
action_mouse_cdtv_horiz
action_mouse_cdtv_vert
action_mouse_cdtv_up
action_mouse_cdtv_down
action_mouse_cdtv_left
action_mouse_cdtv_right
action_joy_0_horiz
action_joy_0_vert
action_joy_0_horiz_pot
action_joy_0_vert_pot
action_joy_0_horiz_pot_inv
action_joy_0_vert_pot_inv
action_joy_0_left
action_joy_0_right
action_joy_0_up
action_joy_0_down
action_joy_0_left_up
action_joy_0_left_down
action_joy_0_right_up
action_joy_0_right_down
action_joy_0_fire_button
action_joy_0_2nd_button
action_joy_0_3rd_button
action_joy_0_cd32_play
action_joy_0_cd32_rwd
action_joy_0_cd32_ffw
action_joy_0_cd32_green
action_joy_0_cd32_yellow
action_joy_0_cd32_red
action_joy_0_cd32_blue
action_mouse_1_horiz
action_mouse_1_vert
action_mouse_1_horiz_inv
action_mouse_1_vert_inv
action_mouse_1_up
action_mouse_1_down
action_mouse_1_left
action_mouse_1_right
action_joy_1_horiz
action_joy_1_vert
action_joy_1_horiz_pot
action_joy_1_vert_pot
action_joy_1_horiz_pot_inv
action_joy_1_vert_pot_inv
action_joy_1_left
action_joy_1_right
action_joy_1_up
action_joy_1_down
action_joy_1_left_up
action_joy_1_left_down
action_joy_1_right_up
action_joy_1_right_down
action_joy_1_fire_button
action_joy_1_2nd_button
action_joy_1_3rd_button
action_joy_1_cd32_play
action_joy_1_cd32_rwd
action_joy_1_cd32_ffw
action_joy_1_cd32_green
action_joy_1_cd32_yellow
action_joy_1_cd32_red
action_joy_1_cd32_blue
action_lightpen_horiz
action_lightpen_vert
action_lightpen_left
action_lightpen_right
action_lightpen_up
action_lightpen_down
action_par_joy_0_horiz
action_par_joy_0_vert
action_par_joy_0_left
action_par_joy_0_right
action_par_joy_0_up
action_par_joy_0_down
action_par_joy_0_left_up
action_par_joy_0_left_down
action_par_joy_0_right_up
action_par_joy_0_right_down
action_par_joy_0_fire_button
action_par_joy_0_2nd_button
action_par_joy_1_horiz
action_par_joy_1_vert
action_par_joy_1_left
action_par_joy_1_right
action_par_joy_1_up
action_par_joy_1_down
action_par_joy_1_left_up
action_par_joy_1_left_down
action_par_joy_1_right_up
action_par_joy_1_right_down
action_par_joy_1_fire_button
action_par_joy_1_2nd_button
action_key_f1
action_key_f2
action_key_f3
action_key_f4
action_key_f5
action_key_f6
action_key_f7
action_key_f8
action_key_f9
action_key_f10
action_key_esc
action_key_tab
action_key_ctrl
action_key_ctrl_right
action_key_caps_lock
action_key_shift_left
action_key_alt_left
action_key_amiga_left
action_key_amiga_right
action_key_alt_right
action_key_shift_right
action_key_space
action_key_cursor_up
action_key_cursor_down
action_key_cursor_left
action_key_cursor_right
action_key_help
action_key_del
action_key_backspace
action_key_return
action_key_a
action_key_b
action_key_c
action_key_d
action_key_e
action_key_f
action_key_g
action_key_h
action_key_i
action_key_j
action_key_k
action_key_l
action_key_m
action_key_n
action_key_o
action_key_p
action_key_q
action_key_r
action_key_s
action_key_t
action_key_u
action_key_v
action_key_w
action_key_x
action_key_y
action_key_z
action_key_enter
action_key_np_0
action_key_np_1
action_key_np_2
action_key_np_3
action_key_np_4
action_key_np_5
action_key_np_6
action_key_np_7
action_key_np_8
action_key_np_9
action_key_np_period
action_key_np_add
action_key_np_sub
action_key_np_mul
action_key_np_div
action_key_np_lparen
action_key_np_rparen
action_key_2b
action_key_30
action_key_backquote
action_key_1
action_key_2
action_key_3
action_key_4
action_key_5
action_key_6
action_key_7
action_key_8
action_key_9
action_key_0
action_key_sub
action_key_equals
action_key_backslash
action_key_leftbracket
action_key_rightbracket
action_key_semicolon
action_key_singlequote
action_key_comma
action_key_period
action_key_div
action_mousewheel_down
action_mousewheel_up
action_key_cdtv_stop
action_key_cdtv_playpause
action_key_cdtv_prev
action_key_cdtv_next
action_key_cdtv_rew
action_key_cdtv_ff
action_key_0e
action_key_1c
action_key_2c
action_key_3b
action_key_47
action_key_48
action_key_49
action_key_4b
action_key_68
action_key_69
action_key_6a
action_key_6b
action_key_6c
action_key_6d
action_key_6e
action_key_6f
action_key_70
action_key_71
action_key_78
action_key_79
action_key_7a
action_key_7b
action_key_7c
action_key_7d
action_key_7e
action_key_7f
action_activate_cartridge (1.3.17+)
action_eject_floppy_0
action_eject_floppy_1
action_eject_floppy_2
action_eject_floppy_3
action_pause
action_warp
action_irq_7
action_state_rewind
action_state_current
action_state_capture
action_volume_down
action_volume_up
action_volume_mute
action_master_volume_down
action_master_volume_up
action_master_volume_mute
action_quit
action_soft_reset
action_hard_reset
action_switch_interpol
action_disk_swapper_next
action_disk_swapper_prev
action_disk_swapper_insert_0
action_disk_swapper_insert_1
action_disk_swapper_insert_2
action_disk_swapper_insert_3
action_disk_prev_0
action_disk_prev_1
action_disk_prev_2
action_disk_prev_3
action_disk_next_0
action_disk_next_1
action_disk_next_2
action_disk_next_3
action_arcadia_diagnostics
action_arcadia_player_1
action_arcadia_player_2
action_arcadia_coin_1
action_arcadia_coin_2
action_cdtv_front_panel_stop
action_cdtv_front_panel_playpause
action_cdtv_front_panel_prev
action_cdtv_front_panel_next
action_cdtv_front_panel_rew
action_cdtv_front_panel_ff
action_save_state_1
action_save_state_2
action_save_state_3
action_save_state_4
action_save_state_5
action_save_state_6
action_save_state_7
action_save_state_8
action_save_state_9
action_restore_state_1
action_restore_state_2
action_restore_state_3
action_restore_state_4
action_restore_state_5
action_restore_state_6
action_restore_state_7
action_restore_state_8
action_restore_state_9
action_drive_0_insert_floppy_0
action_drive_0_insert_floppy_1
action_drive_0_insert_floppy_2
action_drive_0_insert_floppy_3
action_drive_0_insert_floppy_4
action_drive_0_insert_floppy_5
action_drive_0_insert_floppy_6
action_drive_0_insert_floppy_7
action_drive_0_insert_floppy_8
action_drive_0_insert_floppy_9
action_drive_0_insert_floppy_10
action_drive_0_insert_floppy_11
action_drive_0_insert_floppy_12
action_drive_0_insert_floppy_13
action_drive_0_insert_floppy_14
action_drive_0_insert_floppy_15
action_drive_0_insert_floppy_16
action_drive_0_insert_floppy_17
action_drive_0_insert_floppy_18
action_drive_0_insert_floppy_19
action_drive_1_insert_floppy_0
action_drive_1_insert_floppy_1
action_drive_1_insert_floppy_2
action_drive_1_insert_floppy_3
action_drive_1_insert_floppy_4
action_drive_1_insert_floppy_5
action_drive_1_insert_floppy_6
action_drive_1_insert_floppy_7
action_drive_1_insert_floppy_8
action_drive_1_insert_floppy_9
action_drive_1_insert_floppy_10
action_drive_1_insert_floppy_11
action_drive_1_insert_floppy_12
action_drive_1_insert_floppy_13
action_drive_1_insert_floppy_14
action_drive_1_insert_floppy_15
action_drive_1_insert_floppy_16
action_drive_1_insert_floppy_17
action_drive_1_insert_floppy_18
action_drive_1_insert_floppy_19
action_drive_2_insert_floppy_0
action_drive_2_insert_floppy_1
action_drive_2_insert_floppy_2
action_drive_2_insert_floppy_3
action_drive_2_insert_floppy_4
action_drive_2_insert_floppy_5
action_drive_2_insert_floppy_6
action_drive_2_insert_floppy_7
action_drive_2_insert_floppy_8
action_drive_2_insert_floppy_9
action_drive_2_insert_floppy_10
action_drive_2_insert_floppy_11
action_drive_2_insert_floppy_12
action_drive_2_insert_floppy_13
action_drive_2_insert_floppy_14
action_drive_2_insert_floppy_15
action_drive_2_insert_floppy_16
action_drive_2_insert_floppy_17
action_drive_2_insert_floppy_18
action_drive_2_insert_floppy_19
action_drive_3_insert_floppy_0
action_drive_3_insert_floppy_1
action_drive_3_insert_floppy_2
action_drive_3_insert_floppy_3
action_drive_3_insert_floppy_4
action_drive_3_insert_floppy_5
action_drive_3_insert_floppy_6
action_drive_3_insert_floppy_7
action_drive_3_insert_floppy_8
action_drive_3_insert_floppy_9
action_drive_3_insert_floppy_10
action_drive_3_insert_floppy_11
action_drive_3_insert_floppy_12
action_drive_3_insert_floppy_13
action_drive_3_insert_floppy_14
action_drive_3_insert_floppy_15
action_drive_3_insert_floppy_16
action_drive_3_insert_floppy_17
action_drive_3_insert_floppy_18
action_drive_3_insert_floppy_19
action_joyport_0_mode_none
action_joyport_0_mode_mouse
action_joyport_0_mode_djoy
action_joyport_0_mode_gamepad
action_joyport_0_mode_ajoy
action_joyport_0_mode_cdtvjoy
action_joyport_0_mode_cd32joy
action_joyport_0_mode_lightpen
action_joyport_1_mode_none
action_joyport_1_mode_mouse
action_joyport_1_mode_djoy
action_joyport_1_mode_gamepad
action_joyport_1_mode_ajoy
action_joyport_1_mode_cdtvjoy
action_joyport_1_mode_cd32joy
action_joyport_1_mode_lightpen
action_joyport_2_mode_none
action_joyport_2_mode_mouse
action_joyport_2_mode_djoy
action_joyport_2_mode_gamepad
action_joyport_2_mode_ajoy
action_joyport_2_mode_cdtvjoy
action_joyport_2_mode_cd32joy
action_joyport_2_mode_lightpen
action_joyport_3_mode_none
action_joyport_3_mode_mouse
action_joyport_3_mode_djoy
action_joyport_3_mode_gamepad
action_joyport_3_mode_ajoy
action_joyport_3_mode_cdtvjoy
action_joyport_3_mode_cd32joy
action_joyport_3_mode_lightpen

27 thoughts on “FS-UAE Input Actions

  1. Hi there.
    The dedicated autofire button works well on my PS3 game pad, but how to assign it to a keyboard key like left alt key?
    I’m using FS-UAE on a Mac but everything I tried won’t work:

    1. extra options in the main FS-UAE configuration
    2. own configuration for a certain game

    I’ve mapped keyboard_key_lalt = joystick_1_right_trigger and vice versa but it won’t work.

    How can I achieve this?

    Regards,
    Christian

    • You want something like this: keyboard_key_lalt = action_joy_1_autofire_button

      (If you use recent dev versions you also need to toggle full keyboard mode with Alt+K to be able to use the left alt key for input mapping)

  2. I would also like kindly ask if you could consider adding the Autofire/Rapid Fire Button mentioned here.

    On the original Competition Pro Joystick (at least my transparent blue version) I used to have on the Amiga, you would have the large round buttons being regular and the small triangle buttons set to autofire.

    Unfortunately the Speed Link USB Model you can buy today can only switch autofire on for all 4 buttons or completely off. This is quite cumbersome especially for a game like Turrican where you constantly require both.

    Apart from this request, thank you so much for this great emulator!

    • Hi, FS-UAE 2.6 includes support for a separate auto-fire button:
      * Separate auto-fire button (based on patch from S. Jordan).
      * Dedicated auto-fire button mapped to “right trigger” by default.

      You need to either:
      – map a button manually to the new autofire action via custom input mapping
      – create a custom controller config
      – or use the FS-UAE Launcher joystick mapping tool, and just tell FS-UAE Launcher that the button you want to use for auto-fire is “left trigger”. If you do this, you also need to map all the buttons and axes you want to use on the joystick. Just map the stick to the d-pad, and the regular fire button should be “south button”. Use “west button” for secondary fire.

      The last option should be the easiest!

  3. hi.. i have added floppys to a swaplist.. example:
    floppy_drive_0 = Pinball Dreams (1992)(21st Century)(Disk 1 of 2)[cr FLT].adf
    floppy_image_0 = Pinball Dreams (1992)(21st Century)(Disk 1 of 2)[cr FLT].adf
    floppy_image_1 = Pinball Dreams (1992)(21st Century)(Disk 2 of 2)[cr FLT].adf

    is it possible to swap to next file in list with an input command

    i tried:
    action_disk_swapper_nextΒ = action_key_n

    am i missing something or how do i achieve this. dont want to use f12 and swap manually..

    • Hi, unfortunately the disk swapper actions are not implemented in FS-UAE. The action list is generated based on the WinUAE sources and not all actions are implemented (I have now marked them with a strikeout effect in the list). I have also opened an enhancement issue to implement some kind of swapping shortcuts. You can subscribe to the issue at https://github.com/FrodeSolheim/fs-uae/issues/52 to get further updates on this matter πŸ™‚

    • Actually, the disk swapping actions work, but you also need to use for example action_disk_swapper_insert_0 to insert the disk you have “navigated to” using prev/next actions into DF0.

      By the way, the upcoming 2.7.4dev will show a GUI message when using these actions, so you can see what the currently selected floppy is.

  4. Hi,

    First of all, a big thanks, and congratulations for this amazing emulator. I can now travel back to A500 times, on my Linux box, without having to reboot to Windows.

    I’m currently trying to map my gamepad start button to the pause FS-UAE function, and it doesn’t seem to work. For example, I tried this line in Battle Squadron config:

    joystick_0_start_button = action_key_p
    ==> It works well. I have the ingame pause: the mapping works well. But…

    joystick_0_start_button = action_pause
    ==> Does nothing.

    It seems that action_pause just doesn’t work.

    I’m using FS-UAE 2.4.1 on Kubuntu 12.04, package from http://ppa.launchpad.net/fengestad/stable/ubuntu

    Thanks in advance for your reply.

    Frolp

  5. I am trying to use my Japanese layout keyboard with FS-UAE in OSX, but I notice there is no key_actions for much of the keyboard_key mappings such as at, quote, asterisk, and many others. I wonder why they are not present? Is there anyway to get this working so something like
    keyboard_key_quote = key_action_at will work?

    • The key “actions” are keyboard events the Amiga sees. There is no key_action_at because the Amiga keyboard does not have an “at” key. If you explain in more detail exactly what you want to achieve, I can probably help. As far as I know, the keyboard mapping is “complete” (in the sense that any valid mapping can be configured).

  6. Hi all !!!
    How can i map the left and right sholders on xbox pad, with the 2 amiga mouse button ?? i used the string ” joypad_0_left_shoulder = action_mouse_0_left_button ” But don’t work !!!

    Please help !! Tnx !!

    • Try something like this instead: joystick_0_left_shoulder = action_joy_0_fire_button πŸ™‚

  7. It appears that the standard gamepad for FS-UAE is the Dualshock 3. Good that you decided on a commonly available product.

    I have tried the latest FS-UAE with Apidya, mapped my controller using Gamepad/Joystick setup in FS-UAE Launcher, and it still makes no sense to me at all:

    Why are the buttons not used for the various functions listed at http://fs-uae.net/keyboard-shortcuts?
    Apparently the only buttons used by the emulator are
    Menu = Toggle emulator menu
    Cross (or ‘South’) = Accept menu item
    Triangle (‘North’) = Amiga fire button

    You mentioned that Left Trigger (L2) toggles autofire. Well for me it doesn’t! πŸ™

    Pushing various buttons cause a joystick event to be sent. For instance, Circle makes Apidya bee fly DOWN.

    I checked C:\Users\marco75\Documents\FS-UAE\Controllers\ps_to_usb_convert_cable_12_4_1_0_windows.conf and everything is mapped as it should be to account for the characteristics of the adapter, so I’m at a loss.

    • Well, the Dualshock isn’t better supported than any another similar gamepad, but is is true I’ve used an “anynomous” version of the PS3 controller as illustration image since it is very symmetrical and has all the “supported” buttons. -But a Logitech gamepad will work just as well πŸ™‚

      Anyway, it does sound like the gamepad is set up incorrectly, somehow. Could you send ps_to_usb_convert_cable_12_4_1_0_windows.conf to frode@fs-uae.net, and also do this:
      – Open the joystick settings dialog in Windows where you can calibrate and/or test buttons.
      – Press the “Circle button” and let me know what button number lights up in the Windows joystick test dialog.

  8. Hi,
    Thanks for the nice emulator !!

    Is there any action for save screenshot , or bring F12 menu screen ?

    • Hi, action_screenshot was added in version 2.1.28 -I’ve now updated the input actions page. There is no action for the toggling the menu yet, but it’s on the todo list πŸ™‚ -Though it is possible to map a joystick/gamepad event to opening the menu by mapping a joystick event the menu_button name (you can also use the FS-UAE Launcher joystick configuration tool for this).

  9. Hi !!! is possible to configure a gamepad button with the key-combination F12 + W for Warp mode ?

    Thanks for your answer πŸ™‚

  10. Thank you for writing FS-UAE. I used to run games on WinUAE, but that was the most confusing emulator I have ever used, many years ago, and when I tried it again today I could not remember how to get anything to run.

    Wikipedia led me to FS-UAE, and it is a great improvement. As Alan Cooper, inventor of Visual Basic said: “No matter how many buttons and controls your user interface has, the less interface there is, the better.”

    I’m using a PS2 controller connected to USB through an adapter. The .conf file as demonstrated in your guide seems to work. I don’t understand the file, though.
    When it says button_*, going up to button_12, are those buttons on the Amiga or on my Dual Shock?

    How many buttons did the Amiga support? I have only ever seen joystick with one button.
    What about the CDTV?

    I was surprised to find that some games support the second button, like the Sega Master System. Elvira The Action Game is one. Apidya supposedly does too, the config menu has options for “game pad/joystick” and activate special with ‘auto’ ‘2nd button’ or ‘joystick’, though I could only get it to work with the spacebar.

    Here’s my question:

    How do I map Amiga fire button rapid fire to a different button on my Sony Dualshock than the Amiga fire button without rapid fire?

    How do I map “Emulator toggle F12 menu” to a button on my Sony Dualshock?

    I was thinking of having it go like this:

    Amiga Fire 1 -> Square
    Amiga Fire 2 -> Cross
    Amiga Fire 3 -> Circle
    Amiga Fire 1 Rapid (for shooters) -> Triangle
    Emulator toggle menu (super sexy effect by the way πŸ˜‰ -> L1
    Emulator warp -> R1

    Thanks for reading!

    • Hi, sorry for a really long without any reply, this was a bit tricky to answer, and it was forgotten for a while :-/ Anyway, I’ll try to answer as best I can.

      button_0, button_1, button_2, etc are buttons on your Dual Shock controller. Which of the buttons is button_0 depends on the gamepad and/or driver. Amiga joysticks existed mostly with one or two buttons, one actual button being the most common. I’m not sure, but I don’t think games support a third joystick button (unless they have CD32 gamepad support..)

      FS-UAE comes with a default setup for gamepads and joysticks, which supports several common gamepad models. Though your PS2 controller through adapter is probably not supported out of the box. But you can still take advantage of this by running the gamepad config tool from FS-UAE Launcher. With this tool/wizard, you identify the physical buttons/axes/hats on your controller, and a config file is automatically written. This default setup supports two Amiga joystick buttons, and will also automatically set up the gamepad correctly for CD32 gamepad emulation. There isn’t full support for the CDTV remote yet, but emulation still works when the CDTV game works with a regular Amiga joystick.

      It is not possible to configure a dedicated button as fire/autofire, but it is a good idea. What exists today is a possibility to toggle autofire on/off. If you run the Launcher gamepad config tool, the “left trigger” will toggle autofire.

      To map the open/close menu function, assign “menu” to a button, for example: button_7 = menu. But as before, if you use the config tool, this should be set up for you automatically: If you have mapped a menu button (which the PS2 controller lacks), that one will be used. But the combination start + select will also open/close the menu, for controllers without a dedicated menu button πŸ™‚

      Warp speed cannot be mapped directly to a joystick button in the controller config file. The reason for this is that the controll config files where not designed specifically for FS-UAE, but to describe how gamepad/joysticks should be mapped for emulating other systems’ controllers. FS-UAE has support for additional input mapping, and you can map warp speed to a button using this. There are several ways to achieve this actually, please see http://fs-uae.net/input-mapping for more information, and just ask if you get stuck. I’ll reply quicker the next time πŸ˜‰

      • This time it is my turn to be sorry — about my tardy reply to your tardy reply. I have been busy with my Karate and my book keeping course.

        Tonight I ran the launcher again, and there was an update to both the emulator and the launcher. (2.2.3) Since I had named its folder “\Amiga\FS-UAE-2.2.0-windows”, I decided to delete the old folder, but leave the FS-UAE folder in My Documents alone.

        Anyway, if some games or emulator functions require keyboard input, I can always use XPadder to map them to the joypad buttons. Will report back once I have downloaded the new version and have tried Apidya.

Leave a Reply to Smartimp Cancel reply

Your email address will not be published. Required fields are marked *