Button Numbers are changed about xbox360wirelesschatpad HOT 19 CLOSED

I noticed this when testing with some games, however when trying to implement 
it; it wasn't true for all the games I have. In fact, different games had 
different button mappings, I think there were about 3 or 4 sets.

What's currently implemented supports FFXIV ARR and another game I play which 
is what I had intended to make the driver for. As there doesn't seem to be a 
one stop mapping solution, (unless my games are just THAT unique) switching the 
current button mapping to another would likely limit support on games it 
already works on.

That being said, this is an open source project and switching the button 
mapping would actually be very simple once you have Visual Studio C# Express 
installed. I'd encourage you to download a copy (free) and switch the button 
mapping for whatever your needs are.

Once you have VStudio Express installed and the SRC directory downloaded, open 
up the .sln file. From there open up Gamepad.cs. Lines 79 through 92 of 
Revision 20 is the button mapping for Non FFXIV compatibility mode. Simply 
change the numbers (1,2,3,4) to the new button numbers you'd like. Then just 
hit the play button to compile. The new executable in the Debug folder will be 
what you want to run.

Maybe you could make customizable button mappings in the future?

I've looked into it a couple of times, an it's definitely on the to-do list. 
The priority was mouse mode and multiple controller support which I just got 
out (r23). Until I can get to the customization, the code has been reorganized. 
You can find the button combinations in the Controller.cs file if you need to 
edit in the short term.

Just looking at the button number code so far, It may not be too difficult, but 
I might be wrong. I might just fiddle around with the code myself If I get the 
time.

Thanks for the new features in r23 this is a great update considering how I use 
this a lot.

It shouldn't be too hard. Lines 939 through 999 contain the mappings for the 
gamepad. There are two groups, one for the Trigger as Trigger mode and one for 
the Trigger as Button Mode. Simply change the assignment for the buttonMap your 
wanting to switch around. Good luck!

Thanks! It worked Perfectly!

I followed your installation instructions and was able to successfully get my 
xbox 360 wireless controller working with the Chatpad on a Windows 2008 R2 
machine.  It is really awesome.  Thanks for the great work.

I did encounter the same button issue explained above by [email protected]. 
 I am not too familiar with Visual Studio, so was curious if it was possible 
for  [email protected] to make available his fix for the button remapping?

Thanks again for all this great stuff.
BB

I could probably upload the fix if anyone else would like to use it.

A version with this fix plus the one with the inverted XY axis would be nice to 
get for all us XBOX 360 Controller users.  If you aren't ready to upload it, 
maybe you can send to me via email?

Sorry I meant inverted Y axis.

I'll upload the fix online as soon as I can. We would like to add customizable 
button mappings as a feature in an upcoming release. I'll upload the fix when I 
can.

I've uploaded the version of the application with the modified button mapping 
to the repository and a download link should be added to the main page soon.

Should be god to go, download Rev25, hopefully it helps.

Thank you guys.  Just seeing this. I will report back once I get it installed 
and tested out.

The new button mapping works great.  Now it is just like the standard XBOX 360 
controller for Windows. Thanks!!

The only remaining difference I have with the standard controller is the 
INVERTED ZY axis, reported previously in issue #27.  I am currently correcting 
this using XPADDER, but was curious if this was something that might be added 
like the buttons were.

Then of course the Zy and Z axes differences, which cannot be overcome since we 
are not using the native XInput driver for this solution.  I am trying to 
overcome that with XPADDER as well, but with limited success.

Anyways, thanks again for the button fix!

The Inverted RY Axis should be fixed as I remember modifying the code for that 
myself. I don't think the compiled code in the zip download was modified to 
have that updated in the last build. As for the Z axis, we need a Z and A Z 
rotation axis for both triggers to function due to how Xinput used the triggers 
and Z axis. If we can get it to work with Xinput, we would only require just 
the Z axis. It will take a lot of work to make it work with Xinput though

I've attatched the Main Executable with the Inverted RY axis fixed to this 
comment. The next Version should ship with the inverted RY axis fixed

Thanks! I confirmed this version does indeed fix for the inverted Ry axis on my 
xbox 360 wireless controller.