Thinking again, once I have all 4 controllers configured and buttons mapped, I could modify the udev rules so that Joy1 and pad1 are both mapped as js0 while joy2 and pad2 are both mapped as js1. Any clue if that would work or create a conflict?

@ramchip I'm afraid I can't think of what it could be. Sorry!

Facing the same issue with "select" not working. Don't know what "drastic" is, so cannot comment on this.

There seems to be a "fix", but I am not sure whether this is part of 4.3 yet? Anyone has a more recent image and can try? Are their nightly or weekly builds for Retropie?

https://github.com/RetroPie/SDL-mirror/pull/4

@darkside1305 did you ever solve this issue? I've tried everything listed elsewhere to no resolve. I keep getting the KB unknown key for many of the buttons I want to map. Using a bluetooth xbox one S controller. In the drastic.cfg file I notice that anything listed as KB unknown key is changed to a zero. If I knew how the emulator worked with retroarch I might be able to figure out the numbers but they do not match up with the normal 1-14 buttons retroarch uses.

@danielmewhouse Sorry for that then. Unless there's some magic we can pull off with XBoxDRV, I imagine your easiest solution is to re-map your buttons for GBA or for this game in a way that makes those combos more accessible (i.e. keeping those buttons closer to one another, for instance).

@psyke83 You are awesome, thanks a lot :)

I'm sorry about that. Was trying to find the right spot to ask this question. Will check out OpenELEC.

I make them myself by hand, i have what i want now.
Now i only search to complete my UDEV file collection to make my RVGM compatible with most of the Joystick.
A friend will give me his file for NES30 Pro.

Similar problems. Two identical DragonRise USB Joystick, with same identical connection to usb encoder. In EmulationStation Player2 buttons respond correctly, also if just one config is written (identical joystick). When i start lr-mame2010 with - for example - street fighter i see that player1 controls are OK, player2 controls are ok BUT only 4 buttons of 8 is working. Tryig to make /boot/cmdline.txt mods. Trying also to reconfigure manually in retroarch. What can be? becoming crazy from a week !!! Thanks

@meleu I remember having myself a problem when trying to save the core config overrides for PS1 from the retroarch menu - and I've seen similar reports at https://retropie.org.uk/forum/topic/8527/psx-remaps-failing or https://retropie.org.uk/forum/topic/8527/psx-remaps-failing - that's why I thing that it might be a permission problem with saving the core specific options for the PS1 core.

@sonicsheppard also, if you want the sensitivity in the analogs to work better get something with a longer analog joystick. You can get a flightstick or use something like the mad catz xbox 360 gamestick:

0_1508592124231_16280532-3F05-4D38-9148-FB0828D4BEE9.jpeg

I can map the "parameter" keys 0-9 by hitting "Tab" to bring up the MAME menu, and the game will work fine until I close out and re-open it....then those settings aren't saved. Does anybody else have that problem?

Hi,
i solved in inverting RIGHT and LEFT Gpio cables ans calibrated under Emulstation.
Bye

have you tried the joystick selector tool?

I know this post is a couple months old, but I've just set up moonlight today on my Retro-Pie setup, using the same controller, and ran into a similar (if not the same) issue... But I managed to come up with a solution which (I think) will hopefully help others.

Long story short, I replaced the line matching the controller's ID (030000005e040000dd02000003020000) in /usr/share/moonlight/gamecontrollerdb.txt with this:

030000005e040000dd02000003020000,Microsoft X-Box One pad (Firmware 2015),platform:Linux,x:b2,a:b0,b:b1,y:b3,back:b8,guide:b10,start:b9,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,dpup:h0.1,leftshoulder:b4,lefttrigger:b6,rightshoulder:b5,righttrigger:b7,leftstick:b11,rightstick:b12,leftx:a0,lefty:a1,rightx:a2,righty:a3,

When I start moonlight it outputs an error about the config not being correct now, but it actually works (button mappings matched what Steam/games wanted, with no manual config necessary within steam or games).

I came up with this mapping by running the SDL "controllermap" utility. I compiled it using the steps laid out here

Now it's very possible I did something wrong, but when I ran controllermap, all I got was a blank screen (apparently you're supposed to see prompts asking you to assign/map buttons, but I never saw this). The first time I ran it I just mashed buttons until it exited. What this accomplished was it allowed me to get an idea of what order it took the inputs (based on the order it output them in the configuration string that was output when controllermap exited. Then, using this order as a reference, I ran controllermap again I pressed the buttons/joysticks in the order seen in the configuration string. This time controllermap output the string I included above. Then, as I said, I replaced the existing mapping in moonlight's config file. Then I rebooted (probably unnecessary) and launched moonlight again, and my controller was working.

Hey i had the same problem and i fixed it by

Going into a n64 game Pressing select plus x on my keyboard Go to quick menu (might be something by a similar name not at home rn to check Go to controls? Configure ur controls