@Darksavior actually snes9x2005 is not rendering jurassic park right. SNES9x2010 is actually doing it right. That game uses a kind of a fake high res mode that renders a 640x240 image, but the snes sends out a 320x240 image. So on a CRT TV, every other line blurs together making a kind of a fake transparency. It was a trick used in a couple of game including kirbys dream land 3. The problem is that emulators don't output down to 320x240, and show the full 640x240 image with every other line as a vertical line where there is supposed to be a fake transparency. There is a shader that does the blend, but makes the games look blurry during the 320x240 parts (kirby changes back and forth based on the level) and is slow on a Pi. Snes9x 2005 just ignores it all together and just shows a 320x240 image with no transparency. Bsnes on the other hand (not on the Pi) can detect it and add the blend when needed.

@edmaul69 that worked perfect thanks for the help

@soonerdoc I tested sending buttons from the 360s directly and had the same results. I believe its an issue with rgbcommaner. no big deal if you don't mind errors but I do. I decided to go pc on this arcade build now. New os but new problems :). I'll checkin again but please contact me if you find a soultion.

@BuZz I want to disable it for the Nintendo 64 and SNES

@Shootersf I have only tried PiFBA briefly. I use lr-fbalpha as I use a Pi3. Does PiFBA have a config file that can be edited and saved? It may well stick if you go that route.

I will try adding games. I will also check out the wiki forum. Thanks.

I tried it on a 32-bit installation of ubuntu and I must say it runs okay. However I don't know if it is really Dolphin 5.0.
It says "Dolphin f94cd57".

@Capeman save states can be dangerous if there is a in game save. I've had it where the game thought I was using a different memory card and could no longer save to the main game because the memory card from the save state did not match the real one.
They are great if you're just trying to pass a part, but not as a save to come back to.

@backstander

I think I'll need to level up a few more times.

It's really more intimidating than it is difficult. After you've written a couple of commands and learn a few troubleshooting measures, it becomes as routine as anything else.

Now, finally I found another image from the retropie facebook grp... tried it and BAM, no more color problems!!! Wth?
Guess I need to compare the configs since this last one was pre-configured for crt.

Awesome! :) Who would have thought-.. Thanks all!

I am going to put it in a NES advantage, and the two player switch "might" be used for power ON/OFF instead.

@Mahlon If you are happy to just use the default es_systems.cfg file, ie alphabetical order and default names etc you should actually delete the version in /home/pi/.emulationstation. The system will treat this as a custom config file. If you add extra systems to the Pi not already in this config file they won't appear unless you add them manually as it looks here first for the systems to display. If this doesn't exist it defaults to the /etc/emulationstationversion.

solved it! I just rebuilt the filesystem in another SD card and now everything is working.
Probably I have corrupted the configuration moving manually the images of the megadrive.
Thanks guys

@DEWx

What would I need to do, to (re)install the xbox-controller using xboxdrv (while removing it first, incl. the other driver)

If you're talking about the Xpad driver, as long as you include --detach-kernel-driver in the xboxdrv launch command, the two drivers should be able to coexist without issue.

It's definitely not worth your time to start every game just to see if it works. It won't get you anywhere since many games start fine but then have issues later.

If you are finding that many games don't work then you may have the wrong ROM set, it needs to match with the version of MAME you are using.

Assuming you do have the the correct set, you can find the non-working games more easily by running searches using the ROMlister program. For example you can use it to search for Sega S-TV ROMs which will never work on Raspverry PI. Then you can make a batch file to delete those ROMS.

Did you manage to solve this?
My situation is kind the same. I have two controllers, though they are different type than this one.
Both controllers report themselves as "Gamepad", fortunately with different addresses.
So in the udev rule instead of specifying its name I used
ATTRS{address}=="bt address"
(interestingly with small letters when required: E8:A1:00:.... -> e8:a1:00:... you can check it with the udevadm info -a -n /dev/hidraw0 or hidraw1 command)
This is where the good story ends.
From this point the EmulationStation looses, because both of the controllers are recognized with the same name and somehow they got mixed up. Sadly the same happens in the games also.
Any idea to tell Linux to propagate the BT client on different name than it reports itself?

@mattrixk Have you tried the tilde key?

oh really? I think I have to read about basic programming

well I tried to enable the button pcb like described here:
http://sudomod.com/forum/viewtopic.php?t=57

"type:

cd /home/pi/Adafruit-Retrogame

then type:

make retrogame (This did not work - So I had to do one more step)

This should build the executable retrogame utility. If you instead get an error message, there’s a problem in the edited table — most likely a missing curly brace, comma or semicolon.
One more step is to create a custom udev rule which will allow retrogame input events to be visible to applications built using the latest SDL2 library. Some applications like the latest version of RetroPie's EmulationStation frontend require SDL2 and can't see input events from retrogame without this rule. It can't hurt to add this rule even if you aren't using EmulationStation or other SDL2 apps.

To add the rule, run the following command to create and edit the file /etc/udev/rules.d/10-retrogame.rules in the nano text editor:

sudo nano /etc/udev/rules.d/10-retrogame.rules

Now copy in the following line exactly as shown (this should all be on a single line in the rules file, i.e. don't put in any linebreaks):

SUBSYSTEM=="input", ATTRS{name}=="retrogame", ENV{ID_INPUT_KEYBOARD}="1"

Save the file by pressing Ctrl-O and pressing enter, then exit nano by pressing Ctrl-X.

Restart your Raspberry Pi to make sure the new configuration is loaded.

sudo reboot

Now we’re in good shape to test it!

Navigate back to the Adafruit-Retrogame directory

cd /home/pi/Adafruit-Retrogame

Retrogame needs to be run as root, i.e.:

sudo ./retrogame (this did not work)

Give it a try. If it seems to be working, press control+C to stop the program and we’ll then set up the system to launch this automatically in the background at startup."

I still can not create this file mentioned in the first step

make retrogame

Best wishes