I've followed the instructions but I've got another problem. I can't see all systems emulator not only the ports.

For me, out of Retropie, Recalbox and Lakka the only one where it's been a straightforward affair, all working is Recalbox. Running Kodi Isenguard...can't wait for Krypton to catch up ;)

Much prefer Retropie, but hope ppl don't mind the mention.

@BuZz http://pastebin.com/rs1FP0Wb

https://retropie.org.uk/forum/topic/3/read-this-first

@BuZz I guess I hadn't noticed; I spend too much time editing the es_systems.cfg to know what was originally there, but it's good to know, thanks.

I have a problem where I deleted it but it wont recreate the file? any ideas or help with that.. I have chmod the cfg directory to 777

mame4all works fine

lr-mame4all wont work at all

ok that helps thanks.. I lost my ability to use the MAME tab menu now... sigh..

I was having the same issue. Added code from other sites, which said to add to /boot/configure.text instead of ".txt".

Went to .txt instead and uncommented hdmi_drive=2

Hope all the /boot/confit.text files and all the things I changed in them are okay.

Hello,

I had to reinstall mame2003 in the end for the settings to work. I have lost my controls though. I run a game hit tab and choose "input (general" and try and configure P1 and P2 etc but my bartop buttons are not detected now.

They work fine in ES and all other emulators execpt this arcade/mame2003 emulator.

Any ideas what it might be?

@chavatar Thanks man! Worked out great for the games I couldn't find. And also I could swap to the openGDB if the GDB didn't find the games I was looking for. thanks!

@meleu

After pushing this hotkey that I am back in emulationstation, it can hear the sound and can choose a game etc., but the screen (connected over composite) goes black, seems like it loose the connection, comes back for a millisecond and goes black the hole time. The physical conection of the screen is not the fault, it must be something with the hotkey and my retroarch.cfg. (I have different kinds of retroarch.cfg in each emulator.)

edit for posterity, and I might be an idiot
While researching a similar post on this forum (https://retropie.org.uk/forum/topic/3287/noob-xbox-controler-question/8) I discovered that connecting the charging cable/mount to an xbox 360 wireless controller does not make it a "wired" controller; a truly wired controller cannot be used "wirelessly." In retrospect, this now seems painfully obvious...

AgentlemanNinja, I'm not sure exactly what your controller situation is, but if you are running a true wireless controller with the charging cable, like I was, that might explain your problem.

Hope this is helpful.

This FoFix is very interesting. I might not ever get 'The Monkeys: Rock Band', but this could be the next best thing.

@bfenty Glad you got it working! That problem stumped me once or twice--it's sometimes good just to have another pair of eyes on it.

Ahh, I mounted it in the mnt as another folder and just redirected the es_systems to look there for the roms. I didn't even think to do it this way. thanks for the tip bud

I figured this out and wrote up a basic script to turn the backlight on and off for my secondary display. It's in a post in my Super Famicom build thread.

I am not aware of crashes because of CEC, but I know that some joysticks, in rare cases can make Kodi crash. Try running Kodi without any controllers attached and if the problem remains, post you Kodi log.

No problem:

vbs@vbs-XS35:~$ grep -a4 "(fbset)" /opt/retropie/supplementary/runcommand/runcommand.sh # get default fb_res (if not running on X) fb_orig="" if [[ -z "$DISPLAY" ]]; then fb_orig="$(fbset)" fb_orig="${fb_orig##*mode \"}" fb_orig="${fb_orig%%\"*}" fi

Well, I probably clicked that option in the runcommand menu "Select framebuffer Res" but I think I chose "320x240" which was the initially value anyway. But ok, that might be the reason! Thanks!