XInputs?? mixing up buttons?

Post Reply
pastlife
Posts: 1
Joined: 30 Dec 2012, 21:27
Contact:

XInputs?? mixing up buttons?

Post by pastlife »

I have a Nyko AirFlo EX gamepad and I cant get it to work with anything.

I thought Xpadder would help but, not too sure now.

I found the image on the site and started to create a .xpaddercontroller file. I followed the walk through.

While in controller settings when I was mapping my keys, everything was detected and seemed properly calibrated. I got all 13 buttons laid out, d-pad, and both sticks.

MY problem is when I OK and close the settings, Some buttons are mixed up and some do not even detect on the main xpadder window, but they are working because they work in settings as well as control panel. It is funny because the inputs match on both windows while controller settings is open, its just when you close it and actually start to map the keys that they are mixed up and dont detect.

did I do something wrong or is this program a scam?

..Also the left stick is inverted L is R and R is L but not the right. This also is only correct in the settings window.


Seriously frustrated. I'm on a tight budget and probably shouldn't have bought a controller but I did, now im down $20 plus $10 for xpadder, and NOTHING is showing.. :cry:

I want my $10 back

Primal Fear
Xpadder Xpert
Posts: 2437
Joined: 09 Feb 2010, 16:41
Location: Germany
Contact:

Re: XInputs?? mixing up buttons?

Post by Primal Fear »

The Controller Settings window is using DirectInput, but the main window uses Xinput if it is available. I suppose that there are two problems with the Xinput signal of your controller, first it actually shouldn't have one (it's not Xinput compatible) and second it differs from the DirectInput signal in the button order and the X axis differs from the Xinput standard (which both shouldn't be the case on an Xinput compatible controller).

Check the folder where you have placed the Xpadder.exe. I think you have also placed there two files called xinput1_3.dll and x360ce.ini. These files are causing this problem. Either delete them or move them to another folder. Alternatively you can move the Xpadder.exe together with the Xpadder.ini (in the same folder) somewhere else into a own folder. But you need to close Xpadder completely in the notification area (also called system tray) if it should be running, before you can move the Xpadder.exe.

If you cannot find this xinput1_3.dll, check the Controller Properties in Xpadder by clicking on the tab of your controller (the small picture in the upper left of the main window).
You should see on the left side under "Xbox 360 compatible" "No" and in the lower right quarter a blank area. But if I'm right, you will see "Yes (ID1)" and such green bars like in the upper right quarter that are titled "XInput".
If this is the case, close the Controller Properties and open the Xpadder settings (tool symbol in the upper right of the main window), select "Options" on the left side and deactivate "Use Xinput (if installed) in the chapter "Running". Close the settings window and the problem should be fixed. If you should get yourself a Xinput compatible controller some day you need to activate this setting again, otherwise the triggers will share the same axis and Xpadder cannot control the rumble of the controller.

Post Reply

Return to “Problems detecting controller buttons, triggers or other”