@sleve_mcdichael Of course... I used xboxdrv so many times for gamepad-mouse-keyboard mapping, but I didn't know it could mimic xbox pad. Thanks.

Yes, I think the doc page is wrong and the buttons are switched on the libretro port.

@mitu awesome thank you for your responses.

Hey @mitu.

Just what I was after. jstest is exactly what I wanted. As yet I haven't done anything with evtest or sdl2-jstest, but I've taken notes and they are now in the tool box for continued retro-pie adventures.

Again. Thanks very much for your help.

Rob

@BAZLOCO thanks. I did this years ago and the notepad file must have been overwritten. I will run the test then later the file w mappings. Appreciate it. Once done I will take a stab at altering intellivision. Much appreciated.

@skankieflank said in Can we use Pad2Key?:

Pad2key is really simple to use and great for mapping games which were for keyboard use only to joypad.

Sure, but it seems something specific to Batocera and not a standalone app than one can take and integrate into an existing setup.

Right now, the documentation here https://retropie.org.uk/docs/8Bitdo-Controller/ gives advice which seems kind of wrong.
First of all, you shouldn't be using Bluetooth at all. It has too much input lag for gaming. Maybe if all you want to play is visual novels or watch movies with Kodi then Bluetooth is fine but for anything video game related that has actual game in it which isn't just a video, you shouldn't be using Bluetooth at all AFAIK. Too much input lag. Use a wire.
Second, it suggests that you can go in and edit the RetroArch controller configuration files. Well, maybe. Until the next time you plug a controller in and then RetroPie's EmulationStation will overwrite those files with whatever it thinks your controller mapping should be, completely undoing all your hard work.
There's got to be a better way to handle this whole aspect of RetroPie from a design perspective.

@mitu My apologies for not reading through that read first post. Nevertheless the problem was exactly what you said. I made sure that everything on the back of those little controller boards was plugged in exactly the same on both sides now the only problem is the joystick orientation has to be flipped around because it is reading backwards should be good. Thank you for your help I appreciate it.

Dragonise is a generic USB controller name used in a great deal of encoders, so there's no single mapping that will work with them. If you configure your controller in EmulationStation, then the mapping you chose there should be saved in dapinput.ini automatically.

Please add some more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first and post your dapinput.ini file.

Just a heads-up: removing xpad might break the controller in emulationstation and elsewhere. In my case, the triggers weren't being properly parsed, and as such they couldn't be properly mapped. Hence, I wasn't able to simply remove said driver. That being said, the original solution by @tuxophil DOES work properly, and as such I would still recommend it. Keep in mind, though, that the command at step "8" requires a declaration about which controller you want to map. As such, a correct command might be ./controllermap 0 >> ~/my360.txt, if your X360 gamepad is in slot 0. Running just ./controllermap will show which controllers are connected, so use your gamepad's slot from that list.

@mginster my question is about mapping controls. I have player 1(working fine) and player 2 ( not mapped correctly). How do you map ultimarc joysticks and buttons for player 2? Any help or ideas would be useful. Thank you

Glad you got it sorted out and thanks for adding the solution to the topic.

Hold SELECT + DPAD DOWN = Switch the positions of the A-B and X-Y keys

It would be nice if 8BitDo would include this info in the Modkit manual, they are mentioning _ SELECT + DPAD DOWN_ as a way to send the Home button only when the modkit is paired in Switch mode.

I'll mark this topic as solved.

@theawfulone in-game, open the RGUI (RetroArch Graphical User Interface) with default Select + X ("north" face button). From there, navigate to quick menu (this should be where you start already) then to controls >> port 1 controls. Set up the buttons how you like, and then go back to the controls menu (one level up from port {n} controls) and "save core remap file."

Do this once each for GB and GBA. Saving it as a "core" remap file will apply the changes to every title on that system. You can also set overrides that will apply on a per-game basis (and override the core setting) by saving a "game remap file" instead. "Content directory remap" isn't very useful, in most situations, since the configs are already separated out by system anyway so they will already only apply to a single content directory, even using the core remap.

This means that even if you use the same lr-gambatte emulator core for GB and GBC games, you still have to remap them separately (unless, you put them all in the GB folder, which you can do with a simple edit to your custom es_systems.cfg file.

@sleve_mcdichael Thanks! I will try this out.

Thank you everyone for your feedback and suggestions! I think I figured out what is causing the conflicts I am experiencing, for which I'll reference the following screenshot of the mame input configuration for sf2.zip:

sf2-210802-174734.png

My rebindings are attempting to "relocate" buttons, assigning buttons 1->2, 2->3, 3->6, etc... (as noted before). The end result is that only the RetroPad bindings changed, not the keyboard key bindings. The OR clause in the mame mappings thus maps one key/button to two events and that ends up breaking things!

@dankcushions said in Unable to configure per-ROM input override for MAME:

point of order, but they do, but it relies on you using the correct physical location or your buttons:

B A R
Y X L

I had not considered this, but this seems very sensible given mame's default inputs (key or retropad event). I had have wired things using the IPAC switch numbers, which won't be hard to change.

1 2 3
4 5 6

EDIT
Here is a post descripting this same problem, which is due to the "simultaneous" core input setting in retroarch:

https://retropie.org.uk/forum/topic/29976/mame-button-mapping-conflicting-with-retroarch-button-mapping