@michael40475 You could do the same way most people do here: burn a clean Retropie image into another SD Card, put into your RPi, put your games on it and enjoy.

@edmaul69

Actually since I am playing with lib cores then there is no mame tab (ex. Xmen: The Arcade) as all the controls are from retroarch. So my question should be "how can I keep user 1 from controlling user 4 and vice versa". The keys for user 1 is only binded to controller buttons and user 4 is just keyboard buttons but for some reason I can still control both players (P1 and P4) at the same time on the keyboard. Is it by default that keyboard P1 and joystick P1 are always binded to player 1, like it's hard-coded?

Edit:
I wonder if it has to do with user 4 not having a device index (set to N/A "Port #3")

Edit #2:
Okay nevermind it's solved now. I somehow unbinded the tab key so I couldn't get the mame menu to appear. So I deleted the "default.cfg" file from "/home/pi/RetroPie/roms/mame-libretro/mame2003/cfg" to reset it back to defaults.

Once I was able to bring up the mame tab (menu) then I was able to fix my issue by assigning keys to a keyboard button that I would never use (ex. F12). So for each player I made sure it was only binded to the specific controller button or keyboard button. Player 4 was called retropad 4 as well (keyboard only).

I have a pi zero that more or less works with a USB hub, but wont recognise the keyboard when I connect it to the hub, I havent tried an xbox controller, but i could try it I suppose.

@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 strongly recommend the Wii U Pro controller. For the price of a generic clone, I don't think there is a better option out there, especially considering the 80 hour(!) battery life.

@dankcushions said in Single place to map controllers:

yes, it does. at least, the libretro ones (lr-mame2003, for example).

It didn't seem to for me. I'll have to go back though to process and document what I do better (my memory is not what it once was...). But the way I remember it, I did the initial setup, when into Arcade, played Galaga, and neither the fire button nor the joystick worked. The Tankstick uses out-dated mappings for MAME (I guess they changed at some point). So I assumed that was the cause. I ended up remapping the Tankstick to just 'regular' letters on the keyboard, ran the controller setup, and still no-go. I had to go into the tab menu, and do a 'global' mapping there for it to work.

I've got some good areas to start looking.

@tropez You can't. It's the same on Xbox 360 controllers also. The lights indicating player number must be part of the proprietary drivers installed on each hardware system. The generic OS drivers used in Linux / RetroPie haven't included this function.

@red2blue try setting them to:

input_player1_joypad_index = 0 input_player2_joypad_index = 1

@darksavior you can use the bluetooth controllers and the ps3 driver at the same time. Uninstall the ps3 driver, add all the bluetooth devices you want. Then reinstall the ps3 driver. All devices work. If you want to add more bt devices, remove the ps3 driver again, add more devices, then reinstall the ps3 driver. I have been using all my bluetooth and ps3 driver together for a couple years now with no issues at all. Including my 8-bitdo fc30 pro.

@indvrkness Your post does not include all of the details from THIS POST which you are supposed to read and follow, and it doesn't look like you have read and followed the documentation that actually addresses using these controllers.

@Mr_Fix_It Thanks sooo much for this man I've been pulling my hair out for days with these bloody controllers. :)

@jonnykesh the “usb connector order” is useless since I am using a hub. Also as far as I see it, nothing in a system should ever depend on WHICH usb slot I insert a device...

Sorry I meant to remove one of these.

@caver01 i also should mention, the biggest reason why the intellivision is hard to get used to. Most games arent designed for you to tap up down left right. They are designed to have you "roll" around the disk from one position to another. Auto racing wont work at all tapping left and right. The whole top half of the disc determines the position of the steering wheel. So pressing up is straight and as you roll right or left it determines how far you are turning the steering wheel. This design really takes a lot of getting used to.

Im putting the gpio issue on hold for the moment as for some reason my adapter magically started working correctly. I plan to revisit it someday as it would reduce costs if I built one of these for someone else but for now its on hold. However my arduino came today and should make for some fun here soon.
alt text

I decided to turn my Pi upside down to find out why the heck PPSSPP wasn't recognizing my gamepad. Below is a little journal of my journey, describing what I had to do to fix things. Please, bear in mind that I'm a Linux newbie, and this is a tutorial of sorts intended to those just as new to it as me.

So, a little background information: I use a PS3 Logitech ChillStream (identified as a “PS3/USB Corded Gamepad”) with my RPi. This nice little gamepad works perfectly with everything EmulationStation throws at me... Except for ppsspp (not to be confused with lr-ppsspp: it DOES work with that core). It wasn't an in-emulator mapping problem, the damn thing didn't even recognize button pressing when I tried binding stuff.

I've read elsewhere that controller recognition was a hardcoded part of PPSSPP, and that you couldn't do much to make it see a controller it isn't seeing. But after two months of trying to find documentation and workarounds for this, I decided that I had enough. I would look under the hood and see how PPSSPP detected controllers myself.

By navigating to /opt/retropie/emulators/ppsspp/assets, I was pleasantly surprised to see that there is actually a list of recognized controllers inside gamecontrollerdb.txt, presented in a very readable way. For sure, my gamepad wasn't listed there, under either of its names. I had at last pinpointed the source of my problems.

Searching around the web, I found out that the file originates from a tool in SDL2 , a development library that provides low level access to audio, keyboard, mouse, joystick and graphics hardware via OpenGL. That tool is called controllermap. Luckily, if you originally set up your RPi using NOOBS to install a full Raspbian OS, you'll already have the required SDL2 library lying around (in my case, libsdl2-dev-2.0.6). If you don't have that library, just find and install it. The library won't come with controllermap, though, so you'll have to compile and install it yourself.

If you're a newbie like me, that will sound more complicated than it really is. I followed the guide found here, but in easier terms (remember to substitute the version number for the version of the SDL2 library you have):

Compile controllermap
1.1. wget https://www.libsdl.org/release/SDL2-2.0.6.tar.gz
1.2. tar -zxvf SDL2-2.0.6.tar.gz
1.3. cd SDL2-2.0.6/test
1.4. ./configure
1.5. make controllermap
1.6. mv controllermap ../..
1.7. cd ../.. Connect the gamepad. ./controllermap Does it output anything? If yes, great, you can keep going! For the next step, you'll have to drop out to CLI (that is, you can't be running a terminal in an x environment) ./controllermap 0 > out.txt You should see an illustration of a gamepad on the screen now. IF YOU DON'T, JUST PRESS ESC. Check the error log, you must be missing some image files. In my case, they were axis.bmp, button.bmp and controllermap.bmp. Just fetch those files in SDL2-2.0.6's /test/ folder and put them right next to controllermap, at /home/pi, and try again. Press your controller's equivalent of the highlighted buttons. If you want to skip a button, press the spacebar. The results will be saved to out.txt. You may now remove the SDL2 source and object files:
7.1. rm -r SDL2-2.0.6
7.2. rm SDL2-2.0.6.tar.gz

If you run into any problems, please refer to the guide linked above. Anyways, you can now check the output file in /home/pi and see that it has the same syntax as the PPSSPP's gamecontrollerdb.txt. Now all you have to do is copy the line in out.txt and paste it at the end of gamecontrollerdb.txt, and ppsspp should now see your controller! Bear in mind that you need to have root privileges to edit gamecontrollerdb.txt, so just sudo leafpad and browse for the file. You will probably need to rebind the controls in the emulator, but that is extremely straightforward!

Well hope this can be of use to someone who was just as lost as I was. For reference, the following is the output line from my controllermap. If you happen to use the same gamepad that I do, just go ahead and paste it in your gamecontrollerdb.txt and ignore everything else I said! =D

030000006d040000d1ca000011010000,PS3/USB Corded Gamepad,platform:Linux,a:b1,b:b2,x:b0,y:b3,back:b8,start:b9,leftstick:b10,rightstick:b11,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,leftx:a0,lefty:a1,rightx:a2,righty:a3,lefttrigger:b6,righttrigger:b7,

@krakenrelease Your first post is a link to your site with an affiliate link to buy a controller? I don't think so.

Link removed - I was going to ban/delete your account, but I'll give you a chance to explain why it wasn't spam in case I have somehow made a mistake.