@ciderman As a workaround, you could make a dedicated control panel and wire the microswitches of its second stick to the connectors for the respective buttons of the first stick.

Check the dip switches. You may be able to control the coin chutes. That's something I've seen often in the test/mame menu. This solution would be per ROM though, not per core.

@arduinoGamepad Emulationstation is using SDL's joystick sub-system to handle joysticks, my guess it's not detected as such. There's a similar sdl-jstest utility -which is similar to jstest - that tests whether the joystick is detected by SDL. To get it detected by ES, try one of these - in order add a local udev rule to force the device to appear as a joystick: SUBSYSTEM=="input", ATTRS{idVendor}=="<VID>", ATTRS{idProduct}=="<PID>" ENV{ID_INPUT_JOYSTICK}="1" substituting VID and PID with the values you get for your controller from running lsusb. Use Xboxdrv to make your device be seen as an Xbox driver.

It depends on the emulator. If it's a Libretro RetroArch core you can use Core remapping and save a game remap file. If you're using a MAME based emulator, you press Tab to open the menu and configure the Inputs for that particular game. In RetroArch's case, the input configuration in Emulationstation would produce a general mapping which is good enough for most games.

@mitu I'm using 4.4. I have not reset config from the retroarch gui. Controls work fine in the retroarch menu as well. This problem has had me stumped for awhile.

@mitu ok I think I know what to do. Should I edit the file to the keycodes?

@stoney66 I tried setting this up this way and the problem was still the same

@jcthrity3 Anyone? Beuler? Beuler?

@ddallman said in Player 1 START button not working IN GAME - CPS1: What could be the deal? If the start button works everywhere except the cps1 games, i would expect the issue to be in mame2003's cps1 emulation ? However i don't think you'll get support for this emulator, using mame2003-plus or FBNeo is highly recommended nowaday. Also, FBNeo is supposed to provide the best experience with cps1/cps2 in terms of accuracy and input lag.

problem looks solved!! thank!!!

@Maalik_ I see. I don’t know what happened that made reicast so screwed up recently. I was fortunate because when I built my bartop reicast was working the best it had and then we got access to lr-reicast (now Lr-flycast) and that was working well on the pi and even gave us access to some Naomi and atomiswave games and then all of a sudden it is like both projects fell off a cliff with a ton of users reporting various bugs. Sorry wish I could be more help.

I saw this thread, so I set up lr-hatari, got it working, and updated the docs, mostly just from the core's github readme. It worked pretty much first try, but the docs previously only covered Hatari standalone. One thing I am not clear on is how you get the core to look at different BIOS files in order to emulate the STE or Falcon, but I haven't tried that yet.

@Dcgrandon said in No input on certain PSX games: I've dug all I can in the archives but this one has me stumped. It's actually part of the PS1 emulator page - look here. You may have set the controller to analog for one game and this setting is automatically saved, applying to all games (as it's about the emulator/core options).

@pengu1n said in GPIO Controls Not Registering After Launching Games: [WARN] Input device ID 3 is unknown to this libretro implementation. Using RETRO _DEVICE_JOYPAD. That's because of the RA's configuration - try resetting the configuration to default by copying the retroarch.cfg.rp-dist files over the retroarch.cfg in the /opt/retropie/configs/all/ folder.

I have the same problem, not know how to solve, also my start button becomes X (for example) any tip? Thanks

I have a custom bar top arcade which has menu buttons on a front panel to navigate Emulationstation. I found another bit of configs I needed to place into es_input.cfg: <?xml version="1.0"?> <inputList> <inputConfig type="joystick" deviceName="Xin-Mo Xin-Mo Dual Arcade" deviceGUID="03000000c0160000e105000001010000"> <input name="a" type="button" id="11" value="1" /> <input name="b" type="button" id="8" value="1" /> <input name="down" type="axis" id="1" value="1" /> <input name="left" type="axis" id="0" value="-1" /> <input name="leftbottom" type="button" id="2" value="1" /> <input name="right" type="axis" id="0" value="1" /> <input name="rightbottom" type="button" id="5" value="1" /> <input name="select" type="button" id="9" value="1" /> <input name="start" type="button" id="10" value="1" /> <input name="up" type="axis" id="1" value="-1" /> <input name="x" type="button" id="1" value="1" /> <input name="y" type="button" id="0" value="1" /> </inputConfig> </inputList> Sorry for the false alarm. :/

@markwkidd thanks. Actually, it might be something that we can solve on our end on autoconfig. Adding the following to the mapping on /opt/retropie/configs/all/retroarch-joypads solved it: input_b_btn_label = "Cross (down)" input_y_btn_label = "Square (left)" input_select_btn_label = "Select" input_start_btn_label = "Start" 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 (right)" input_x_btn_label = "Triangle (up)" 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 = "Home" There's a repository with lots of these mappings here, following @mitu 's thread (thank you!): https://github.com/libretro/retroarch-joypad-autoconfig/tree/master/udev So it's probably something that's RetroPie-specific for now. Thanks both.

@Riverstorm I'm using an Xbox controller myself so this is definitely something to look into. Thanks for the detailed advice. I'll report back if I have any issues.