@bomberb17 For RetroArch/libretro based emulators (lr-mame..), the Select key should function as a 'Coin Insert'. If you're other MAME emulators (advmame, mame4all), I think you need to open the MAME input menu (pressing TAB on a keyboard) and manually map the key/button you'd like.

Deleting retroarch.cfg and renaming the other one didn't help. I reinstalled RetroPie with the same image. Installed plugin https://github.com/meleu/RetroPie-joystick-selection. In it I've set detect by name and set Logitech to player1 and Redragon to player2. It worked for player1 in lr-pcsx-rearmed. Not for player2. It is a problem with Redragon gamepad I think. In plugin I've deleted 2nd gamepad and Logitech now works in all my cores and all my games and in RetroArch menu. But when I've tried games the very first time, I had only one gamepad (Logitech) and keyboard plugged. And they didn't work in games. I think it's the problem in RetroArch, that it decides on its own what controller to use for player. And you can't configure it easily. That plugin is a good solution with detect by name option, it sets the corresponding device for the corresponding player as you want it, not as RetroArch wants it. But to be sure I need to test it with normal gamepad for player2, not Redragon one.

@mitu said in Logitech F310 not working: @raspy said in Logitech F310 not working: I would recommend leaving the switch on "X" and the mode button off (no light) That would probably be the correct choice, but the poster said it seems to be clone of the original controller and BUT I do not have the X - D switch on the back that seems to be everyone's issue That's correct, I don't have any button along the back side, so it could very easily be a clone. I didn't think of that, which could explain why all the front buttons are numbered 1,2,3,4, etc. Even the shoulder buttons are numbered in the same vein. I've been trying to sort things out from the advice given, but so far, no luck. The controller isn't being recognized. Even when I use a keyboard to navigate and try to configure the controller. ☹

@mitu The only setting which might be related to the joypad is input_joypad_driver, which is by default udev. You can try re-adding back the file, then changing this to sdl2 and see if this fixes the mapping. Yeah, I tried that. Didn't change anything. I've decided to just restore my RetroPie install from a backup and avoid the Xpad driver update for the time being. I was able to update everything else individually without issue. Thank you for your time and I apologize for not seeing this through to end.

@herb_fargus Thanks for the pointer - but it was actually the bottom right trigger, not one of the top ones - and I'm on the latest Retropie (4.x) so that issue shouldn't be happening anyway....like I said, no worries, I just added the trigger in manually and it's good to go. :) Love this thing - I've already built several more for friends! :)

it will show splash scrren if my buffalo controller is plugged in....if anything else...it will not show splash screen

@Rookervik I wasn't sure what resolution to use, so enjoy an almost 4k image

@fun4stuff good you solved it! :-)

For your luck, you solved it simply by switching from DInput to XInput mode. However, there may be cases where this workaround can't be used. This link may have a fully working solution: https://www.raspberrypi.org/forums/viewtopic.php?f=78&t=36564&sid=cc03fff216d25ee04264771b9e3bd0bc&start=25 In summary, some USB adapters / controllers, such as this one, have issues on various Linux distros. A problem on HID Input drivers prevents D-Pad to work properly. Down and Right works, but no Up and Left. To solve this problem, you'll need to recompile Linux kernel on your RPI after making a few changes on "hid-input.c" file, which is located in "/drivers/hid/hid-input.c" (Within the source code directory). You can find all instructions on link above. Alternatively, you can try a few compiled kernels made by the same guys who found this solution. But you'll need to make sure the kernel was compiled exactly for your linux version, or else, you may have problems (I got no sound problem two years ago, when I tried those kernels). This kernel bug is here since 2010, and it affects Linux on desktop too (got it on Ubuntu 14.04 and 16.04, per example). Until now, it wasn't fixed by developers. So, the only way to get it working is by compiling kernel from scratch.