Since some recent kernel / drivers updates, some joysticks causes Kodi to crash, and others look like they get a button stuck. Others still work fine. If you are affected by this, you can disable the gamepad support in System -> System -> Input Devices until Kodi 17 comes out. It will have official joystick support, and hopefully all of this will be fixed.

Thanks to all :)

For now I'm stick to default ES version. Maybe in future the experimental branch would resolve all it problem.

I will mind the tip!

Thanks to all for responding me, thanks even to you I'm really near to finishing my project :)

[SOLVED] Thanks to all who replied. As per info the link posted by UDb23, the simplest solution was to move all the roms into the 'arcade' directory. That way, lr-fbalpha is selectable, alongside lr-mame2003. Brilliant!

@ezlikespie you haven't searched this site, read the instructions for mame or looked in the wiki. All information is provided. Your question has even been asked before on this forum many times. Here is one of many.....
https://retropie.org.uk/forum/topic/4197/can-someone-confirm-galaga-does-not-work-on-pi-3-mame/2

Okay so, apparently I misunderstood the copying process... I thought I could just use the SAMBA Shares, but that didn't work... However, I have since used the USB Flash Drive option and now the games and emulators are showing up on the console.

So, problem solved!

@FlyingTomahawk

I was trying to not go wifi route. Setting up a couple for my buddies and didn't want to mess with it. Might have to try it though. Thanks.

Chex quest can be loaded as a pWAD. For the DEH use the -deh load command.

@aschwan this is a different issue (Their script is launching but they can't see it)

i use the dual shock analog triggers for pedals, the problem i have with dual shock is the dial is hard to map except as left-right buttons. Worked great with the positional sensor in the dual shock 4, but the driver for that sucked up over half of my cpu

It was the SD card. Apparently nothing was loaded on it....

@aspiringnobody No - please use the other topic. It's not useful to continue on a previous (old) thread.

@meleu Yes. That's what I was saying :-)

@Lamaman1971 yea obviously lol. I meant their local network cache. It's still going to look for the name retropie and that's going to point to that old IP. I'm at work too much :/

Hey, sorry to keep this issue open for so long.
I was working on a cleaner re-implementation of this, but got bogged down in debugging.
I got very frustrated with it all for a while, and decided to let this lie for a while.

Currently, I am working on theming the system carousel on the main screen. Once that is in reasonable shape, I will start working on this again. I am now able to build (and debug!) on windows which has revitalized my development process a bit, so there's still hope!

Thanks for holding out for such a long time.

@drewjbx np!

Hi Franke808, Here are three main possibilities:

The OS (written image) is corrupt/not present, The SD card is faulty, The Pi is faulty.

When you wrote the image to the SD card, in Windows did it show that the card had free (and used) space and that you could open that 'drive' and see files on the SD card? If not, then you possibly didn't extract the image file 'prior' to writing it using Win32 Disk Imager.

I had yesterday an situation that the Pi wouldn't boot with a reimaged (old) SD card. My problem was if I pressed the SD card in a certain place the Pi would boot. Long story short, the SD cards connection pads were worn and didn't make appropriate contact.
I was able to use a spare SD card and successfully use that. Tip: Use a micro SD card in an SD card adapter so if the contacts wear, you just swap out the adapter without having to rebuild your OS.

To test the Pi, try a different serviceable SD card.