From retroarch, write the config to file. Retroarch create a .cfg file. Copy and Rename this file to retroarch.cfg inside the directory of emulator, eg: /opt/retropie/configs/psx/

Now it should work!

Hi all,

I’ve read quite a few posts on GnGeo config and watched floob’s video but no matter what I do, my Xbox 360 controller just will not work.

I’m using an ‘eBay special’ wireless receiver, which works perfectly fine up until now. The only thing that I can see that seems to be odd about it, is that when I look in /dev/input I see js4 and js5. Either way, it should be fine.

So my gngeorc conf file, for example the coin button, should be COIN=J4B8 which according to jtest is my select button. But this just will not work. I know the config file is being read as I’ve enabled showfps and some effect successfully.

Can anyone shed any light on this? Thanks

I am using a mayflash n64 adapter with retropie 3.0 beta 4 for raspberry pi 2:

http://www.amazon.com/May-Flash-Controller-Adapter-Nintendo-64/dp/B002B9FIUU

I have edited
/opt/retropie/configs/n64/retroarch.cfg
in order to create specific controls for the mupen64plus emulator (including hotlinks)

When I start Ocarina of Time in mupen64plus, all of my controls work, but when I push the joystick through it’s full range, link walks instead running. I have seen other threads where advice is given to edit
/opt/retropie/configs/n64/InputAutoCfg.ini

however, this file already contains a controller called [Linux: USB GamePad] and changing the AnalogPeak and AnalogDeadzone for my controller has no effect on the game (I don’t think the file is being used…). I don’t want auto controls anyway, I want to use the controls I have outlined in /opt/retropie/configs/n64/retroarch.cfg

I’ve also tried editing the ‘AnalogPeak’ value in /opt/retropie/configs/n64/mupen64plus.cfg but that hasn’t changed anything either.

Is there a way to adjust the joystick range for my mayflash n64 adapter? How can I make link run?

As a side note, I had this same problem with project64 on my pc, but in the controls window, there is an option to uncheck “Real N64 Range” and that fixed the problem entirely.

I have been at this for hours. Any help would be greatly appreciated.

hmm, what if you try this content instead
http://pastebin.com/raw.php?i=kmLCRvR8

basically delete these lines
input_r_x_plus_btn = “9”
input_r_y_plus_btn = “9”
input_r_y_minus_btn = “9”

I’m assuming you havent tweaked any of your retroarch.cfg files. If you have, please post those as well.

Yeah- lr-mame4all doesn’t have a tab menu- it utilises retroarch configs which can be modified from the rgui or by manually editing the retroarch.cfg file for its respective emulator. If you’re running retropie 3 beta 4 when you configure your controls in emulation station it will automagically configure your controls for retroarch as well.

I think I have this resolved. I formatted the SDcard and re-imaged RetroPie 3 b4. I ran through all the normal configurations and then set up controllers. They are now mapped correctly.

Though my 2nd question is still present. If I have a sega 6 button like controller + 2 bumbers, do I need to manually configure the 2 not listed if the controller script?

Thanks,
DFL

Hello!

I’m new to Retropie and this is my first attempt to use emulation on my Raspberry Pi.
With my setup I’m using a XBox One Controller.
The controller works fine in RetroPie menu, but in the emulated games the left/right/up/down buttons won’t work.

The controller is detected and the configuration guide works.

I’ve think there is a bug – and i found a workaround that works for me.

The problem is in the file /retropie/configs/all/retroarch-joypads/Microsoft_X-Box_One_pad.cfg

The original (not working file) looks like this:

input_device = "Microsoft X-Box One pad"
input_driver = "udev"
input_up = "h0up"
input_right = "h0right"
input_state_slot_increase = "h0right"
input_down = "h0down"
input_left = "h0left"
input_state_slot_decrease = "h0left"
input_a_btn = "0"
input_b_btn = "1"
input_reset_btn = "1"
input_x_btn = "2"
input_menu_toggle_btn = "2"
input_y_btn = "3"
input_l_axis = "+2"
input_load_state_axis = "+2"
input_r_axis = "-5"
input_save_state_axis = "-5"
input_l2_btn = "4"
input_r2_btn = "5"
input_l3_btn = "9"
input_r3_btn = "10"
input_start_btn = "6"
input_exit_emulator_btn = "6"
input_select_btn = "7"
input_enable_hotkey_btn = "7"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+3"
input_r_x_minus_axis = "-3"
input_r_y_plus_axis = "+4"
input_r_y_minus_axis = "-4"

The file working (manually edited) looks like this:

input_device = "Microsoft X-Box One pad"
input_driver = "udev"
input_up_btn = "h0up"
input_right_btn = "h0right"
input_state_slot_increase_btn = "h0right"
input_down_btn = "h0down"
input_left_btn = "h0left"
input_state_slot_decrease_btn = "h0left"
input_a_btn = "0"
input_b_btn = "1"
input_reset_btn = "1"
input_x_btn = "2"
input_menu_toggle_btn = "2"
input_y_btn = "3"
input_l_axis = "+2"
input_load_state_axis = "+2"
input_r_axis = "-5"
input_save_state_axis = "-5"
input_l2_btn = "4"
input_r2_btn = "5"
input_l3_btn = "9"
input_r3_btn = "10"
input_start_btn = "6"
input_exit_emulator_btn = "6"
input_select_btn = "7"
input_enable_hotkey_btn = "7"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+3"
input_r_x_minus_axis = "-3"
input_r_y_plus_axis = "+4"
input_r_y_minus_axis = "-4"

Note that the diffrence between the files are missing ‘_btn’ suffix

I hope this post can help other users and also notify the creator of retropie-software. Thanks!

Thats a very broad question. There are different romsets for different emualtors:
https://github.com/RetroPie/RetroPie-Setup/wiki/Managing-ROMs

Thanks for that, I mean its not a insurmountable problem, I can still use my controller for regular mame. Its just so weird that this specific emulator is giving me hell.

Hi.

I’m using a wireless Xbox 360 Controller with that official Microsoft remote connector for my Retropie 3.0 beta2 on a Raspberry Pi 2 which works perfect for me.
Now I bought a second one but can’t get both to work.
If I activate the first one it registers as usual and also activates the first light around the Xbox Button.
If I activate the second one, this one also registers himself as the first controller so that I have two Player 1 Controllers at the same time.
I tried to reconnect them with the remote connecter but that didn’t help.
I also thought that this could be an issue with the new controller, so I connected both to my PC. But there everything works just fine. Player 1 is player 1 and player 2 is player 2.
It also happens when I activate the second controller that the lights flash twince and then deactivate themself. If I deactivate the first controller now, the second controller actives himself automaticly like if it was in standby and becomes player 1.

I also checked the /dev/input Folder (where you do the jstest) and there’s only js0 and no js1 or so.

I’m quite confused now how I should solve this problem. I tried to google it but I only find guides to setup just one Xbox 360 Controller.

I installed and configured my Xbox Controller with the following guide by using step 3 – init script:
https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-the-XBox360-controller

It uses this code:

In the /etc/init.d/xboxdrv:

#! /bin/bash
### BEGIN INIT INFO
# Provides:          xbox-controller
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start XBOX Controller Service
# Description:       Start the xboxdrv daemon with several options
#                    support up to 4 Controllers
### END INIT INFO

# Author: MasteRehm

PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="XBOX Controller Service"
NAME=xboxdrv
DAEMON=/usr/bin/$NAME
DAEMON_ARGS="-D -d --deadzone 4000 --dbus disabled --detach"
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] && . /etc/default/$NAME

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
# and status_of_proc is working.
. /lib/lsb/init-functions

do_start()
{
        if [ $CONTROLLER_NUM -gt 4 ]; then
                echo -e "\n$CONTROLLER"; exit 1;
        fi
        start-stop-daemon -S -q -x $DAEMON -- $DAEMON_ARGS $CONTROLLER

# -- This workaround only works with 4 controllers connected.  It also is creating a name that
# does not match the minor device node.

#        # Workaround: xboxdrv daemon creates /dev/input/js[4-7] device files, if /dev/input/js[0-3] created on startup.
#        if [ -x /usr/bin/rename ]; then
#                sleep 1
#                if [[ <code>ls /dev/input/js*</code> =~ /dev/input/js[4-7] ]]; then rename 's/js4/js0/;s/js5/js1/;s/js6/js2/;s/js7/js3/' /dev/input/js*; fi
#        fi

# Rather than renaming files, it's better to clear the existing ones by stopping the driver
# and then when you start it again, everything will be correct.

    sleep 3
    do_stop
    sleep 3
        start-stop-daemon -S -q -x $DAEMON -- $DAEMON_ARGS $CONTROLLER
}

do_stop()
{
    start-stop-daemon -K -o -q -x $DAEMON
    sleep 1
}

case "$1" in
  start)
    log_daemon_msg "Starting $DESC" "$NAME"
    do_start
     status=$?
    log_end_msg $status
    ;;
  stop)
    log_daemon_msg "Stopping $DESC" "$NAME"
    do_stop
     status=$?
    log_end_msg $status
    ;;
  status)
    status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
    ;;
  restart)
    log_daemon_msg "Restarting $DESC" "$NAME"
    do_stop
    case "$?" in
      0|1)
        do_start
        case "$?" in
            0) log_end_msg 0 ;;
            1) log_end_msg 1 ;; # Old process is still running
            *) log_end_msg 1 ;; # Failed to start
        esac
        ;;
      *)
        # Failed to stop
        log_end_msg 1
        ;;
    esac
    ;;
  *)
    echo "Usage: $SCRIPTNAME {start|stop|status|restart}" >&2
    exit 3
    ;;
esac

And in the /etc/default/xboxdrv:

# How many Controllers? (support up to 4 Controllers)
CONTROLLER_NUM=2

case $CONTROLLER_NUM in
    1) CONTROLLER="-w 0 -l 2 --trigger-as-button --dpad-as-button"
    ;;
    2) CONTROLLER="-w 0 -l 2 --trigger-as-button --dpad-as-button --next-controller -w 1 -l 3 --trigger-as-button --dpad-as-button"
    ;;
    3) CONTROLLER="-w 0 -l 2 --trigger-as-button --dpad-as-button --next-controller -w 1 -l 3 --trigger-as-button --dpad-as-button --next-controller -w 2 -l 4 --trigger-as-button --dpad-as-button"
    ;;
    4) CONTROLLER="-w 0 -l 2 --trigger-as-button --dpad-as-button --next-controller -w 1 -l 3 --trigger-as-button --dpad-as-button --next-controller -w 2 -l 4 --trigger-as-button --dpad-as-button --next-controller -w 3 -l 5 --trigger-as-button --dpad-as-button"
    ;;
    *) CONTROLLER="incorrect amount of controller specified"
    ;;
esac

Of yourse I’ve entered CONTROLLER_NUM=2.

Has anyone any idea how I can fix this and get it to work?
Thank you!

If your system boots on ES directly, you can try to edit “usr/bin/emulationstation” (if I remember well) and add your lines right after #!/bin/bash.

Thanks! I had considered just editing one of the already existing start up scripts, but I didn’t know which one to use.

In the end, I decided to use a different method of running my script. I learned that I could have the script called whenever I plugged in my controller by making a rule in the /etc/udev/rule.d folder. See

https://raopinion.wordpress.com/2012/01/27/mayflash-n64-controller-adapter/

I was pretty disappointed though. I spent hours configuring my controller setup only to realize that n64 emulation is pretty bad. Most games run fast with the rice plugin, but for whatever reason, the menu textures are shot. I wonder if any future updates will correct these issues…

ssh in, or press f4, then a key after it to stop emulationstation restarting

Hi.

Pretty new to Retropie/RPI in general but I’ve learned a lot the last days.

Thing is, I’ve been playing all sorts of emus & roms with a PS2-clone USB wired joypad “GreenTechAsia”, with nothing to complain about.

Then yesterday I purchased the official “Microsoft Xbox 360 Wireless Controller for Windows & Xbox 360 Console”
(Link: This one: Microsoft Xbox 360 Wireless controller)

… and used this Youtube-guide:
RetroPie: Xbox wireless controller setup on Raspberry Pi – by Floob

… which refers to these instructions:
Github: Setting up the XBox360 controller

… but with lesser satisfaction.

I know that the USB-reciever which is plugged in to the RPI should “detect” 4 controllers natively, and that’s correct when I check the js*-files in /dev/input/

However after following – the exact – instructions of that Youtube video & the Github instructions, my Emulationstation “detects” 3 joypads instead of only 1 controller (which it’s supposed to be).

A look in the /dev/input folder shows me js0, js1 and js2.

The input js1 is the only one that responds when doing a jtest.
That’s.. well irritating to say the least… since retroarch-joypad configure goes for the js0-input.

All in all:

If I only knew how to “get rid” of the other 2 phantom controllers so Emulationstation only detects 1 (real) controller would be nice.

Even nicer would be if I managed to set my Xbox 360 wireless joypad from js1 to js0 – so I could run the retroarch joypad config properly.

I’m used to having my good ‘ol wired USB pads properly set up via retroarch and then to be found in the /opt/retropie/emulators/retroarch/configs/ folder

I’ve tested to just remove the phantom js-files, but after reboot they spawn alive those little twitchers… grrr!

Help me!

It sucks having a brand new USD $50 controller to be collecting dust if I don’t work this out.

The normally refered to retroarch.cfg, es_systems.cfg and es_config.cfg files – for me – are “mysterial” files that I don’t in any way have the slightest grip of.

Besides from switching paths for roms & set video_smooth = true, that is

Otherwise I think I’ve got a pretty good platform to build from now, a RPI2 + Retropie 2.6 + loads of roms.

Did the “Binary based” install in RetroPieSetup.
And the “Perform script update” … if that could make it easier for you to help me?

Anyways, thanks in advance.

/Alucard the Swede, hence the rusty English grammatics.

I have a Raspberry Pi 2 with version 3.0 beta 4 installed successfully with 2 Logitech F310 controllers and a MAME joystick. All controllers work fine and are recognized in NES, SNES, Megadrive, MAME, etc. The problem I am having is that only 1 controller (for player 1) is recognized in the Atari 2600 emulator. I am not able to play any 2 player games. I have checked the controller configuration file for Atari 2600 and it directs it to the “all” controller configuration file. I was wondering if there is something that needs to be added to the Atari 2600 controller configuration file to allow it to recognize a second controller for 2 players. Thanks in advance to anyone who can help!

Hey mate,

I’m also using an iPac VE in my build and I’ve successfully managed to configure all keyboard buttons except for the ones corresponding to the joystick. I can’t figure out how to get “up, down, left and right” working. Have you got any clue?

So far, this is my config:

# Keyboard player 1
input_player1_a = z
input_player1_b = x
input_player1_start = num1
input_player1_l = lshift
input_player1_r = v
input_player1_left = left
input_player1__right = right
input_player1__up = up
input_player1_down = down
input_player1_l2 = nul
input_player1_r2 = nul
input_player1_l3 = nul
input_player1_r3 = nul

This is driving me crazy. And even more so because the config says:

Mupen64plus-libretro utilises RetroArch configurations. Add custom retroarch controls to the retroarch.cfg file in

/opt/retropie/configs/n64/retroarch.cfg
Yes, sure, but which custom controls?

Regards,
Jonathan

I didn’t come across this thread until late, but for anyone else working on this, I found the instructions at https://learn.adafruit.com/retro-gaming-with-raspberry-pi/buttons to be quite helpful.

The procedure is essentially what @raoulangel described.

We have rebuild an old dead Arcade cabinet and fitted it with retropie, image: RetroPie SD-card Image for Raspberry Pi 2 Version 3.0 BETA 4

It uses two seperate “DragonRiseInc.GenericUSBJoystick” joystickcontroller.
As the arcade cabinet only has 3 buttons+start+coin on each side, there are plenty of button connections left on the controllers.

I would like to dedicate a button to exit the emulator and return to the retropie frontend.

I have managed to do so in AdvMame and Mame4All, but am having trouble in FBA.

The exitbutton is wired to js0-button 10 (verified by jstest /dev/input/js0)

my /opt/retropie/configs/fba/fba2x.cfg is as follows. As you can see, I tried to add QUIT to the joystick portion.

[Keyboard]
# Get codes from /usr/include/SDL/SDL_keysym.h
A_1=306
B_1=32
X_1=308
Y_1=304
L_1=122
R_1=120
START_1=13
SELECT_1=9
LEFT_1=276
RIGHT_1=275
UP_1=273
DOWN_1=274
QUIT=27
#player 2 keyboard controls, disabled by default
A_2=999
B_2=999
X_2=999
LEFT_1=276
RIGHT_1=275
UP_1=273
DOWN_1=274
QUIT=27
#player 2 keyboard controls, disabled by default
A_2=999
B_2=999
X_2=999
Y_2=999
L_2=999
R_2=999
START_2=999
SELECT_2=999
LEFT_2=999
RIGHT_2=999
UP_2=999
DOWN_2=999

[Joystick]
# Get codes from “jstest /dev/input/js0″
# from package “joystick”
A_1=0
B_1=1
X_1=2
Y_1=3
L_1=4
R_1=6
START_1=9
SELECT_1=8
QUIT=10
#Joystick axis
JA_LR=0
JA_UD=1
#player 2 button configuration
A_2=0
B_2=1
X_2=2
Y_2=3
L_2=4
R_2=6
START_2=9
SELECT_2=8
#Joystick axis
JA_LR_2=0
JA_UD_2=1

[Graphics]
DisplaySmoothStretch=1
# Display Effect: 0 none, 1 scanlines
DisplayEffect=0
DisplayBorder=0
MaintainAspectRatio=1

[Sound]

I also altered my /opt/retropie/configs/all/retroarch.cfg file and added:

input_exit_emulator = escape
input_exit_emulator_btn = 10
input_enable_hotkey = nul

I’m not sure thats possible to be honest:
http://sourceforge.net/projects/pifba/files/

I’ll let you know if I find a way.

Hey!

I managed to figure it out how to properly configure the N64 controllers for my iPac VE. The only thing missing is Z-support and D-pad, which I still don’t know how to configure.

I found the answer using this link in combination with the controller button reference.

I’ve posted my config below so that you can have a look at it as well. Keep in mind that plus is minus and vice-versa. The Y-axis is reversed.

# Keyboard player 1
input_player1_a = z
input_player1_b = x
input_player1_start = num1
input_player1_l = lshift
input_player1_r = v
input_player1_left = left
input_player1_right = right
input_player1_up = up
input_player1_down = down

# Keyboard player 1: Joystick
input_player1_l_x_plus = right
input_player1_l_x_minus = left
input_player1_l_y_plus = down
input_player1_l_y_minus = up

# Keyboard player 1: C-pad
input_player1_r_x_plus = "c"
input_player1_r_x_minus = "lctrl"
input_player1_r_y_plus = "space"
input_player1_r_y_minus = "lalt"

# Keyboard player 2
input_player2_a = i
input_player2_b = k
input_player2_start = num2
input_player2_l = w
input_player2_r = l
input_player2_left = d
input_player2_right = g
input_player2_up = r
input_player2_down = f

# Keyboard player 2: Joystick
input_player2_l_x_plus = g
input_player2_l_x_minus = d
input_player2_l_y_plus = f
input_player2_l_y_minus = r

# Keyboard player 1: C-pad
input_player2_r_x_plus = "j"
input_player2_r_x_minus = "a"
input_player2_r_y_plus = "q"
input_player2_r_y_minus = "s"

# Increases audio volume.
input_volume_up = num6

# Decreases audio volume.
input_volume_down = num7

I’ve also attached a photo showing a reference to which buttons and mapped to what in my layout as well as a photo of my build.

Hopefully this will help you configure your machine properly as well. Let me know if you manage to fix D-pad support!

Regards,
Jonathan