killer instinct does not work.

lr-fba-next: preliminary support, but not playable (AFAIK)
lr-mame2003: does not work because of a bug - https://github.com/libretro/mame2003-libretro/issues/38 - almost certainly would be too slow if it did work.
advamame: works, but about 0.5 fps.

n64 has a version you could try.

For those keeping an eye on this thread, so far so good! For about a week the Delta PMC-05V015W1AA seems to be working just fine, runs cool, the rPi runs fine, I'll test the analog audio output soon just to see if it's clean. It does have a soft high pitch harmonic tone, but inside any enclosure should be completely unheard.

You could download/setup a new RetroPie image at your friends and use SSH & SCP (under Windows Filezilla or WinSCP) to copy the roms folder over. Even easier would be to use the Samba file shares by enabling them in the config and then copy files over from \retropie\roms .

@BuZz Thanks Buzz. I just retried this at work :-) and it downloaded with the correct MD5. Thanks for the pointers.

@davej thanks for the advice and insights; I was unsure if exophase's code drove the GPU directly, it sounded like it did from descriptions, but benchmarks didn't confirm.
I do use the barrel distortion shader at times, but not often. Still soak-testing the Pi with the GPU overclock removed.

So did you just scrape your Arcade library and then add your own art? I like the way NES, SNES, and Genesis scraped with the box art, but Arcade was a cluster-F. I imagine scraping Arcade just for the data and taking screen shots to use as title art would be better.

@kaitlin4599 You must set a button to be the hotkey and then a button to be the menu toggle.
And to get the configs saved, you must to enable the "Save config on exit", but be prepared to face some confusing situations. The use of "save config on exit" is discouraged in RetroPie (my words, not an official statement).

Nevermind, I burnt it all down. On RetroPie 4.0 RC1 using NES30 Pro Firmware 1.7 Beta 5 and now the hotkeys are working. Thanks for the assist anyways...

@cromartian

If this is your only problem, it's probably a better idea to continue trying to troubleshoot it rather than move backwards. Can you past the contents of /etc/rc.local?

Hey, thanks for all the help, and thanks for the command lines, Rascas.

When I ran sudo apt-get update && sudo apt-get dist-upgrade -y I got the same "failed to fetch" errors as when I tried to install kodi. Tried 20 times or so. It would get about 3/4 way through and start doing that.

It just felt like a species of a "timeout" error to me. So, just to see, I took the pi downstairs and directly connected it to the modem. It went through both installs fine. So it's something to do with the wifi.

Anyway, got kodi up and running - fantastic. Thanks!

Now I have a weird problem where kodi cycles through launch over and over with the PS3 controller in - it goes from the black screen with the grey config box to the kodi background (the blue bubbles) and then bakc again, flashing errors at the bottom of the config screen so fast I can't read them. If I unplug the controller, Kodi starts without any issues. Once it's launched, it works with the controller fine, but won't exit, reboot, power down, or anything else unless I unplug the PS3 controller. It just cycles through the same thing as the launch over and over with errors at the bottom of the screen, like I am restarting it. The minute I unplug the controller everything works perfectly again.

Works great with the keyboard, though. So my workaround for now is launch Kodi with the controller, wait for the Kodi bubble background, then unplug the controller. Then plug the controller in and unplug the controller to exit.

Thanks,

It's working now. I uninstalled retropie and installed it again and reconfigured the controllers from RTGUI and then did the "Bind"-thing to get the controls right for the "Core" NES.

The keyboard is working as it should at this moment to, don't know what that was for weird error.

Thanks. =)

@edmaul69 the splashscreens were changed so you have to update your splashscreens manually from the splashscreen module and re-enable them or else you'll get a black screen

@Machtroid I forgot to mention earlier that I've never successfully overclocked the sdram, even mildly, either on a pi 2 or pi 3. Even 25mhz increases are unstable (when soak tested long enough).

@jtu128 if dual booting is too confusing just use the RetroPie sd image we provide and install lxde after the fact: https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#where-did-the-desktop-go then you can choose which one loads on boot with the autostart options

That board doesn't appear to have any sort of video out, so I doubt it's much use for running games.

uae4all doesn't use f12 - it uses ctrl+escape to go back to the menu

both mine with latest firmware autoconnect - however older firmware requires a script to connect in the background which is included in latest retropie-setup bluetooth configuration