Game Profile for the Xbox 360 Controller: Game Controller for the Xbox 360 Controller: (XBOX360ForWindows).xpaddercontroller Bitmap image file for the Xbox 360 controller: If you have any questions, feel free to ask me.
ONLY Xpadder (2012 versions) and JoyToKey (v5+) and Autohotkey scripts are supported options for keymapper functionality. Will not work with JoyToKey v3 or below.Even though Keymapper supports 16 controllers, this only for Direct Input and not XInput since XInput is limited to 4 controllers. (Xinput is typically used in software that natively supports the 360 controller.)
xpadder controller images only
KeymappersXpadderXpadder costs $10 and can be downloaded from xpadder.com. This is the recommended keymapper of choice. To set it up, run it once you have downloaded it. Make note of where you have installed it to since you will need to know that when you use it with RocketLauncher. Once you have installed it, you will need to make a layout for your controller.Images to replace the pink background can be found at xpadder.com/gcdb. An image of your controller will be useful for making your profiles. To grab an image from the xpadder database right click on the image you want and choose copy image. You can then use the paste button in xpadder. Now you will need to add your analog sticks, dpad, buttons and triggers using the on screen instructions Once you've finished adding all the controls for your controller you will need to save your layout. I suggest saving it as the same name as your controller (the default name).You will now need to create a profile. Profiles are what RocketLauncher uses to tell xpadder how to map your controller. You can start by making a profile by clicking on the text page button first and then choosing New.The next step is to map your buttons to a keyboard key. This is simple and easy to do. You will need to click on one of the white boxes that represent your buttons on your controller. This will open a virtual keyboard. Choose your key. When you are finished mapping your buttons you can now save your profile. To use with RocketLauncher you will need to name it and place it in the correct folder path as described in the profiles section below.AutoHotKeyAutoHotKey is the only free keymapper that is supported by RocketLauncher. The downside to using ahk as your keymapper is that RocketLauncher only has basic support for it and it does not support Front End or RocketLauncher Menu profiles or any other kind of in game remapping done by Pause. There is no download required to use it, but if you wish to test your key maps without starting RocketLauncher you can download autohotkey from autohotkey.com. To create an ahk profile, you will first need to create an ahk file. You can do this by creating a new Text Document and renaming the file extension from .txt to .ahk. Now open your new ahk file with your favorite text editor and start adding your remaps. You can find more info about how to remap via ahk here. A list of support ahk keys can be found here. Information on how to remap keys and buttons can be found here and more information on how to remap joysticks and controllers can be found here. Save the ahk file with the remaps as one of the profile names specified in the profile section below. As an example, let's say you want to remap a to b and c to d using ahk for the rom "Mario" for Mame. You would create a "Mario.ahk" in "Keymapper Profiles\Mame\" and in it you would find the following remaps:Code:
Front EndThe Front End profile is only used when you exit your game and return to your front end. The name for your Front End Profile is set by the key "Keymapper_FrontEnd_Profile_Name." If you want to use this profile you will need to create it like you would a system profile. If you have RocketLauncher v3.0.1.1 or later you will need to set the value for the key Keymapper_FrontEnd_Profile to match your keymapper of choice; valid options are xpadder, joytokey, ahk, and false (default value that turns front end profile loading off). The default front end name is HyperSpin and this name will be used in the below examples. This profile is supported for AHK, but you must set Keymapper_AHK_Enabled to equal external.Xpadder
*Keymapper_AHK_Enabled = externalFile:Keymapper profile ahk front RocketLauncher.jpg.1379464584168.jpgBlankThe blank profile is supposed to be an empty profile. It has no remappings in it at all. This is meant as a place filler for controllers that have no remaps made. Example, if you have two different types of controllers connected, and the controller you don't want to use occupies the 2nd player number (id 2) in Pause, but in Xpadder it might occupy the first tab. The controller that is first player (id 1) in Pause might occupy the second tab in xpadder. Due to the way xpadder handles the profiles passed to it in the command line, this blank profile is needed as a filler for the unwanted controllers that show up in the tabs before the preferred controller. Xpadder loads profiles through the command line in the order of the tabs displayed, not the order used by Pause (Direct Input order), or the order the controllers were connected in. There should only be one blank profile for Xpadder. This profile is always loaded last if no other profile is found, anytime RocketLauncher is loading your profiles that you use for playing your games, returning you to your front end, or opening a RocketLauncher menu. To make one, you need to name it "blank" and place it in the same directory as the default profile. This profile is only supported and required by xpadder.Xpadder
Custom NamesCustom Names are useful for grouping your controllers or giving them a shorter name. The limitation to this feature is that you can have only one custom joystick name assigned to a default windows joystick name. Also if you use both the default name and custom name in naming your profiles or for your Preferred Controllers list the default name will always be used since it is inherently more specific. Some examples of it being used are to reduce long controller names to something simple like "Controller (Xbox 360 Wireless Receiver for Windows)" to just "x360." or for grouping your controllers like "Controller (Xbox 360 Wireless Receiver for Windows)" to "xbox 360 controller" and "Controller (Afterglow Gamepad for Xbox 360)" to "xbox 360 controller." You will need to enable this feature first by setting the" Custom_Joy_Names_Enabled = true" and defining your custom joystick names list in the "Custom_Joy_Names" key.Custom_Joy_Names_Enabled = trueCustom_Joy_Names = Controller (Xbox 360 Wireless Receiver for Windows)xbox 360 controller\Controller (Afterglow Gamepad for Xbox 360)xbox 360 controller\Default Windows NameCustom NameKeymapper Ini SettingsSettings\RocketLauncher.ini[Settings]
No configurationUsually, though, you won't have to configure anything, unless you have a really, really obscure controller and/or really, really obscure game. You can simply google e.g. "xpadder mass effect" or "xpadder bioshock 2" or "xpadder 360 controller" to find controller images, controller config files, and game config files already carefully created by somebody else to work with your controller and the default key/mouse settings for your game.
What I wanna do is: When I start an emulator with gameex, xpadder shall load the specific profile for each controller.. I know that this is somehow possible with a command line or batch file.. but I don't know s*** about command lines or batch files, so I don't know how to do that so, can someone help me? It should be something like: When ZSNES starts, xpadder should load: windowsxbox, psxp1, madcatzblackp1, madcatzredp2, ps3bluep1, ps3blackp2And the last question is: What if I don't have connected all Gamepads? For example: I Connect just the Xbox pad and the two PS3 Pads, will xpadder then load the correct configs for the ps3 controllers?I hope you guys can help me 2ff7e9595c
Comments