After trying the XML files here I still have not got the wired controller working.

It does stop auto moving which makes the app and keyboard usable but I would still love to get the xbox controller working with Kodi.

I didn't mention that Kodi did not come out on the the main screen of ES even after multiple times going through the simple process.

I also didn't mention I got Kodi working and then tried to get Kodi on the main ES screen and it didn't work and Kodi stopped working with the controller, I have no idea why but even when I un do the steps taken to move Kodi it still does not work with the controller.

I've thought about this a lot myself.

I have a 2nd generic Xbox 360 wireless adapter and have broken it down to just the chip inside (which is still MUCH larger than it needs to be - tons of blank board space all around). It's small enough that it should slip right into the official Raspberry Pi case with maybe even some room to spare since the Pi is tall where the 4x USB ports are, with a lot of wasted space behind it in the case.

I'm currently researching if I can hard-wire the 4x wires of the USB plug to the Pi's GPIO wires (which I don't think is possible), or how to most easily connect the wireless adapter inside the Pi's case so it looks nice and neat from the outside at least (if anybody has links to any tutorials I'm all ears!).

The problem I haven't figured out yet is how to select which player is which. I commonly have an issue where the Xbox wireless adapter steals player 1 even when it's plugged into the traditional Player 3 or Player 4 USB slot (this is when I plug in my 6-button Genesis controller for example, for some Streets of Rage action ;) and the only way to get that Genesis controller to be player 1 is to unplug the Xbox wireless adapter...which won't be possible if I hard wire it (unless I put in a switch or something). Might just snake a very short wire out of the case to a regular USB plug if it would look OK.

@bassman6805 Install the xpad driver from RetroPie-Setup -> Manage Packages -> Drivers and it will make the triggers act as buttons and you will be able to configure easily in ES.

No, I just meant I haven't tried to tackle setting it up yet. I will definitely open a new thread if I have issues. :) Thanks again!

It's still a step in the right direction. I think once I get my controller problems all sorted out, everything will be fine. What I'll probably just do is use your Joystick Selection tool and map everything out to just use the Xbox controller, and then the NES pads just for NES. I can still go back in and change that to the Xbox controller in the future easily enough, so I don't have to worry too much about using that "on-the-fly" method.

@kleesdad
Check out this thread and should work the same with the wired Xbox 360 controller as well:
https://retropie.org.uk/forum/topic/3580/wireless-xbox-360-controller-issues-in-kodi-16-1-on-retropie-4-0-1

never mind, i changed it to a Q then solved it :-)

Well, I tried that but I am not sure that it is a good idea. I "hacked" it so that only positive values are passed into the kernel API. This is what happened:

jstest /dev/input/js0 shows a range of 268 to 32768 (instead of -32k to +32k.) evtest /dev/input/event10 shows ranges from 128 to 255 (instead of 0 to 255)

So I don't get 0 still. Might be a problem.

ES can be correctly configured on device configuration with the analog triggers.
But still for example Crazy Taxi on Dreamcast can't be correctly played with analog triggers. In fact, patching the value range didn't have an effect at all. When you accelerate using right trigger you only reach like 15 km/h :)

I assume something like this: all the analog axis are signed 16 bit values ranging from -32k to +32k. The analog trigger is just 8 bit from 0 to 255. So I think that libretro also expects the 16 bit input range. But when the controller only delivers 8 bit you won't be able to trigger the full value range (only get values of a maximum of 255 instead of 32k).
I think they tried a fix here already:
https://github.com/libretro/beetle-psx-libretro/issues/40#issuecomment-252248501

I renamed the file.

I also went to RetroArch congifuration and put the digital->Left analog to P2 and P3 (silly me!!)

It worked like a dream.

Thanx @meleu

I am just starting a game. I tried 3 different games but no sound with any of them.....hey its working thanks, that worked

I got it working. I had a couple lines added in the config file that I did when I was trying to get my wiimote working. I just commented them out and it started working. I haven't tried to see if the wiimote still works after making the change. When I was trying to get it to work I changed and added quite a bit of stuff so hopefully it isn't needed.

I would not recommend using xboxdrv anymore. It used to be the go-to for 360 controllers but Xpad is now better. Here's some documentation on it:

https://github.com/retropie/retropie-setup/wiki/Setting-up-the-XBox360-controller

As for the version that you are currently running, there is no easy command to run to get this. Here is a Reddit post that mentions (in the comments) how to find out what version you have from Github which you'd then need to compare to what is on your screen.
As I understand it, the reason there is not an easy, one-line command is because Retropie is not one big program. Instead it is a ton of smaller programs all bound together. If you think about the many emulators that you can run on Retropie, each emulation program has its own version. This might be an oversimplification but it is how I understand it from the research I've done.

You can always follow this wiki update guide (same website as the top) to make sure you are on the latest but there is always the chance of messing up the current settings/controls you have set.

Best case scenario for you, you will see xpad on the list of drivers, install it, and things work well. But my experience is that if you change one thing, others will be modified accidentally.

So I updated my retropie to 4.something, uninstalled the xboxdrv and then installed the xpad and it seems to work fine. Kodi on the other hand is an absolute clusterfuck but looking at the thread you posted it seems it should be cleared up in the next version.

@ven9 Please open a new topic for your issue - and add more details about your system as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Heh----that's the danger with enjoying less-popular systems, not as much info is available in the world :-(

@edmaul69 said in ANSWERED: Button remapping (general & specific questions):

@polishzeus at least you chose a controller worthy of being "the one"

It was love at first sight 😀

@Rascas has posted that "Kodi 17 beta 7 available for RetroPie"
https://retropie.org.uk/forum/topic/6308/testing-kodi-17-beta-7-available-for-retropie

This has a kodi-peripheral-joystick addon that should help you get your controllers working in Kodi.