@natesroom sudo rm /home/pi/.kodi/userdata/guisettings.xml will remove the settings file and will create a default when you start kodi again.
OR navigate to that file open it and change the skin (around line 139) setting to one you have installed. ie

<skin>skin.estuary</skin>

@edmaul69 not to worry was haveing a really dumb day just forgot to switch over the kickstart roms simple fix

You have two options:

Stick with official plug and play devices like (s)nes classic mini Start a new hobby creating your own personalized Retropie system by starting from scratch. It's not that hard. All the information is readily available on this website. You may want to invest in a quality micro sd card first.

I find a workarround. If run script witch xterm emulationstation and games work fine. Strange, isn't it?

@edmaul69 so this is how the config.txt reads now... # for more options and information see# http://rpf.io/configtxt# some settings may impact device functionality. See link above for details# uncomment if you get no picture on hdmi for a def drive=2# uncomment to increase signal to hdmi, if you have interference, blanking, orno displayconfig_hdmi_boost=4# uncomment for composite PAL#sdtv_mode=2#uncomment to overclock the arm. 7

@edmaul69 looks like he used berryboot...I contacted him and he said he would flash it again for 5$ shipping. Thanks for your help! It was appreciated and I learned a few things :)

@nevsan

does anyone one have any advice themselves on best practices?

Start with a fresh and official image from this site, decide what features are most important to you and follow the official documentation until those features are operating to your satisfaction. That's what anyone truly happy with their installation has done.

3rd party images should always be avoided, as they're loaded with configuration errors that can't be easily corrected because there's no working knowledge of how everything was set up. Not to mention the fact that the images containing game ROMs are highly illegal and only serve to damage the reputation and risk the very existence of this project.

Well, I don't have an IPAC, but maybe some forum members can chime in with their experience, but IMHO shouldn't be an issue as long as all controllers are detected by the system.

@rjmonteiro edited last post for error

Ok, thank you

Thanks both.

Have added a 5 second delay, and it works now.

Will look at adding a powered hub.

Ok, so I've created separate emulator.cfg for each version of CSBwin I'm using and that works fine.

But now I have troubles with Der Clou again. After a reboot I can't start it from ES anymore, I get:

Executing: /opt/retropie/ports/theclue/theclue ERROR: Module Dsk: Open :./pictures/bubble.fnt

And it seems to be a path issues, because I get the same error when I try to run the binary from the menu in Raspbian.
I can run it when I go to the directory manually at the command promt. So my guess is that the script not goes into the directory and thats why it can't find the datafiles anymore. Weird thing is, that I can run it from ES after I started it once from the command promt.

Also i just noticed that I can't save because of restrictions. D:

Just wondering if you ever figured this problem out? I too am having the same problem. It worked fine for a while, then it just stopped working. I'm not sure what changed to cause it.