Having a similar issue myself still mate, cannot regardless of which combination I try get player 2 (or 1) to work in retroarch emulators. For some reason when I add in the prefix”player1″ or”player2″ retroarch then seems to ignore all input from these buttons and Joysticks, the only buttons that remain working are the hotkey enabled buttons. If i remove the player prefix from each line of code, for instance

input_b_btn = “12” (Works perfectly)
input_player1_b_btn = “12” (Stops working)
I’ve pasted my config file for the Xin-Mo in retroarch incase anyone spots a glaring error that I’ve missed.

Cheers

input_device = “Xin-Mo Xin-Mo Dual Arcade”
input_driver = “udev”
input_player1_joypad_index= “0”
input_player1_b_btn = “12”
input_player1_y_btn = “13”
input_player1_select_btn = “14”
input_player1_start_btn = “15”
input_player1_up_axis = “-2”
input_player1_down_axis = “-3”
input_player1_left_axis = “+3”
input_player1_right_axis = “+2”
input_player1_a_btn = “10”
input_player1_x_btn = “11”
input_player1_l_btn = “17”
input_player1_r_btn = “16”
#input_l2_axis = “”
#input_l3_axis = “”
#input_r3_axis = “”
#input_l_x_plus_axis = “”
#input_l_x_minus_axis = “”
#input_l_y_plus_axis = “”
#input_l_y_minus_axis = “”
#input_r_x_plus_axis = “”
#input_r_x_minus_axis = “”
#input_r_y_plus_axis =
#input_r_y_minus_axis = “”

input_enable_hotkey_btn = “14”
input_exit_emulator_btn = “15”
#input_shader_next_btn = “17”
#input_shader_prev_btn = “16”

input_player2_joypad_index = “0”
input_player2_b_btn = “1”
input_player2_y_btn = “0”
input_player2_select_btn = “4”
input_player2_start_btn = “9”
input_player2_up_axis = “+0”
input_player2_down_axis = “-1”
input_player2_left_axis = “-0”
input_player2_right_axis = “+1”
input_player2_a_btn = “2”
input_player2_x_btn = “3”
input_player2_l_btn = “7”
input_player2_r_btn = “6”

The Mame Rom set that is most compatible with Retropie is 0.37b5. MAME is very complex, so certain rom sets work with certain emulators. As the current time, you’re best bet is to find a the above rom set. If you try to individually piece a collection together, you’ll likely get compatibility issues and it wont work.

it used to download/update all binaries, but this was a problem since some binaries required configuration updates which it didn’t do – this was causing problems.

You can update individual items from menu 5, or use the menu 1 to do a complete binary install which will update the system (backup any custom configs etc first).

We may add it back again in the future, but in a way that doesn’t cause the problems as before.

You could try this thread for reference:

Playstation Dual usb

Since this is in “Ideas For Further Enhancements” section of the forums, what about adding this –gfx switch in the video options (press x or m) that way they can be saved per individual roms?

Just out of curiosity guys, are any of you experiencing any problems setting up the second player configuration in the controller file for the Xin Mo Dual ? I have searched high and low for the answer and tried everything I can think of and just cannot get it to work.

Cheers

Thats Awesome!

Somebody should definitely set up a “working n64 roms” database with the specific video plugin + individual changes to the config.

As more people try this emulator those setting could then maybe be setup as a default config for future releases.

Win!

Just a shower thought.

I just updated with instruction listed as well and all is working with my xim mo dual. Awesome job guys.

Having the exact same issue with a Xin-Mo Dual USB controller, my Pi knowledge is certainly lacking a little but this seems quite manageable, if it isn’t too much trouble and seeing only as it was mentioned would it be too much hassle for you to post the updated compiled Kernel feederchain?

Cheers

I am running the Xin-Mo Dual Arcade and having the same issue with the joysticks. The buttons seem to work fine for payer 1 and player 2 respectively but my joysticks player 1 and 2 seem to work as the same joystick. Strange.

Here is my configuration of the two joysticks in retroarch.cnf. Should the index be 0 for both? Also should the axis be the same for both?

input_player1_joypad_index = “0”
input_player1_a_btn = “1”
input_player1_b_btn = “0”
input_player1_y_btn = “2”
input_player1_x_btn = “3”
input_player1_start_btn = “4”
input_player1_select_btn = “5”
input_player1_up_axis = “-1”
input_player1_down_axis = “+1”
input_player1_left_axis = “-0”
input_player1_right_axis = “+0″

input_player2_joypad_index =”0”
input_player2_a_btn = “11”
input_player2_b_btn = “10”
input_player2_y_btn = “12”
input_player2_x_btn = “13”
input_player2_start_btn = “4”
input_player2_select_btn = “5”
input_player2_up_axis = “-1”
input_player2_down_axis = “+1”
input_player2_left_axis = “-0”
input_player2_right_axis = “+0”

input_enable_hotkey_btn = “4”
input_exit_emulator_btn = “5”

I tried the patch above for Pi-FBA and am testing on SNES emulator.

yes.

1. because you might want to change something / re-try a build etc – see ./retropie_packages.sh – you can run individual steps etc. I may introduce a module to clean this up though, or just clean it up after using the setup gui.

Hi all,

This looks like something I was planning on doing on my pi2.

Initially I was trying to dual boot Openelec and Raspbian.

From what I read, should’ve been a case of dropping openelec in.

I grabbed the latest noobs, however the only option was Raspbian. So I’m trying to download (slow connection) an older version of noobs and overwrite with the new Raspbian and Openelec.

I also want retropie running. However, if I install on top of Raspbian, will I lose my Raspbian environment/desktop?

Thanks

I just did it with Openelec and Raspbian (Retropie) installed on a 32Gb SD Card. I followed this tutorial : https://rromo12.wordpress.com/2014/09/10/raspberry-pi-raspbmcretropie-dualboot/

If you want to use it with Openelec you have to delete all the “sudo” commands in Retropie.sh because Openelec has already root permissions:

#!/bin/sh
sudo sed -i 's/7/5/g' /media/RECOVERY/autoboot.txt
sudo reboot

to

#!/bin/sh
sed -i 's/7/5/g' /media/RECOVERY/autoboot.txt
reboot

As stated in the comment if you do a clean install with Noobs, you will have to change the mounted partitions on reboot (or you can get stuck) as they changed boot order in the latest version:

1. “Retropie.sh: changed ‘s/5/7/g’ to ‘s/7/5/g’
2. Raspbmc.sh: changed ‘s/7/5/g’ to ‘s/5/7/g’

It’s absolutely amazing as it will reboot to the correct partition (and which is also great because you will then be “stuck” to the same OS when you normally reboot (good for my girfriend).

it would wipe everything if overwriting the image.

you can either backup your data and do that and restore, or optionally update the script and then choose to install the binaries from option 1.

you can also update individual emulators by installing from menu 5 as needed.

This is taken from my own PERSONAL installation guide that i have been creating as I build my retro station. Please excuse any spelling mistakes and such, I spun this off while working on the pi, but the steps are exactly the process I used while doing individual emulator mapping.

ALTERING EMULATOR SPECIFIC CONTROLS

Assuming you have 4 controllers that are the same… (if not scroll down)

From terminal, type”

cd /opt/retropie/emulators/retroarch/configs

dir (or ls -1)

Now select a controller to look at for reference for button mapping

sudo nano “controller cfg file to reference/alter”

find specific buttons to change and write down the current configuration. For example, I want to change the NES a and b button mapping by swapping the function of each. MadCatzXbox360Controller.cfg states:

input_a_btn = “0”
input_b_btn = “1”

So now I exit without changing anything (ctrl X, n, enter)

Now type:

cd /opt/retropie/configs/nes
sudo nano retroarch.cfg

Now in nano, scroll to the bottom and type:

input_player1_a_btn = “1”
input_player2_a_btn = “1”
input_player3_a_btn = “1”
input_player4_a_btn = “1”
input_player1_b_btn = “0”
input_player2_b_btn = “0”
input_player3_b_btn = “0”
input_player4_b_btn = “0”

Now press ctrl x to exit, y to save, and enter.

IF YOU HAVE DIFFERENT CONTROLLERS (not all the same type)

Enter the emulator you want to alter mapping for. Find the USB that controls the 1st, 2nd, 3rd, and 4th player controllers. Write down the type of controller is for each # player. Exit emulation and emulationstation.

Now in terminal follow the above instructions but repeat the first part for finding how the controller is configured (cd /opt/retropie/emulators/retroarch/configs and sudo nano config file for the controllers that need to be changed) for the controller type for each player. Write down the controls that you want to change under each controller type/player.

Continue to the emulator retroach.cfg file (IE: cd /opt/retropie/configs/nes then
sudo nano retroarch.cfg) and alter the buttons by player# and controller type for remapping (using the configurations from the controller config files). for example, if player 1 is an xbox controller, player one should be reconfigured using mapping for xbox controllers, playstation player # to playstation mapping, etc..

NOTE: You may want to mark what ports they are plugged into by painting a number on the port and the controller. As long as the controllers are in the SAME ports when you load the pi, they should be correctly mapped each time you start emulation.

I know this is a very old thread but I’m having similar issues with FBA and a Dualshock 4.

From what I can gather the changelog notes below mean that the d-pad should always work with PiFBA. This is seperate from the joystick axis setup in the fba2x.cfg file.

Is it possible to simply disable the JA_LR and JA_UD axis variables in the fba2x.cfg file? I’ve tried commenting them out but it seems if they aren’t there it defaults to 0/1.

Editing themes is not that complicated actually. There 2 main XML files to edit, the only time you need to edit more are for each individual system, so assuming that each system theme will look identical with maybe a different background image, there are basically 2 XML files to edit, then you just place them in the system folder and boom.

I’m not sure you want to waste your time on this to be honest, unless you plan on fully re-arranging the layout of the theme, then this will be no more useful than opening an XML file and editing a color value.

The problem really for theming is opposite of what you want, which is more variables. The more we had access to altering the better it would be for customizing our overall looks.

I might be wrong but I think it’s normal for Emulation Station to prompt you to configure the controller on start-up if it’s not been used with it before, regardless of whether it’s set up in the Retroarch config file or not. I’d tried setting up the PS4 pad myself and completed the “Register Retroarch Controller” setup from the Retropie config script but still had to set it up in ES too.

I’m also getting the problem with the pad not responding in games. I’ve tried with SNES and Mega Drive/Genesis, though I doubt it actually makes a difference trying in different emulators. I also tried two different PS4 controllers, both Dualshock 4. Neither gets any response once ES has started the emulation.

I’ll try setting up FBA or something to see if that works.

edit: removed the quote of the previous post as the text was really big for some reason and didn’t read easily.

Yes I have tried that in the past before, not sure what that does and since it did not fix my two controller issue, i restored it to original.

At this point, I have tried several different versions of the RetroPie software, two different types of BT dongles (BT211 and BT400) paired fine individually but cannot get both controllers online at the same time. I am out of ideas..

I had the same issue when I started out. I think I just had to create a configuration file for the Dualshock 4 and put it in the right folder.

UPDATE: Don’t bother with the attached file, just check out this thread:

Config file for DualShock 4 / PS4 controller

I’ve been using a pair of the SNES styled iBuffallo controllers for a few weeks. I can’t recommend them though. The face buttons work fine, as do the triggers, though the d-pad registers lots of false inputs. When left idle it’ll occasionally send false up, left and rights. This happens during play too, and while it’s not a huge problem in many games, in some (Street Fighter style games, for example,) it’s significant.

I’ve had better luck with the Mad Catz Street Fighter X Tekken Fightpad for PS3. It set up fine and works great. The build quality is great for the price, though the face buttons feel a little cheap, and it’s very good for most games. Had theRPi2 Model B not just arrived and made good N64 emulation possible I’d just use these.

I’m currently trying to get the PS4’s Dualshock 4 working and while it works fine in ES, as soon as I go into a game it loses all functionality, as does the keyboard. I can only exit out by disconnecting the controller and pressing the Esc key on the keyboard. I’m not sure why this is happening, but the pad is wired on an extremely long cable so maybe it’s a power issue. I have no technical knowledge whatsoever though so that’s just a guess.

i have the exact same problem.
some people wrote, that when you get the controllers to work individually all you have to do then is to “parse the second controller”. i dont really get what it means. i am confused because various tutorials about this matter tell you to edit config files, that are either not there at all or are named differently or are at a different place. it seems the tutorials all relate to certain versions of retropie and obviously there were changes made to the location and naming of config files.

Raspberry Pi: Connecting multiple PS3 controllers via bluetooth

i tried the above tutorial among others and i dont get where i should put the config lines for the second controller. what i did find was the declaration of the controllers index. i uncommented these lines in, without success..

id like to hear someone explaining it on the most current version. that would be seriously cool!

im so amazed by the speed of the rpi2 and the ability to emulate all those games from the past. thank you for that neat software project! :)

Hi Buzz.

Thanks for all the effort. Really apreciated :-)

You got some documentation on how to setup a cross compile environment for retropie ?

I never cross compiled something like retropie. I did for individual binaries but never for such a project as retropie. I can only assume the building of a new image is not as simple as it would be when building debian live images.

@moothead2

This probably sounds silly but have you pressed the PlayStation button before pressing the buttons on the Dualshock 4? This usually works for me.