@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.

Glad to hear that!

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.

@gizmo90 you could also put them in the arcade folder. The arcade folder let's you select from multiple different arcade emulators (libretro mame, advmame, fba etc) it's used for organizing if you have multiple romsets and you want to keep them all in the same place.

@mitu @kyuzumaki Curiously, I have something similar on 18.04.1, which is also a recent thing. I just stumbled across this post but already made my own thread with my own findings this evening: https://retropie.org.uk/forum/topic/21139/error-and-gui-terminates-back-to-es-when-launching-retropie-setup-direct-on-machine-libudev-but-ssh-is-ok Let me know if I can help grab any further information here to get this resolved. Thanks!

@hallda12 What I think it might happen is that the triggers are actually registered as analog axes instead of just button presses. The xpad driver has a parameter for this (triggers_to_buttons) which is always on in the RetroPie installations and disables this behavior. It doesn't seem that xpadneo has a similar parameter - or it behaves differently. You can try and running jstest /dev/input/js0 from the command line and see how the trigger appear - button presses or axis movement.

ANSWERING YOUR OWN QUESTION AGAIN DEPARTMENT: Don't ask me to explain this, but to navigate the boot menu you have to hold up on the joystick while tapping the down cursor key on the keyboard. And I was right, get past that and the emulation is superb, bringing some real curios to the Pi. (For many years, the Tutor had the ONLY home-TV licenced port of Scramble, the only other format to get one being the Vectrex. Quite a brutal version of Mr Do as well.)

@mitu But isnt the shortcut meant to be Hotkey + X, not just select/start on its own. I'm almost certain my map is correct. Its almost like Retroarch thinks my Xbox controller is something different.

Can you add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first ? What type of controller are you using ? You might want to switch to Emulationstation as frontend and configure it, since this will also generate a gamepad auto-configuration for RetroArch.

@kalel715 Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@quicksilver the “home” button is called “the globe”

Suffering from similar issues. I will try deleting all the .uae and see if that helps me. If no luck I plan to raise this in Github. Thanks again to @dudleydes for his efforts.

@jakejm79 i believe your neogeo colour coordination thing would at least work in fbalpha and my suggested layout thanks to the ‘game pad’ neogeo control layout core option.

@mitu @clyde okay thanks

I think I worked it out. A year or so ago when I originally set up my retropie I was focussing on PSX emulation, and in the "autoconfig" controller mappings I must have force mapped this: input_up_axis = "-1" input_down_axis = "+1" input_left_axis = "-0" input_right_axis = "+0" Removing these seems to have done the trick

@SpudsMcToole That's a pity. I've only got 4 games setup at present so haven't encountered that problem (albeit for some reason Elite simply won't work when I chain load it - I'll need to check whether it works with the run command instead).

You can customize your key/button bindings as you like - globally, per-system or per-game. Look into the RetroArch controller configuration docs.