Forum Replies Created

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
  • colinshare84

    I feel bad for not having the time to try any of this myself!

    But thanks for all your help guys, I’ll try the steps (when life stops getting in the way!) which majerle9 took and see if I get the same result.

    Thanks again!

    in reply to: My SUpi NINTENDO #107104


    This looks excellent! Well done!

    Have you or are you planning on putting up some steps or a guide, etc? I was thinking about doing something similar to this but with a Raspberry Pi integrated into a keyboard to make a dedicated Amiga.



    I’ve still not had the chance to try any of this myself, luckily I only subject my machine to kids occasionally! But it’s good to know I’m not the only one, majerle9!

    Thanks for your help, buzz.


    @buzz, @herbfargus

    Thanks guys, I’ve not had the chance to check if I can actually navigate using my controller. I think the reason I hadn’t noticed this before is that my player 1 controls are js1 and player 2 is js0 (long story!).

    , that’s just what I was looking for! I’ll try this and let you know.


    in reply to: 2 x joystick config #106775

    Also, check out floob’s videos:


    He does well at keeping them updated to the most recent versions of RetroPie so they should help. There’s a few looking at exactly what you need.

    in reply to: 2 x joystick config #106774


    No problem!

    I understand the logic for the auto config files like you mentioned but since I only use a Xin-Mo with my setup, I’ve not really delved into utilising them I’m afraid.

    If it helps, here are the steps that I took to set up my controls once I had added the entry to cmdline.txt:

    Quit to the terminal using F4
    Type “cd /dev/input” to change to that directory
    Type “ls” and it will show the directory contents
    Look for js0, js1, js2, etc.
    Type “jstest js0”
    Press buttons to see what they are identified as and make a list/diagram, press Ctrl-C to quit jstest

    Type “sudo nano /opt/retropie/configs/all/retroarch.cfg”
    Go to the end of this file and add custom controls using the list/diagram such as:

    input_enable_hotkey_btn = “9”
    input_pause_toggle_btn = “7”
    input_exit_emulator_btn = “10”
    input_menu_toggle_btn = “6”
    input_volume_up_axis = “-1”
    input_volume_down_axis = “+1”
    input_audio_mute_btn = “8”

    input_player1_joypad_index = “1”

    input_player1_up_axis = “-1”
    input_player1_down_axis = “+1”
    input_player1_left_axis = “-0”
    input_player1_right_axis = “+0”
    input_player1_a_btn = “1”
    input_player1_b_btn = “0”
    input_player1_x_btn = “2”
    input_player1_y_btn = “3”
    input_player1_l_btn = “4”
    input_player1_r_btn = “5”
    input_player1_select_btn = “6”
    input_player1_start_btn = “7”

    input_player2_joypad_index = “0”

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

    input_player1_joypad_index = “1” should refer to the js name found previously
    Press Ctrl-X to quit and make sure to press Y to save
    Type “emulationstation” to get back to the familiar menus and try one of the retroarch emulators!

    Hope this helps! Maybe not the clearest steps but if you need any more help just ask!



    You can navigate with the d-pad?! I’m going to double check on my setup but I don’t remember that!!

    Either way, I’d still think adding an option to either disable the message or being able to change which buttons enter the runcommand menu would be a good addition. Don’t you agree? My 4 year old cousin can’t control his hands/excitement when starting a new game and I’ve had to tell him loads of times not to press buttons! Plus, I’ve got everything set up the way I want it so I don’t need to change which emulator runs a certain rom, etc.



    Yeah if you pay attention to the quick message then you’ll see it but the problem is that if you press joypad button 0 (by accident or on purpose!) then it drops back to a menu which you can’t navigate with anything other than a keyboard! That’s why I think having the ability to change which joypad button it looks for would be a good addition.

    It may be possible to change it by editing some code but I’m unsure as to which file I would need to edit.

    in reply to: 2 x joystick config #106658


    I was in your position not long ago! I’ve learned a lot since then!

    Assuming you’re running the most recent version of RetroPie! Follow this post to sort out the XinMo:


    No need to patch the kernel, simply go through the terminal and run “sudo nano /boot/cmdline.txt” to add the “usbhid.quirks=0x16c0:0x05e1:0x040” entry or take your SD card and plug it into a PC which will give you access to the cmdline text file.

    Good luck!

    in reply to: Autofire on the axis #106523

    hijinksensue, I ran into this problem too.

    What you need to do is go into your es_input.cfg and make sure that your buttons refer to page up and page down, similar to the following example:

    <input name=”a” type=”button” id=”4″ value=”1″ />
    <input name=”b” type=”button” id=”5″ value=”1″ />
    <input name=”down” type=”button” id=”1″ value=”1″ />
    <input name=”left” type=”button” id=”2″ value=”1″ />
    <input name=”menu” type=”button” id=”13″ value=”1″ />
    <input name=”pagedown” type=”button” id=”11″ value=”1″ />
    <input name=”pageup” type=”button” id=”10″ value=”1″ />

    <input name=”right” type=”button” id=”3″ value=”1″ />
    <input name=”select” type=”button” id=”8″ value=”1″ />
    <input name=”up” type=”button” id=”0″ value=”1″ />

    After the auto configuration in Emulation Station, my buttons seemed to refer to top left and top right or bottom left and bottom right.

    Hope this helps!


    For anyone that’s interested…

    I managed to have another go at this and I think I got it working.

    1. Plug in a controller to any USB port and type this command:

    udevadm info –query=property –name=/dev/input/js0

    2. Move the controller to the other USB ports and run the command above.

    3. The information returned from each USB port allows you to create a file named 20-custom.rules in /etc/udev/rules.d with the following contents:

    # Lower Left USB Port
    KERNEL==”js*”, KERNELS==”1-1.3″, NAME=”input/js0″
    # Lower Right USB Port
    KERNEL==”js*”, KERNELS==”1-1.5″, NAME=”input/js1″
    # Upper Left USB Port
    KERNEL==”js*”, KERNELS==”1-1.2″, NAME=”input/js2″
    # Upper Right USB Port
    KERNEL==”js*”, KERNELS==”1-1.4″, NAME=”input/js3″

    This results in a control pad being connected to, for example, the upper left USB port to be assigned js2. It doesn’t differentiate between devices but using their model/serial/name rather than which USB port they are connected to should generate this behaviour.

    Hope this is of help to someone!


    I had a shot at something very similar to this recently but gave up! I’m not experienced enough in Linux to see it through to the end.

    You could have a shot and see if you have any more luck. Here are the links to the pages I used:

    Using UDEV rules to assign persistent names to joypads

    As a rough guide, here are the steps I used:


    udevadm info –name=/dev/input/js0 –attribute-walk

    and then use the information which is returned to create a udev rule (in /etc/udev/rules.d)

    Good luck!

    in reply to: Hotkey Questions #105397

    I would also like to see this as an option.

    My problem is that I have 2 extra buttons in my arcade machine setup. I want these to ONLY control the volume + and volume -. I have another button I can use to quit the emulator. So I want to disable input_enable_hotkey_btn in general without affecting the ability to use input_volume_up, input_volume_down and input_exit_emulator. These only seem to work when a hotkey is assigned. Does anyone know how I can achieve this?

    I’ve tried:

    input_enable_hotkey_btn = ” ”
    input_enable_hotkey_btn = “nul”
    #input_enable_hotkey_btn = “9”

    But these all seem to disable the ability to use the volume and exit commands. I can achieve what I want with 1 button by assigning the hotkey to be the same as what I want, ie.

    input_enable_hotkey_btn = “9”
    input_volume_up_btn = “9”

    but this only allows me to use 1 single command rather than all 3 that I need.

    I’ve even tried setting multiple input_enable_hotkey_btn, such as:

    input_enable_hotkey_btn = “9”
    input_volume_up_btn = “9”
    input_enable_hotkey_btn = “10”
    input_volume_down_btn = “10”
    input_enable_hotkey_btn = “11”
    input_exit_emulator_btn = “11”

    …but this results in only 1 hotkey taking preference rather than all 3. Would I maybe be able to set multiple buttons for hotkeys somehow? This would allow me to use this method and achieve what I need!

    Thanks for any help!

Viewing 13 posts - 1 through 13 (of 13 total)