- The Controller Settings window doesn't react when I'm pressing a button or move a stick: Show
- If you use a wireless controller you should check following, you may want to refer to it's manual for that:
-if it is on, some LED should indicate that (some controller have a switch to turn it on/off, others get activated by pressing the guide button)
-if the batteries are sufficiently charged and put in correctly (if replaceable)
-if it could establish a connection to it's dongle/the wireless receiver (if you have a wireless Xbox360pad), on Xinput compatible controllers one lit up LED (should be the 1, as long you only have one controller connected) will indicate that
Now to more complex issues:
For the DualShock3 you need to install special drivers, as there are no default drivers under Windows. You have the choice between MotioninJoy which is large, uncomfortable and has ads but offers a lot of functions or SCP DS3 which is small and comfortable but offers less additional functionality.
What you also need to check if you actually have the right controller selected. Even if you have only one controller connected, you may have installed a program that creates virtual controllers for emulating controller input (eg: PPJoy,Vjoy) or you have a none controller device connected that poses itself out in some way as a controller although it isn't.
If you didn't save a controller layout yet, you can find the name of your controller in the title bar of the Controller Settings window. If it is not visible anymore you can also access the "Name" by opening the controller menu (the one on the left side) and clicking on "Properties...". Anything with "Virtual" indicates that this isn't a real controller, the only exception the MotioninJoy driver which is obviously for the DS3. Usually it's name should indicate the controller distinctively. If it isn't that obvious a Google search for the name may help to identify the device.
However if you have a wrong controller, you need to click on tab's in the upper area of the Xpadder main window (like with your web browser) to select another one. Check again the name before creating the layout.
If this is fixing your problem, you can hide the unwanted controllers in the Xpadder settings. Click on the button with the tool symbol in the upper right corner of the main window, select in the settings windows "Controllers", select the unwanted controller in the chart and click on the "Hide" button. After closing the settings window you should see that the tab of the unwanted controller became red. After closing Xpadder and restarting it (or your PC), you won't see it anymore.
- After closing the Controller Settings window my buttons are mixed up: Show
- There are two reason why this issue can occur and it only occurs with Xinput compatible controllers (Xbox360pads).
If you have a standard Xinput gamepad (two analog sticks, Dpad, 10 buttons, two triggers), you pretty sure have a file called Xinput1_3.dll and a X360CE.ini in the same folder as the Xpadder.exe. Close Xpadder and move these files into another folder. You can also move the Xpadder.exe together with the Xpadder.ini into a own folder (you should anyways use a own folder for Xpadder related files) but note that the "Start with Windows" option won't work anymore until you started Xpadder once from the new location. Please don't use the "Program Files" or the "Program Files (x86)" folders for Xpadder, as Xpadder cannot save the Xpadder.ini there without running with admin privileges.
If you have a non default Xbox360 controller like a fightpad of an arcade controller, then the reason is most likely that the button order of the DirectInput data differs form the Xinput data. The best solution for creating a properly working controller layout with such a controller is loading a preconfigured controller layout (that I have posted below), loading normally your controller image into it and then arranging everything according to their names and not to how the lit up when press the button. When you close Controller Settings window, everything should fit now.
Code: Select all
;--- Xpadder Controller Data --- DataType=Controller Version=2014.01.01 Name=XBOX 360 For Windows Button1Location=394,136 Button2Location=435,96 Button3Location=354,96 Button4Location=394,55 Button5Location=117,6 Button6Location=367,4 Button7Location=187,98 Button8Location=298,98 Button9Location=41,155 Button10Location=398,218 DPadUpLocation=164,153 DPadRightLocation=196,185 DPadDownLocation=164,217 DPadLeftLocation=132,185 Stick1UpLocation=91,62 Stick1RightLocation=123,94 Stick1DownLocation=91,126 Stick1LeftLocation=59,94 Stick2UpLocation=317,154 Stick2RightLocation=349,186 Stick2DownLocation=317,218 Stick2LeftLocation=285,186 TriggerLeftLocation=24,1 TriggerRightLocation=461,1 DPadUpAccess=POV DPadRightAccess=POV DPadDownAccess=POV DPadLeftAccess=POV Stick1XAccess=Axis X Stick1YAccess=Axis Y Stick2XAccess=Axis RX Stick2YAccess=Axis RY TriggerLeftAccess=Axis Z TriggerRightAccess=Axis Z - Button1Name=A Button2Name=B Button3Name=X Button4Name=Y Button5Name=LB Button6Name=RB Button7Name=Back Button8Name=Start Button9Name=left stick button Button10Name=right stick button DPadName=DPad DPadUpName=Up DPadRightName=Right DPadDownName=Down DPadLeftName=Left Stick1Name=Left Stick Stick2Name=Right Stick StickUpName=Up StickRightName=Right StickDownName=Down StickLeftName=Left TriggerLeftName=LT TriggerRightName=RT
- Xpadder doesn't detect any controller input anymore as soon as the Controller Settings window is closed: Show
- This occurs with Xinput compatible controller (Xbox360). You pretty sure have a file called Xinput1_3.dll in the same folder as the Xpadder.exe. Close Xpadder and move these files into another folder. You can also move the Xpadder.exe together with the Xpadder.ini into a own folder (you should anyways use a own folder for Xpadder related files) but note that the "Start with Windows" option won't work anymore until you started Xpadder once from the new location. Please don't use the "Program Files" or the "Program Files (x86)" folders for Xpadder, as Xpadder cannot save the Xpadder.ini there without running with admin privileges.