Need a new search?

If you didn't find what you were looking for, try a new search!

Viewing 35 results - 1 through 35 (of 1,077 total)
  • Author
    Search Results
  • ceconl
    Post count: 2

    I’ve been searching forums and help everywhere online and I can’t figure this out. I have two homemade joysticks using the Easyget USB encoders from amazon. They are detected as DragonRise Inc. Generic USB Joystick by RetroArch.

    I have them configured for Emulationstation, NES, SuperNes, MegaDrive, and MAME just fine. I’m having an issue with 32x and getting the 6 button setup to work for Mortal Kombat for instance. I’ve created retroarchconfigs in the 32x config location using the button info I have from from running jstest. I can’t get my top row “XYZ” to be recongnized. I have gone into retroarch and verified core options is set for 6 button.

    Haven’t tried PSX with this joystick yet to see if I have similar issues. Any help is much appreciated.

    Here is a copy of my config:

    #Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

    input_remapping_directory = /opt/retropie/configs/sega32x/

    input_player1_joypad_index = 0
    input_player1_b_btn = 6
    input_player1_a_btn = 5
    input_player1_y_btn = 8
    input_player1_x_btn = 7
    input_player1_l_btn = 11
    input_player1_r_btn = 4
    input_player1_start_btn = 3
    input_player1_select_btn = 2
    input_player2_joypad_index = 1
    input_player2_b_btn = 6
    input_player2_a_btn = 3
    input_player2_y_btn = 7
    input_player2_x_btn = 4
    input_player2_l_btn = 5
    input_player2_r_btn = 2
    input_player2_start_btn = 8
    input_player2_select_btn = 9

    # Axis for RetroArch D-Pad.
    # Needs to be either ‘+’ or ‘-‘ in the first character signaling either positive or negative direction of the axis, then the axis number.
    input_player1_up_axis = -1
    input_player1_down_axis = +1
    input_player1_left_axis = -0
    input_player1_right_axis = +0
    input_player2_up_axis = -1
    input_player2_down_axis = +1
    input_player2_left_axis = -0
    input_player2_right_axis = +0

    #Hotkeys- Hotkeys enable you to press a combination of buttons to do such things as exit emulators, save states,
    # and load states, as well as any other functionality in an emulator. (In the example below 8 is the select key
    # and 9 is the start key so when I hold down select and press start it will exit the emulator.)
    input_enable_hotkey_btn = 2
    input_exit_emulator_btn = 3
    input_save_state_btn = 5
    input_load_state_btn = 4
    input_menu_toggle_btn = 0
    input_state_slot_increase_axis = +0
    input_state_slot_decrease_axis = -0

    #include “/opt/retropie/configs/all/retroarch.cfg”

    Post count: 1

    I have had emulation station working great on my pi2 for a few weeks now. I am using a PlayStation 2 controller with a converter to USB, and a Logitech f310 gamepad. Historically when the start and select button when pushed on either controller it would allow me to Exit a emulator. However since upgrading to the pi 3 I can no longer exit emulation using the start and select button combination. There also seems to be some difficulty setting up each controller input using the configuration menu. It will frequently skip buttons without anything being pressed and I end up having to go back to reconfigure individual buttons. The system was upgraded using apt-get update and apt-get upgrade before being used in the pi 3. Does anyone have any thoughts on how to fix the start select button combination to exit the emulator? I have already tried editing the config file to reflect a hotkey and exit button , but the key numbering is different for each controller. Also I found the after editing the config file the start select method worked from Sega Genesis but did not work from Nintendo 64 for one controller and not at all for the other.

    Post count: 8

    I’ve built a “PiSP Pocket” device by installing a Raspberry Pi 3 into a gameboy pocket. An annoying inconvenience I’m having is the requirement to plug in a keyboard when I want to tweak retropie settings like wifi, audio, memory splitting, etc.

    So I’m trying to figure out a way to make my controls (which are USB via Teensy) emulate keyboard strokes outside of emulators and emulation station. I know emulators allow keystrokes via hotkeys, but they don’t seem to apply to Retropie’s settings that are accessible as a “system” in emulation station. Clicking on those settings launches what appears to be a shell script/console window that requires a keyboard.

    I’ve spent a couple hours researching apps like joy2key and QJoyPad but they seem to function only or best as a GUI which I can’t do with Retropie…

    Does anyone have any ideas for accomplishing this?

    Post count: 2
    #122354 In reply to: Dreamcast |

    In addition to hyell’s fix I found that the:

    /opt/retropie/configs/all/autoconf.cfg has reicast set to an input of 1. I changed it to 4.

    # this file can be used to enable/disable retropie autoconfiguration features
    mupen64plus_audio = 1
    mupen64plus_hotkeys = 1
    mupen64plus_compatibility_check = 1
    reicast_input = 4 
    es_swap_a_b = 0

    after changing the input number in the above file I put in my input device info:


    backend = oss
    disable = 0
    Debug.SerialConsoleEnabled = 0
    Dreamcast.Broadcast = 4
    Dreamcast.Cable = 3
    Dreamcast.RTC = 1543276800
    Dreamcast.Region = 3
    Dynarec.Enabled = 1
    Dynarec.idleskip = 1
    Dynarec.unstable-opt = 0
    aica.LimitFPS = 1
    aica.NoBatch = 0
    aica.NoSound = 0
    bios.UseReios = 0
    joystick_device_id_2 = -1
    pvr.MaxThreads = 3
    pvr.Subdivide = 0
    pvr.SynchronousRendering = 0
    pvr.rend = 0
    rend.UseMipmaps = 1
    rend.WideScreen = 0
    ta.skip = 0
    evdev_device_id_1 = 6
    evdev_device_id_2 = 7
    evdev_device_id_3 = -1
    evdev_device_id_4 = -1
    evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_XboxGamepad(userspacedriver).cfg
    evdev_mapping_2 = /opt/retropie/configs/dreamcast/mappings/controller_XboxGamepad(userspacedriver).cfg
    joystick_device_id = -1
    ElfFile = 
    OpenGlChecks = 0

    Before changing the input number whenever I would reset my device_id’s and device_mappings this information it would go back to the default values whenever I started the dreamcast emulator.

    I’m using 2 wireless Xbox 360 controllers and both are working on Power Stone in the dreamcast emulator.
    I hope this helps anyone trying to get this going.

    Post count: 13

    I found the solution online. Hope this helps someone.

    1. Create a new file in notepad called “Sony-PlayStation4-DualShock4-Controller.cfg”.

    2.It should be placed in /opt/retropie/configs/all/retroarch-joypads

    3. Delete the file “Sony_Computer_Entertainment_Wireless_Controller.cfg”) that is currently created by Retroarch when you setup the controller by the wizard.

    4. Paste the contents below into the file you created in notepad (probably easier to do after step 1. Thats it! It should now work.

    input_device = “Sony Computer Entertainment Wireless Controller”

    input_driver = “udev”

    input_vendor_id = 1356

    input_product_id = 1476

    input_b_btn = “1”

    input_reset_btn = “1”

    input_y_btn = “0”

    input_select_btn = “8”

    input_enable_hotkey_btn = “8”

    input_start_btn = “9”

    input_exit_emulator_btn = “9”

    input_up_btn = “h0up”

    input_down_btn = “h0down”

    input_left_btn = “h0left”

    input_state_slot_decrease = “h0left”

    input_right_btn = “h0right”

    input_state_slot_increase = “h0right”

    input_a_btn = “2”

    input_x_btn = “3”

    input_l_btn = “4”

    input_r_btn = “5”

    input_l2_btn = “6”

    input_load_state_btn = “6”

    input_r2_btn = “7”

    input_save_state_btn = “7”

    input_l3_btn = “10”

    input_r3_btn = “11”

    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 = “+2”

    input_r_x_minus_axis = “-2”

    input_r_y_plus_axis = “+5”

    input_r_y_minus_axis = “-5”

    input_menu_toggle_btn = “12”

    input_b_btn_label = “Cross”

    input_y_btn_label = “Square”

    input_select_btn_label = “Share”

    input_start_btn_label = “Options”

    input_up_btn_label = “D-Pad Up”

    input_down_btn_label = “D-Pad Down”

    input_left_btn_label = “D-Pad Left”

    input_right_btn_label = “D-Pad Right”

    input_a_btn_label = “Circle”

    input_x_btn_label = “Triangle”

    input_l_btn_label = “L1”

    input_r_btn_label = “R1”

    input_l2_btn_label = “L2”

    input_r2_btn_label = “R2”

    input_l3_btn_label = “L3”

    input_r3_btn_label = “R3”

    input_l_x_plus_axis_label = “Left Analog Right”

    input_l_x_minus_axis_label = “Left Analog Left”

    input_l_y_plus_axis_label = “Left Analog Down”

    input_l_y_minus_axis_label = “Left Analog Up”

    input_r_x_plus_axis_label = “Right Analog Right”

    input_r_x_minus_axis_label = “Right Analog Left”

    input_r_y_plus_axis_label = “Right Analog Down”

    input_r_y_minus_axis_label = “Right Analog Up”

    input_menu_toggle_btn_label = “PS”

    Post count: 7

    Thats exactly what I’ve been searching for, too!

    Would be great to have a different default controller for each emulator, but still be able to switch them around with a hotkey or something…

    Post count: 2

    This is a great tutorial. I did it yesterday and everything is working, except one thing : I can’t configure the emulator exit button and the hotkey for mame4all (start + select).
    I tried several configurations, including configuring the “retroarch.cfg” and “Xin-Mo Xin-Mo Dual Arcade.cfg” manually with:

    input_start_btn = "8"
    input_exit_emulator_btn = "8"


    input_select_btn = "9"
    input_enable_hotkey_btn = "9"

    The emulator exit button (start+select) works well if a use a 8BitdoNES30Pro8BitdoNES30Pro controller. The 8BitdoNES30Pro8BitdoNES30Pro.cfg is exactly the same above, only the button numbers are diferente, of course.

    – Yes, the buttons are working
    – Yes, the buttons are mapped

    Is there any other place that may be misconfigured ?
    On the mame4all <TAB> menu, there is not mapping to a exit button. Should be one available there ?

    Any help is appreciate.

    Post count: 3

    The problem with mupen64plus and hotkeys is, everytime you start the programm, the mupen64plus.cfg gets edited. To change that, edit the runfile for mupen64plus.


    # write hotkey to mupen64plus.cfg
    iniConfig “=” “\” $configdir/n64/mupen64plus.cfg”
    iniSet “${hotkeys_m64p[$i]} “$bind”

    comment the two last lines out, it should look like this.

    # write hotkey to mupen64plus.cfg
    #iniConfig “=” “\” $configdir/n64/mupen64plus.cfg”
    #iniSet “${hotkeys_m64p[$i]} “$bind”

    However keep in mind that, your hotkey configurations from retroarch are not updated to mupen64plus anymore.

    Post count: 4

    I got my 8Bitdo NES30 Pro to work by following Floob’s video tutorial step-by-step. The only thing I did differently was to bind the controller using “power + R1” instead of “power”, so it runs in Joystick mode and lets you bind L2 and R2 (which did not work in the video tutorial).

    Following this video and once you configured the controller in emulation station, the controller should be set up for all emulators, except for Megadrive/Genesis. This is also mentioned in the video. You’ll need to switch to 6 button controller and configure your button mappings manually for Megadrive.

    There’s another problem regarding the hotkey mappings in mupen64plus (N64 emulator). I found a quick and dirty solution for that one by digging through the forums, but it seems there is also a way to do that using the Configuration Editor – I haven’t found that setting yet, but I will have a look at it as soon as I’m home again. However, here’s the thread where I describe the problem.

    On a side-note:
    Downgrading your conrtoller firmware will add problems rather than solving yours. The Joystick mode has just been added with version 1.69, so you will be stuck with your shoulder buttons (L2 and R2) not working.

    Post count: 2

    [quote=121656]Make the hotkey button nul or remove it.


    Cheers! Defining it and setting it to nothing (null) works like a charm!

    Follow up: How do i bind button 5 in player 1 to exit? As I want a button on the panel to also make it go back. The button is connected to button 5 input to player 1 on the USB breakout. :-S

    Post count: 1858

    Make the hotkey button nul or remove it.

    Post count: 9

    For anyone else having this issue, I was able to solve it. It turns out that whenever the controller paired while emulation station was loaded it was moving my PS3 controller config to a cfg.bak file and generating a new config file. I was unable to do anything about this.

    In the end, I used RGUI in the Retropie menu to set up the hotkeys for the controller in the actual retroarch.cfg. After saving the config file, I removed retroarch.cfg and renamed the file generated by RGUI to retroarch.cfg so that it became the config. Now when the new config file is generated for my controller, the hotkeys still function because they are hard coded into retroarch.

    Post count: 32

    -Wireless Only Portion
    Well, kind of good news for those with the steam controller. It appears that the mouse pad portion of the steam controller works with retropie – bad news is emulation station doesn’t use a mouse :)

    When in retropie and over wireless, if you run your finger over the right d-pad area it lightly vibrates just like on a desktop and these files show up in /dev/input/by-id:

    I did add the /lib/udev/rules.d/99-steam-controller-perms.rules file and contents, rebooted, and plugged in the steam wireless stick on reboot.
    However, js0 or any js* for that matter doesn’t exist when only the steam controller is plugged in.

    -Wired Only Portion
    So, after messing around with the wireless and getting no where, I plugged it in using a micro usb to usb cable and rebooted again. Once in emulation station I went to configure input it found the device….but as a keyboard….the ONLY buttons and pads/sticks that seem to work for me right now are:
    A Button
    Start Button
    Select Button
    Left D-Pad (I think you can also configure the stick as the same…kind of a clone thing between the stick and left d-pad)
    And that’s it….no B button….give me at least the B button so I can play NES roms :)

    FYI – I’m running a Pi3 with keyboard and built-in wifi enabled, can’t promise good performance on a Pi2 with the stuff below per the URL below.

    So I found this tid-bit URL

    Hoped on putty and performed a sudo pip install libusb1 (I don’t know what version of php I have or came on the retropie 3.6 image, but giving it a go anyways…remember I backed up! *My install is fairly clean, I did install the Descent I & II ports, updated RP scripts, and that’s about it (aside from adding my roms)

    Next, in my home directory I did a wget

    tar xf master.tar.gz
    cd steamcontroller-master
    sudo python install

    sudo nano /etc/udev/rules.d/99-steam-controller.rules
    and added the following inside the empty file

    # replace game group by a valid group on your system
    # Steam controller keyboard/mouse mode
    SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", GROUP="games", MODE="0660"
    # Steam controller gamepad mode
    KERNEL=="uinput", MODE="0660", GROUP="games", OPTIONS+="static_node=uinput"

    Then reloaded udev
    sudo udevadm control --reload


    cd /steamcontroller-master/scripts start

    But got a bunch of errors with a lot of “enum” words in it, so I felt lucky and installed the part of the website (above) that listed “enum” in it:
    sudo pip install enum34
    It said something about the requirement already being satisfied, so I figured I was s***-out-of-luck. But for giggles I did the following:

    sudo udevadm control --reload start

    and low-and-behold no messages…looking good so far…didn’t think I’d get this far.
    So, the thing is I’ve got a 70″ screen mounted to the wall with no media center underneath, everything I use is either HD antenna, PLEX, or Roku, I cut the cable years ago and prefer a clean look. So, I’m not keen on having a keyboard hanging off the Pi3 mounted behing the TV, so my next step (after testing) is to setup the python script to auto-start. So, I’m going to edit my rc.local file
    sudo nano /etc/rc.local
    and add the following (change your paths if needed) after all the commented lines but BEFORE the exit 0 line.
    /home/pi/steamcontroller-master/scripts/ start
    after saving the file I stopped the process I kicked off earlier and tested the rc.local file by: stop

    Just to make sure no errors popped up, kept the steam controller plugged in (hardwire) and I’m ready for a reboot to see if it started.
    Wow, now when I go to Configure Input in emulation station I get a “1 gamepad detected”, I hold “A” on the joystick and it see’s it as a XBOX 360 Gamepad…that’s what I call progress.
    The controller is VERY touch sensitive, and I can’t seem to get the right bottom trigger or left thumb press to be defined.
    I’ll work on it a bit tomorrow, see if I’m doing something wrong and take a look at the python script…I’m a bit of a script kiddie (is that saying even still used?).
    Played a quick level in Super Mario on the NES (still wired joystick), exited with start-select like normal, then unplugged joystick and plugged the wireless stick in…this is where you get all warm and creamy….even without a reboot…the joystick works great and immediately over wireless…just need to turn the controller back on after unplugging the usb cable.
    I’m sooo thrilled and taken waaayy to much room in this forum…hope this helps someone.

    I’m thinking of writing a script to make this process much faster, I’m not the coder of the “steamcontroller-master” app, kudos to that person for making my life easier, but I can certainly make setting up a Steam Controller on a RPi much faster (I think).

    Here’s my config file, all buttons working and configured to use the thumbstick instead of the left d-pad for moving (I don’t like the sensitivity of the pads, so I swapped the d-pad for the thumbstick), just backup and overwrite your sudo nano /opt/retropie/configs/all/retroarch-joypads/MicrosoftX-Box360pad.cfg with this info:

    input_device = "Microsoft X-Box 360 pad"
    input_driver = "udev"
    input_r_y_plus_axis = "+4"
    input_l3_btn = "9"
    input_r_x_minus_axis = "-3"
    input_r_axis = "+5"
    input_save_state_axis = "+5"
    input_l2_btn = "4"
    input_start_btn = "7"
    input_exit_emulator_btn = "7"
    input_l_y_minus_btn = "h0leftanalogup"
    input_l_axis = "+2"
    input_load_state_axis = "+2"
    input_up_axis = "-1"
    input_r_y_minus_axis = "-4"
    input_a_btn = "0"
    input_b_btn = "1"
    input_reset_btn = "1"
    input_down_axis = "+1"
    input_r2_btn = "5"
    input_l_x_plus_btn = "h0leftanalogright"
    input_l_y_plus_btn = "h0leftanalogdown"
    input_right_axis = "+0"
    input_state_slot_increase_axis = "+0"
    input_x_btn = "2"
    input_menu_toggle_btn = "2"
    input_select_btn = "6"
    input_enable_hotkey_btn = "6"
    input_l_x_minus_btn = "h0leftanalogleft"
    input_y_btn = "3"
    input_left_axis = "-0"
    input_state_slot_decrease_axis = "-0"
    input_r_x_plus_axis = "+3"
    Post count: 97

    This RetroPie webpage should explain how to setup controllers for the various SNES emulators. They appear not to have an “in game” menu (like Mame when you press TAB on the keyboard).

    If I were you I’d choose an emu that “obeys” the standard key mappings which on my Pi 1 are:

    Hotkeys        |  Action
    Select+Start   | Exit  (avoid!)
    Select+B       | Reset (avoid!)
    Select+R2      | Save!
    Select+L2      | Load
    Select+Right   | State slot
                   |   increase
    Select+Left    | State slot
                   |    decrease
    Select+X       | Retroarch menu

    Some emulators exit when I press ‘Start’ or don’t start at all w/ certain ROMs. I have to fiddle w/ emulators for each game. Select your emu of choice by pressing left/right a lot when the emu starts up. You see a dialog screen then which lets you select an emulator of choice.

    Good luck! :)

    Post count: 31

    Glad you asked! I have tried for weeks to get 1.4 to play vector games at my native resolution with no luck. Last year, after many late nights with PiPlay, I was able to get native resolution on Vector games using 1.2 and this config. So, with RetroPie I finally tried a test with the pre-compiled advmame 1.2 executable from my other SD card (running PiPlay) and simply replaced the advmame .94 binary as a test. This was a feeble attempt at leveraging at least some runcommand flexibility–use 1.4 for most stuff, but for vector games, I could select .94 and know that it was actually running the 1.2 advmame I copied over.

    My .94 swap is kludgy, and I don’t get much traction with other posts on this topic which is why I did the test. When it worked, I figured maybe I could just get 1.2 setup properly with runcommand support. I am still willing to try suggestions, but I have already tried this config (corrected the paths) to no avail in 1.4. Could there be a difference in the retropie-compiled versions of 1.4 that specifically prevents 1280×1024? On a previous post, you seemed to suggest thats the case. But, with the coming changes possibly to the default resolutions in RetroPie, I am definitely interested in making this work well. Once you have seen the crisp vector lines, it’s hard to go back to blurry 640×480 for vector classics.

    Here’s my 1.2 config (game-specific input mapping removed):

    display_mode auto
    display_adjust generate_yclock
    device_video_clock 60-150 / 30-80 / 60
    device_video_format 33630 0.814815 0 0.111111 0.0740741 0.914286 0.0196429 0.00357143 0.0625
    device_video_modeline FULLSCREEN 105.37 1280 1336 1512 1568 1024 1046 1050 1120 -hsync -vsync
    debug_crash no
    debug_rawsound no
    debug_speedmark no
    device_alsa_device default
    device_alsa_mixer channel
    device_color_bgr15 no
    device_color_bgr16 yes
    device_color_bgr24 no
    device_color_bgr32 no
    device_color_bgr8 no
    device_color_palette8 no
    device_color_yuy2 no
    device_joystick auto
    device_keyboard raw
    device_mouse raw
    device_raw_firstkeyhack no
    device_raw_mousedev[0] /dev/input/mouse0
    device_raw_mousedev[1] /dev/input/mouse1
    device_raw_mousedev[2] /dev/input/mouse2
    device_raw_mousedev[3] auto
    device_raw_mousetype[0] ps2
    device_raw_mousetype[1] ps2
    device_raw_mousetype[2] ps2
    device_raw_mousetype[3] ps2
    device_sdl_samples 512
    device_sound auto
    device_video auto
    device_video_cursor auto
    device_video_doublescan yes
    device_video_fastchange no
    device_video_interlace yes
    device_video_output auto
    device_video_singlescan yes
    dir_artwork /home/pi/RetroPie/roms/mame-advmame/artwork:/opt/retropie/configs/mame-advmame/artwork
    dir_diff /home/pi/.advance/diff
    dir_hi /home/pi/.advance/hi
    dir_image /home/pi/.advance/image:/opt/retropie/emulators/advmame/0.94.0/share/advance/image
    dir_inp /home/pi/.advance/inp
    dir_memcard /home/pi/.advance/memcard
    dir_nvram /home/pi/.advance/nvram
    dir_rom /home/pi/RetroPie/roms/mame-advmame
    dir_sample /home/pi/RetroPie/roms/mame-advmame/samples
    dir_snap /home/pi/.advance/snap
    dir_sta /home/pi/.advance/sta
    display_artwork_backdrop yes
    display_artwork_bezel no
    display_artwork_crop yes
    display_artwork_overlay yes
    display_aspectx 5
    display_aspecty 4
    display_brightness 1
    display_buffer yes
    display_color auto
    display_expand 1
    display_flipx no
    display_flipy no
    display_frameskip 0.5
    display_gamma 1.0
    display_interlaceeffect none
    display_magnify 4
    display_pausebrightness 0.6
    display_resize fractional
    display_resizeeffect filter
    display_restore yes
    display_rgbeffect triad6dot
    display_rol no
    display_ror no
    display_scanlines no
    display_skipcolumns auto
    display_skiplines auto
    display_vsync yes
    vector/display_mode FULLSCREEN
    vector/display_translucency yes
    vector/display_intensity 3.0
    vector/display_antialias yes
    vector/display_beam 1.2
    vector/display_flicker .1
    vector/display_adjust none
    vector/display_magnify 2
    vector/display_rgbeffect none
    vector/display_resizeeffect none
    vector/device_video_output fullscreen
    vector/display_resize fractional
    vertical/display_ror yes
    input_hotkey yes
    input_idleexit 0
    input_map[coin5] auto
    input_map[coin6] auto
    input_map[coin7] auto
    input_map[coin8] auto
    input_map[event10] auto
    input_map[event11] auto
    input_map[event12] auto
    input_map[event13] auto
    input_map[event14] auto
    input_map[event1] auto
    input_map[event2] auto
    input_map[event3] auto
    input_map[event4] auto
    input_map[event5] auto
    input_map[event6] auto
    input_map[event7] auto
    input_map[event8] auto
    input_map[event9] auto
    input_map[p1_dialx] mouse[0,x]
    input_map[p1_dialy] auto
    input_map[p1_lightgunx] auto
    input_map[p1_lightguny] auto
    input_map[p1_mousex] auto
    input_map[p1_mousey] auto
    input_map[p1_paddlex] auto
    input_map[p1_paddley] auto
    input_map[p1_pedalbrake] auto
    input_map[p1_pedalgas] auto
    input_map[p1_pedalother] auto
    input_map[p1_stickx] auto
    input_map[p1_sticky] auto
    input_map[p1_stickz] auto
    input_map[p1_trackballx] mouse[0,x] mouse[1,x] mouse[2,x]
    input_map[p1_trackbally] mouse[0,y] mouse[1,y] mouse[2,y]
    input_map[p2_dialx] -mouse[0,y]
    input_map[p2_dialy] auto
    input_map[p2_lightgunx] auto
    input_map[p2_lightguny] auto
    input_map[p2_mousex] auto
    input_map[p2_mousey] auto
    input_map[p2_paddlex] auto
    input_map[p2_paddley] auto
    input_map[p2_pedalbrake] auto
    input_map[p2_pedalgas] auto
    input_map[p2_pedalother] auto
    input_map[p2_stickx] auto
    input_map[p2_sticky] auto
    input_map[p2_stickz] auto
    input_map[p2_trackballx] mouse[0,x] mouse[1,x] mouse[2,x]
    input_map[p2_trackbally] mouse[0,y] mouse[1,y] mouse[2,y]
    input_map[p3_dialx] auto
    input_map[p3_dialy] auto
    input_map[p3_lightgunx] auto
    input_map[p3_lightguny] auto
    input_map[p3_mahjong_a] auto
    input_map[p3_mahjong_b] auto
    input_map[p3_mahjong_bet] auto
    input_map[p3_mahjong_c] auto
    input_map[p3_mahjong_chance] auto
    input_map[p3_mahjong_chi] auto
    input_map[p3_mahjong_d] auto
    input_map[p3_mahjong_double_up] auto
    input_map[p3_mahjong_e] auto
    input_map[p3_mahjong_f] auto
    input_map[p3_mahjong_flip_flop] auto
    input_map[p3_mahjong_g] auto
    input_map[p3_mahjong_h] auto
    input_map[p3_mahjong_i] auto
    input_map[p3_mahjong_j] auto
    input_map[p3_mahjong_k] auto
    input_map[p3_mahjong_kan] auto
    input_map[p3_mahjong_l] auto
    input_map[p3_mahjong_m] auto
    input_map[p3_mahjong_n] auto
    input_map[p3_mahjong_pon] auto
    input_map[p3_mahjong_reach] auto
    input_map[p3_mahjong_ron] auto
    input_map[p3_mahjong_score] auto
    input_map[p3_mousex] auto
    input_map[p3_mousey] auto
    input_map[p3_paddlex] auto
    input_map[p3_paddley] auto
    input_map[p3_pedalbrake] auto
    input_map[p3_pedalgas] auto
    input_map[p3_pedalother] auto
    input_map[p3_stickx] auto
    input_map[p3_sticky] auto
    input_map[p3_stickz] auto
    input_map[p3_trackballx] auto
    input_map[p3_trackbally] auto
    input_map[p4_dialx] auto
    input_map[p4_dialy] auto
    input_map[p4_lightgunx] auto
    input_map[p4_lightguny] auto
    input_map[p4_mahjong_a] auto
    input_map[p4_mahjong_b] auto
    input_map[p4_mahjong_bet] auto
    input_map[p4_mahjong_c] auto
    input_map[p4_mahjong_chance] auto
    input_map[p4_mahjong_chi] auto
    input_map[p4_mahjong_d] auto
    input_map[p4_mahjong_double_up] auto
    input_map[p4_mahjong_e] auto
    input_map[p4_mahjong_f] auto
    input_map[p4_mahjong_flip_flop] auto
    input_map[p4_mahjong_g] auto
    input_map[p4_mahjong_h] auto
    input_map[p4_mahjong_i] auto
    input_map[p4_mahjong_j] auto
    input_map[p4_mahjong_k] auto
    input_map[p4_mahjong_kan] auto
    input_map[p4_mahjong_l] auto
    input_map[p4_mahjong_m] auto
    input_map[p4_mahjong_n] auto
    input_map[p4_mahjong_pon] auto
    input_map[p4_mahjong_reach] auto
    input_map[p4_mahjong_ron] auto
    input_map[p4_mahjong_score] auto
    input_map[p4_mousex] auto
    input_map[p4_mousey] auto
    input_map[p4_paddlex] auto
    input_map[p4_paddley] auto
    input_map[p4_pedalbrake] auto
    input_map[p4_pedalgas] auto
    input_map[p4_pedalother] auto
    input_map[p4_stickx] auto
    input_map[p4_sticky] auto
    input_map[p4_stickz] auto
    input_map[p4_trackballx] auto
    input_map[p4_trackbally] auto
    input_map[safequit] auto
    input_map[service_coin5] auto
    input_map[service_coin6] auto
    input_map[service_coin7] auto
    input_map[service_coin8] auto
    input_map[ui_toggle_ui] auto
    input_steadykey no
    lcd_server none
    lcd_speed 4
    lcd_timeout 500
    misc_bios default
    misc_cheat no
    misc_cheatfile cheat.dat
    misc_difficulty none
    misc_eventdebug no
    misc_eventfile event.dat
    misc_freeplay no
    misc_hiscorefile hiscore.dat
    misc_lang none
    misc_languagefile english.lng
    misc_mutedemo no
    misc_quiet yes
    misc_safequit yes
    misc_smp no
    misc_timetorun 0
    record_sound no
    record_sound_time 15
    record_video no
    record_video_interleave 2
    record_video_time 15
    script_led1 on(kdb, 0b1); wait(!event()); off(kdb, 0b1);
    script_led2 on(kdb, 0b10); wait(!event()); off(kdb, 0b10);
    script_turbo while (event()) { toggle(kdb, 0b100); delay(100); } off(kdb, 0b100);
    script_video wait(!event()); set(kdb, 0);
    sound_adjust auto
    sound_equalizer_highvolume 0
    sound_equalizer_lowvolume 0
    sound_equalizer_midvolume 0
    sound_latency 0.05
    sound_mode auto
    sound_normalize no
    sound_samplerate 44100
    sound_samples yes
    sound_volume 0
    sync_fps auto
    sync_resample auto
    sync_speed 1
    sync_startuptime auto
    sync_turbospeed 3
    ui_color[help_other] 000000 808080
    ui_color[help_p1] 000000 ffff00
    ui_color[help_p2] 000000 00ff00
    ui_color[help_p3] 000000 ff0000
    ui_color[help_p4] 000000 00ffff
    ui_color[interface] 000000 ffffff
    ui_color[select] 000000 afffff
    ui_color[tag] 247ef0 ffffff
    ui_font auto
    ui_fontsize auto
    ui_helpimage auto
    ui_translucency 0.8
    input_map[p1_up] keyboard[0,up]
    input_map[p1_down] keyboard[0,down]
    input_map[p1_right] keyboard[0,right]
    input_map[p1_left] keyboard[0,left]
    input_map[p1_button1] keyboard[0,lcontrol]
    input_map[p1_button2] keyboard[0,lalt]
    input_map[p1_button3] keyboard[0,space]
    input_map[p1_button4] keyboard[0,lshift]
    input_map[p1_button5] keyboard[0,z]
    input_map[p1_button6] keyboard[0,x]
    input_map[p2_up] keyboard[0,r]
    input_map[p2_down] keyboard[0,f]
    input_map[p2_right] keyboard[0,g]
    input_map[p2_left] keyboard[0,d]
    input_map[p2_button1] keyboard[0,a]
    input_map[p2_button2] keyboard[0,s]
    input_map[p2_button3] keyboard[0,q]
    input_map[p2_button4] keyboard[0,w]
    input_map[p2_button5] keyboard[0,i]
    input_map[p2_button6] keyboard[0,k]
    input_map[p1_doubleleft_up] keyboard[0,j]
    input_map[p1_doubleleft_down] keyboard[0,l]
    input_map[p1_doubleleft_right] keyboard[0,i]
    input_map[p1_doubleleft_left] keyboard[0,k]
    input_map[p1_doubleright_up] keyboard[0,up]
    input_map[p1_doubleright_down] keyboard[0,down]
    input_map[p1_doubleright_right] keyboard[0,right]
    input_map[p1_doubleright_left] keyboard[0,left]
    vertical/input_dipswitch[cabinet] cocktailinvaderl/input_dipswitch[cabinet] cocktail
    292x240/display_rgbeffect triadstrong6dot
    320x224/display_rgbeffect triadstrong6dot
    512x480/display_rgbeffect triadstrong6dot
    292x240x60/display_rgbeffect triadstrong6dot
    292x240x60/display_magnify 3
    292x240/display_magnify 3
    240x248/display_rgbeffect triadstrong6dot
    240x248/display_magnify 3
    224x288/display_rgbeffect triadstrong6dot
    224x288/display_magnify 3
    294x239/display_rgbeffect triadstrong6dot
    294x239/display_magnify 3
    336x240/display_rgbeffect triadstrong3dot
    336x240/display_magnify 3
    512x480x30/display_rgbeffect none
    512x480x30/display_resize integer
    512x480x30/display_magnify 1
    292x240/display_mode generate-quad
    292x240/display_resize mixed
    512x480x30/display_mode generate
    512x480x30/display_vsync no
    224x256/display_mode generate-quad
    224x256/display_rgbeffect triadstrong6dot
    224x256/display_magnify 3
    384x224x60/display_mode generate
    384x224x60/display_rgbeffect none
    400x254x53/display_mode generate
    400x254x53/display_rgbeffect none
    480x464x60/display_mode generate-double
    480x464x60/display_resizeeffect filter
    480x464x60/display_rgbeffect triadstrong3dot
    224x288x60/display_resize mixed
    224x288/display_resize mixed
    224x256x60/display_rgbeffect triad6dot
    input_map[p2_doubleright_up] keyboard[0,u]
    input_map[p2_doubleright_down] keyboard[0,v]
    input_map[p2_doubleright_left] keyboard[0,y]
    input_map[p2_doubleright_right] keyboard[0,n]
    input_map[p2_doubleleft_up] keyboard[0,r]
    input_map[p2_doubleleft_down] keyboard[0,f]
    input_map[p2_doubleleft_left] keyboard[0,d]
    input_map[p2_doubleleft_right] keyboard[0,g]
    input_map[p3_up] keyboard[1,scan0]
    input_map[p3_down] keyboard[0,k]
    input_map[p3_left] keyboard[0,j]
    input_map[p3_right] keyboard[0,l]
    input_map[p3_button1] keyboard[0,rcontrol]
    input_map[p3_button2] keyboard[0,rshift]
    input_map[p3_button3] keyboard[0,enter]
    input_map[p3_button4] keyboard[0,o]
    input_map[p4_up] keyboard[1,scan0]
    input_map[p4_down] keyboard[0,n]
    input_map[p4_left] keyboard[0,v]
    input_map[p4_right] keyboard[0,u]
    input_map[p4_button1] keyboard[0,b]
    input_map[p4_button2] keyboard[0,e]
    input_map[p4_button3] keyboard[0,h]
    input_map[p4_button4] keyboard[0,m]
    input_map[p4_button10] keyboard[0,down]
    input_map[ui_up] keyboard[0,up] or keyboard[0,i] or keyboard[0,up]
    input_map[ui_down] keyboard[0,down] or keyboard[0,k] or keyboard[0,down]
    input_map[ui_left] keyboard[0,left] or keyboard[0,j] or keyboard[0,left]
    input_map[ui_right] keyboard[0,right] or keyboard[0,l] or keyboard[0,right]
    input_map[ui_select] keyboard[0,enter] or keyboard[0,1] or keyboard[0,3]
    vertical/input_map[p1_right] keyboard[0,l]
    vertical/input_map[p1_left] keyboard[0,j]
    vertical/input_map[p1_up] keyboard[0,i]
    vertical/input_map[p1_down] keyboard[0,k]
    vertical/input_map[p1_button1] keyboard[0,rcontrol]
    vertical/input_map[p1_button2] keyboard[0,rshift]
    vertical/input_map[p1_button3] keyboard[0,enter]
    vertical/input_map[p1_button4] keyboard[0,o]
    vertical/input_map[p2_right] keyboard[0,u]
    vertical/input_map[p2_left] keyboard[0,v]
    vertical/input_map[p2_up] keyboard[0,y]
    vertical/input_map[p2_down] keyboard[0,n]
    vertical/input_map[p2_button1] keyboard[0,b]
    vertical/input_map[p2_button2] keyboard[0,e]
    vertical/input_map[p2_button3] keyboard[0,h]
    vertical/input_map[p2_button4] keyboard[0,m]
    vertical/input_map[start1] keyboard[0,3]
    vertical/input_map[start2] keyboard[0,4]
    vertical/input_map[coin1] keyboard[0,7] or keyboard[0,8]
    Post count: 9

    Trying to set up a generic PS3 Bluetooth controller I picked up an Amazon, and having a weird issue. I am running a Pi 2 with Retropie 3.5, because the controller would not re-pair properly after rebooting the Pi on Retropie 3.6. I installed the controller with the Gaisa clone support, and it appears to be paring properly and working well.

    I am trying to manually edit the config file for the PS3 controller to set up hotkeys. I am able to get everything set up properly and it tests fine, but when I reboot the Pi the hotkeys stop working. If I go back into the config file, all of the changes I make are gone. Its as if the file is being completely overwritten.

    I am not sure if its related or not, but when I reboot the pi and re-pair the controller emulation station isn’t recognizing anything is connected until I hit some buttons on the controller.

    This controller was working fine on a previous installation of Retropie 3.4 that I had upgraded to 3.5. I am attempting to re-build the image after the SD card had become corrupt on me.

    Anyone have any ideas what could be happening here?

    Post count: 34


    I liked the old retropieimage for my RPi2.
    It worked flawlessy!

    Now, I’m having great issues just to configure my controller.
    I have an easy 8-bit USB-controller which I configure in Retropie, which works fine.

    But I want to add some hotkeys, and that seems impossible.
    The file I try to edit is /opt/retropie/configs/all/retroarch-joypads which is created when I configure the controller in Retropie.
    But making changes in that file doesn’t affect anything at all…

    Any tips? :)

    Post count: 4

    With some further research I found a “solution” to the problem described above in THIS THREAD (which I didn’t see earlier, unfortunately). So in case anyone encounters the same problem:

    The cause for the hotkeys not working is indeed the “wrong” button IDs, which are being written into mupen64plus.cfg automatically.

    I disabled this feature in the /opt/retropie/emulators/mupen64plus/bin/ by commenting out the following lines:

    # write hotkey to mupen64plus.cfg
     # iniConfig " = " "\"" "$configdir/n64/mupen64plus.cfg"
     # iniSet "${hotkeys_m64p[$i]}" "$bind"

    Then I manually made my settings in /opt/retropie/configs/n64/mupen64plus.cfg by adding the button IDs shown by jstest:

    # Joystick event string for stopping the emulator
    Joy Mapping Stop = "J0B10/B11"
    # Joystick event string for switching between fullscreen/windowed modes
    Joy Mapping Fullscreen = ""
    # Joystick event string for saving the emulator state
    Joy Mapping Save State = "J0B10/B7"
    # Joystick event string for loading the emulator state
    Joy Mapping Load State = "J0B10/B6"

    This fixed my problem – the hotkeys are working now.

    I still don’t understand where those other button IDs retroarch uses are coming from though…

    Post count: 28

    For sure i’m the dumbest guy on earth. I didn’t thought for one second that I have to push my hotkey + M or N button. Will give a try tonight.

    Thanks for your help.

    Post count: 1


    I have the same problem.

    After checking, I found that every time when I run this file, it would regenerate mupen64plus.cfg.

    You could find this :

    # write hotkey to mupen64plus.cfg
     iniConfig " = " "\"" "$configdir/n64/mupen64plus.cfg"
     iniSet "${hotkeys_m64p[$i]}" "$bind"

    To solve this problem, I just edit,

    # write hotkey to mupen64plus.cfg
    # iniConfig " = " "\"" "$configdir/n64/mupen64plus.cfg"
    # iniSet "${hotkeys_m64p[$i]}" "$bind"
    Post count: 4

    I just configured an 8Bitdo NES30 Pro on my RPi3 (RetroPie 3.6) using Floob’s video tutorial and am having troubles getting the hotkeys in mupen64plus (mostly for “exit emulator”) to work.

    I suspect the problem has something to do with the fact, that the “Joy Mapping Stop” values are auto-generated when starting up the emulator. These values don’t work for me, since the mupen64plus.cfg – to my knowledge – uses the button numbers shown by jstest. This leads to problems in my case for the following reasons (or at least that’s what I think the problem is):

    The button numbers in my controller specific config file (in the retroarch-joypads folder) are different from those shown when using jstest. E.g. in the controller specific config file “select” and “start” are 21 and 22 (matches up with the values in Floob’s video), but jstest shows 10 and 11 for the very same buttons… The controller config works whith all emulators I’ve tried so far (except for megadrive, where I had to enable the 6 button controller and remap the buttons a,b,x,y,l,r)…

    The InputAutoCfg.ini entries for my controller in the n64 folder also got generated flawlessly (but use the low button numbers which are shown in jstest, not the ones from the retroarch-joypads config). Normal controls in mupen64plus work as they should. It’s just the hotkeys I can’t get to work.

    I tried to set “Joy Mapping Stop” to “J0B10/B11” in the mupen64plus.cfg, but as soon as I start the emulator, it gets overwritten by “J0B21/B22” – which does not work to exit the emulator – so I suspect it actually needs the jstest values in order to work.

    Does anybody know, why my controller.cfg in retroarch-joypads uses different button numbers than shown by jstest and/or how I can overwrite the values used in mupen64plus.cfg permanently?

    Thank you in advance for the help!

    In case this is relevant:
    I used a different mode than the one shown in Floob’s video tutorial in order to pair my controller (“power + R” instead of “power”). This is a new mode added with a later 8bitdo firmware and lets me configure L2 and R2 in ES (which didn’t work with the other mode). However, apart from the additional entries for L2 and R2, the generated values in retroarch-joypads/controllername.cfg are the same.

    Post count: 432

    you have to hold your hotkey enable button to select shaders. i’m not sure what it is on keyboard, but it works for me if i press select on my joypad (hotkey_enable), and then n or m on my keyboard, it cycles shaders.

    maybe it should be mapped to some joypad buttons instead by default in retropie, as it’s not really usable like this, but i don’t know.

    Post count: 4

    Updated to the latest build of ir-fba-next and the service menu hotkey is working now, just push start button for a few second and will enter the service menu.
    But if you are using 8tindo nes controller like me, you will need a keyboard to do it, cause if you push the start button for a few second, it’s long enough to turn your controller off……..hope they can make the timing for hot key a little bit shorter to fix this…

    Post count: 1

    I’m relatively new to this project, but recently purchased an iPAC2 USB controller running Emulation Station and Retropie. I have two problems that I would like some advice please:

    1. (MAME for all) For some reason buttons 5 and 6 (Player 2) don’t work on 6 button games like SF2. FYI, All 6 buttons work fine on Player 1. I’ve read somewhere that there could be a conflict with the hotkeys?, but have no idea how to get into this feature?. I have the latest version of Retropie.

    2. Player 2 doesn’t acknowledge on most of the consoles i.e. SN and Megadrive.

    FYI I was looking for a non programming project so I don’t have much knowledge on programming pi’s, but happy to learn a few lines if it will help resolve this issue.

    My iPAC2 is set to the default keys i.e. buttons 5 and 6 are currently set to buttons ‘I’ and ‘K’

    Appreciate any help here.

    Post count: 54

    [quote=120182]ok, all good, thank you,
    overlay opacity 0.40
    overlay scale 1.70

    can i add these values to the retroarch.cfg so they load for each game, like a shader?

    save the settings via the menu

    Thanks for trying it out and glad it works. I’m curious though why you’ve changed the overlay scale? That shouldn’t be set to 1.7. if you’re doing that then something is wrong as you’re basically telling it to scale the image to 1.7 time it’s size and as the overlay is exactly 1280×720 it should be set to 1 (no scaling).

    Could you get some screenshots of an emulator running with the scanlines so that I can try and see what’s going on? It should be hotkey plus f8 on the keyboard (right shift is hotkey on the keyboard). If you could get one with the overlay scale set at 1 and one with the overlay scale set at 1.7 that would be great. (also set the opacity to 0.6 so I can see it clearly).

    The screenshot will be saved in /home/pi/.config/retroarch/screenshots/


    Post count: 9

    input_device = “USB,2-axis 8-button gamepad ”
    input_driver = “udev”
    input_r_btn = “5”
    input_save_state_btn = “5”
    input_start_btn = “7”
    input_exit_emulator_btn = “7”
    input_l_btn = “4”
    input_load_state_btn = “4”
    input_up_axis = “-1”
    input_a_btn = “0”
    input_b_btn = “1”
    input_reset_btn = “1”
    input_down_axis = “+1”
    input_right_axis = “+0”
    input_state_slot_increase_axis = “+0”
    input_x_btn = “2”
    input_menu_toggle_btn = “2”
    input_select_btn = “6”
    input_enable_hotkey_btn = “6”
    input_y_btn = “3”
    input_left_axis = “-0”
    input_state_slot_decrease_axis = “-0”

    Post count: 10

    So I just recently bought the RP2 and installed RetroPie on it. The first time I installed Retropie on my RP1 I had some issues with the controller. I use a third party xbox 360 wireless adapter off from ebay with my wireless controllers. The adapter was plug and play and I set up the controllers with the gui setting in RetroPie. I did however have to change the joypad driver to sdl in the cfg file in Retro to get it working.

    This time, I have done everything the same way, except it doesn’t work for the N64 emulator. Before when I launched a game I got a message saying “Xbox 360 accessory wireless controller configured on port 0(sdl)” or something like that. Now when I launch a game, I get the same message, except it says (userdriver) instead of sdl. But everything seems to work fine though, all my hotkeys and things work. Except when it comes to the N64 emulator. The controller works just fine except the hotkeys, so I cannot save or load any game. I’ve tried setting the controller explicity in the emulators cfg file but it won’t make a difference. All the other emulators has set the joypad driver to “unused”.I do not get any message saying my controller is configured in the N64 emulator like I do for all the other emulators, so there is clearly some issue with setting the controller. I might add that pressing “select”+”start” seem to work though to exit the emulator.

    On all the emulators I get a message saying my 360 controller has been configured with userdriver except on the N64 emulator. I can play the N64 games with no problems, it’s just my hotkeys for save and load that doesn’t work, exit the emulator works just fine. How do I fix this?

    I tried all the emulators available and discovered something odd. When I use the IR-mupen64plus emulator, I can save and load and I do get the message saying the controller is configured. But if I try any other emulator, let’s say mupen64plus-gles2rice, I don’t get any message that it has been configred. So U could go with only using the IR-mupen64plus, but it dosn’t always work that good.

    Weird, I’ve never had this issue on the RP1 before.

    Post count: 4
    #120020 In reply to: IPac and retropie??? |

    thanks for the reply, but reset and other buttons are still activated :/
    is there a way to just delete the hotkeys entirely? the only one i actually need is the exit emulator button combo

    Post count: 3

    Does anybody know how to create an easy hotkey short cut with the MAME emulator, got it working to quick save, load and exit on all others except MAME, bit of a pain to have to use the keyboard to exit

    Post count: 1629

    The default would be hotkey and F8. You could use a button by using
    input_screenshot_btn =

    You could put this in /opt/retropie/configs/all/retroarch-joypads/{controller-file}

    Post count: 1


    I built a PiGrrl 2 and am having problems with the select button. It’s mapped as the space bar but it enable fast forward when I press it. I can’t find where the hotkey special buttons are setup at. Can anyone help me?

    I know I could change the key applied to the select key, but then how do I change all the retroarch configs to the “new” select button?


    Post count: 54
    #119341 In reply to: RPi 1 PS button |

    Do you mean changing the retroarch hotkey button? If so you can change it in the retroarch config files. Got to this folder:

    There should be a config for each controller.

    In the config file change: input_enable_hotkey_btn = “0”
    To: input_enable_hotkey_btn = “16”

    Button 16 should be the home button on the PS3 controller.

    Post count: 28

    Update: it’s working. Previously, I didn’t understood that I need to edit my retroarch.cfg file using sudo nano command (via putty). I edit the main retroarch file like this:

    # video_smooth = false
    # video_shader_dir = /opt/retropie/emulators/RetroArch/shader
    # video_shader_enable = false
    # video_shader = “/path/to/shader.{cg,cgp,glsl,glslp}”

    What the difference between video_shader path and directory? I would like to use the hotkeys to change the shaders ingame…

    …and, for example, the SNES retroarch.cfg file (i’m doing exactly the same with others emulators):

    # Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

    video_shader = “/opt/retropie/emulators/retroarch/shader/crt/crt-hyllian.glslp”
    video_shader_enable = true
    video_smooth = false

    input_remapping_directory = /opt/retropie/configs/snes/

    #include “/opt/retropie/configs/all/retroarch.cfg”

    My main issue now is about crt-royale.glslp: it simply do not work at all. Any idea why guys?

    Post count: 1858
    Post count: 4

    I don’t know if this is a “sin” or whatever, but I joined here for something not really related to Retropie. My son and I built a retropie rig for my father’s birthday last year and I know start+select exits RA and goes backinto EmulationStation without a hitch. I built a sweet HTPC that runs Kodi, Steam, EmulationStation with RA, Netflix, etc…’s all controllable via my remote control and/or 360 pad. The only way I can exit RA currently is setting a hotkey (l3 + r3) to go into RA (version 1.3), scroll down to exit, and then I’m back in ES. I want to shorten this process to just exiting via a hotkey, like select + start, and be back into ES.

    Look, I know this is a minor, minor thing….but it’s bugging me. I can’t find out how that bind in RetroPie works to impliment it into my desktop setup. Anyway….thanks in advance. And keep up the good work!

Viewing 35 results - 1 through 35 (of 1,077 total)