Is there some up to date instruction on how to make a joystick button make the latest beta and/or dev version of FS-UAE send a keyboard key to the game? Please, stepwise instructions. (see common/gamepad.ini for Amiga CD32 controller mapping).
Here is an example for a joystick with one stick and 4 buttons: Īmiga events are named left, right, up, 1 (fire), 2 (secondary fire) and 3 (tertirary fire). You should also create a section where you provide mapping for the menu navigation (if you want to navigate the menu). The ini file should contain a section with a mapping between controller events and amiga joystick events. If you created a universal configuration you do not have to add or sections.
If you have a controllers which looks nothing like a “standard” gamepad, if can be better to create a specific configuration file and map the Amiga joystick events directly. If you create a configuration file to support your controller, I would very much like a copy of this file to include with FS-UAE in future releases. Button events are simply button_x (where button_0 is the first button on the controller).Īlso, remember to check the log file to see whats going on when FS-UAE starts. You will probably get some hints to what’s wrong if it does not work. Hat events are referred to with hat_x_left, hat_x_right, hat_x_up and hat_x_down (x is hat number – the first hat is 0). Additional informationĪxes on your controller are identified as axis_x_neg/axis_x_pos where x is the zero-based index (the first axis is 0). – since this imports the common gamepad configuration file which maps the generic button names to Amiga joysticks. This line is important to include: include = common/gamepad Let’s say the program indicates that this is button 5! In the config file, the first button is numbered 0, so if the joystick test program calls the first button “1”, you must subtract one from the number, and you get: button_5 = start_button
Fusion sega emulator gamepad update#
What you must to is to check (with a joystick test application) what button number each physical button on your gamepad has, and update the configuration accordingly.Įxample: If you test a button labelled “start” on your controller, and you want to map this to the generic event “start_button”, you press “start” in a joystick tester program. Here is a complete example for this kind of configuration file: In this way, the same configuration can be shared with other emulators using the same configuration file format without having to create an explicit configuration for amiga, super nintendo, c64, and so on. a hat, two analog sticks, 4 buttons to the right, start/select and shoulder/trigger buttons), you can create a config which maps the controller events to generic event names (which again is automatically mapped against amiga input events). If you have a general-purpose gamepad with button layout more or less like PlayStation/Xbox controllers (e.g. This forum thread has some more information: Universal configuration file (recommended) Characters other than letters and numbers are also converted to underscore, and there is never more than one underscore between each word, and the name will not start nor end with underscore.Įxample: Controller (Xbox 360 Wireless Receiver For Windows) becomes controller_xbox_360_wireless_receiver_for_windows.ini The name of the ini file is the system name of the controller, converted to lowercase, with an underscore between each work. This tool will create configuration files for you and it is highly recommended.Ĭustom configurations can be placed in the directory: (My) Documents/FS-UAE/Controllers/
ini file per controller type.įS-UAE Launcher comes with a joystick / gamepad configuration tool (started from the settings dialog). The folder share/input/ contains the bundled configuration files. Controller configuration is specified in configuration files bundled with FS-UAE.