Changes

Angeldust

1,538 bytes added, 02:43, 15 May 2020
The following lines were added (+) and removed (-):
== Support and Troubleshooting ===== Poor game controller mapping ===Angeldust has very annoying game controller mappings.  Firefly does not feel that the end user should be able to create a custom controller mapping.Angeldust utilizes the SDL2 (Simple DirectMedia Layer) library for game controller support.  Many common game controllers are defined in the file ControllerMappings.sdlYou can find ControllerMappings.sdl in the root of your Angeldust installation.  Step 1 - Disable the game controller mapping that Angeldust uses.  To do this we need to identify the SDL2 specific GUID for the controller.  Once identified, search for the controller in ControllerMappings.sdl and modify the mapping parameters.  See: Identify your [[SDL2 Game Controller GUID]] Example:Our example controller is 03000000790000001100000010010000,Retrolink SNES ControllerSearching for 03000000790000001100000010010000 in ControllerMappings.sdl we find the following line: 03000000790000001100000010010000,Retrolink SNES Controller,a:b2,b:b1,back:b8,dpdown:+a1,dpleft:-a0,dpright:+a0,dpup:-a1,leftshoulder:b4,rightshoulder:b5,start:b9,x:b3,y:b0,platform:Linux,Now modify the line so it looks like this: 03000000790000001100000010010000,Retrolink SNES Controller,platform:Linux,Save and exit.  Now if you launch Angeldust you will notice that Angeldust has no controller mapping for this controller.Step 2 - Install and use Antimicro to create your own custom controller mapping. See: [[Game_Controller_Support_in_Linux#AntiMicro]]
Bureaucrat, administrator
14,711
edits