[quote=100776]Of course. Take a look at this page, particularly the Config Slot Options section. Since I assume you are using the init.d script to initialize xboxdrv, the steps to use this option will be different than mine. But I’ll show you how I’m using it regardless.
I’m not at home, so I don’t have everything in front of me. However, in rc.local, I’m initializing xboxdrv kind of like this (I think the second ‘–id 0 –led 2′ can probably be removed):
xboxdrv --trigger-as-button --id 0 --led 2 --dpad-as-button --deadzone 4000 --silent --next-config --trigger-as-button --id 0 --led 2 --deadzone 4000 --silent &
--next-config seperating the different modes. One has
--dpad-as-button the second mode does not. So what that does is when I start up my pi, by default my dpads act as buttons, then if I hit the xbox button, the dpad acts as a hat switch or axis, hit it again, and it goes back to acting as buttons.
Idk if other controllers have a similar option, but if they don’t, this one option makes the xbox 360 controller, the best controller for the Pi IMO.
Thank you so much for your help! Here’s the issue I am running into. Now I did what you did, but in reverse. Where it defaults to normal dpad mapped to axis, then when I hit the xbox button it switches it to dpad-as-button. Now its working correctly, but the problem I am running into now is that even when the dpad is not a button, aka like how I had it before and the dpad is mapped back to the axis, it still reserves the first 4 buttons for the dpad, even though its not being used for that in that mode. Basically xbox btns 0, 1, 2, 3 are reserved for the dpad even though I have it mapped to the axis, which then pushes the rest of the buttons back to different numbers throwing off my mapping in the emulators….