@heinb Make sure you have all the bios files, respecting the filenames (capital or lower case names, as stated in the wiki)
Did you tried a specific rom only or with different roms?
If you can't run any roms, try looking for other bios files from different sources...

Surprisingly, this is not something that comes up often. There are quite a few emulators that don't have native controller support and rely primarily on the keyboard. I don't run any of the MSX emulators on RetroPie, but I assume this is the problem. Even if RetroArch allowed core remapping for MSX, I doubt it would allow f-key mapping to controllers.

If you really want to achieve this, you'll need to familiarize yourself with a keymapping program. This technique is completely off the beaten path, but has been achieved in RetroPie by others. Below is the link to a guide that explains the process as it relates to KODI. You'll need to adapt that information to the keyboard controls you wish to map for MSX.

http://blog.petrockblock.com/forums/topic/mapping-a-game-controller-in-kodi/

I'm currently working in this direction with a few emulators in my own setup, so if you have any further questions, I may be able to help.

The binaries have been updated.

I see time in time again that people are trying to get their controllers from a game system working on their Pi (no wonder: you're used to them, they cost a small fortune and they are of great quality). Those controllers often use a proprietary way of "communicating" w/ other hardware. They are often not compatible w/ general open standards or need to be switched to "standard compatible mode" or something. That is, even though they have a USB wire or are said to connect through Bluetooth they do not comply to general computer standards. Sometimes, like for the genuine Sony branded PS3 controller or the genuine Microsoft branded Xbox 360 controller, there is a solution, workaround or driver for these pieces of hardware for RetroPie (click the links in this post!).

Maybe it should be communicated a little better (sticky? homepage?) that these controllers are NOT standard compliant and that support for them is limited. It might even help to complain about this to Microsoft or Sony. There is no reason to "reinvent" the way that devices communicate via USB or Bluetooth, so they shouldn't.

Succes w/ setting up proprietary hardware y'all. :-)

I got the games to launch now..but i have no control settings so im guessing i have to go back and add controls to prboom :/

No, since they require a newer firmware/kernel to support the RPI3.

Nice job!

I didn't correctly understand you earlier that you are going to be physically covering a widescreen monitor.

I think you should be able to force a 4:3 video mode following the "elinux" link Floob listed earlier. You may then still need to adjust a setting on your TV to prevent it from stretching the input to widescreen as well.

retroarch imho also uses snes9x-port, can't i change the savestate-format (to snes9x compatible)?
as i see in GooglePlay-Comments, retroarch is not working very well on android. It is also bigger (without emulators) than snes9x ex

i know that i can use srm-files (i do this currently), but most games does not support save on every position in game (mostly you must solve more than 1 Level for saving)

winscp worked perfect.

thanks everyone!

Ok, Thank you

@mediamogul said in lr-mame2010:

Are you saying Player 2 controls aren't mapped in the TAB menu for lr-mame2010? If this is the case, you can just select the Player 2 controls one-by-one and press "enter" on your keyboard. At that point MAME will wait for input and you can press whatever button you want on your second controller. If you add one that you didn't mean to, press "enter" gain and then "escape" to clear the entry.

Edit: The bigger problem is that lr-mame2010 won't save these changes if I remember correctly.

Yes, i press "enter" and after this only nº1 pad works fine, i press any button on nº2 pad and it doesn´t work....even i tried a nº3 pad (all pads configured and worked with all emulators except this one...) and no input, that´s life, it´s experimental

Hello, I think it's not the same issue. It will be a mapping issue with your controller.

You have to found configuration file of your controller for reicast :
Go here :
/opt/retropie/configs/dreamcast
and open : emu.cfg

Look : [input] part
evdev_mapping_1 = [NAME of your file controller config]

It will be on /opt/retropie/configs/dreamcast/mappings/[your file]
and check mapping.

Good luck.

Please post the contents of the files in/opt/retropie/configs/all/emulationstation (via pastebin.com or similar)

@ech33k

Here is the fist link off the Google search, "retropie ps4 wired":

https://www.reddit.com/r/RetroPie/comments/3oza3b/where_to_find_a_ps4_controller_install_guide/

@cyberneticwired Awesome! Thank you, i'll give that a try!

For reference, the supported formats (in es_systems.cfg) for the Megadrive are
.smd .bin .gen .md .sg .zip .SMD .BIN .GEN .MD .SG .ZIP

I've updated the Wiki with this.

.gen files certainly work with both picodrive and gx-plus-gx emualtor cores.