@ShawnS: No worries. It would have been cool if it were possible.

@GetKeyOpenDoor if we deleted everything that was solved on the forum we wouldnt have much of a forum now would we? guarantee at least one other person had the same question and now doesnt have the benefit of an answer because you've removed it.

@tastetestertt Please open a new topic providing details as mentioned in https://retropie.org.uk/forum/topic/3/read-this-first

Thanks Buzz, got it working by following your steps. Appreciated!

RetroArch bug - https://github.com/libretro/RetroArch/issues/3605 (or by design perhaps - but should be changed imho).

the default emulator is not a libretro core so doesn't have the retroarch gui. You can try "lr-glupen64" from optional packages though if you require a libretro emulator.

I had a look in /boot/config.txt, but there was nothing of use there. I did come across something else though;

https://github.com/tasanakorn/rpi-fbcp

This utility will copy all the data from my primary framebuffer (fb0 / HDMI) to my secondary framebuffer (fb1/ USB). I've set it up to auto-run on start-up and it kind of works now. My next problem is that the refresh rate is only around 1 fps!

No, there is no metadata stored in the actual ROM zip, it's just a compressed file containing one or more files of binary ROM data.

That binary data might be a valid parent ROM, a valid split child ROM, a valid non-merged child, a picture of your cat, or random garbage.

The only way to check the contents of the zip against known ROM contents is to checksum the contents and compare them to known checksums. Those checksums are what a DAT file contains.

@a7mag3ddon only a commit log on github

After upgrades, I found that you need to plug in the controller for like five minutes.... Then unplug , it should vibrate and be back working, then select your kodi under ports, before you touch the controller wait till kodi comes up fully... Then try controller buttons... This should work...

Works great

Hey @BrockBoyts

I'm using lr-fba-next with romset 0.173 (fba 0.2.97.38) in RetroPie 4.0.3 on a Raspberry Pi 3 and TMNT: Turtles In Time seams to run fine for me. I have both tmnt2.zip and tmnt2po.zip and they both work great.

I also have an unknown romset (I downloaded when I didn't realized you had to have romsets for different versions of MAME when I first installed RetroPie) that I'm using with lr-mame2003 and have 3 versions of TMNT: Turtles In Time and they all work fine as well.

Do you have a tmnt2.zip.cfg file in your ~/RetroPie/roms/mame-libretro/ directory by chance?
(or whatever your ROM file is with .cfg after it?)

If you haven't already, you might also try updating the RetroPie-Setup script and then update lr-mame2003 to the newest binary.

Overclocking will give you more stability on games that may currently be "borderline" for you.

https://github.com/retropie/retropie-setup/wiki/Overclocking
EDIT: Sorry about previous post. That was better advice for a Pi 1. Use the settings for pi2. They're good and safe.

Oh, so you mean we have to wait for a PrBoom update and it is not that i'm messing around with the worng files/options?

By the way, I didn't know that PrBoom Plus existed at all, suppousedly it can load .pk3 mods just like ZDoom does, I don't know if it's compatible with Brutal Doom and the likes? Wonder if it would be too hard to port to work with the Pi3?

Got it. Thanks!

I'd recommend using the configuration editor to manage your configs:
https://github.com/retropie/retropie-setup/wiki/Configuration-Editor

You may want to check your system specific retroarch file isnt holding a mass of non-required configs now, there is usually just 4 or 5 lines in there.
A bit like this:
http://pastebin.com/n5FbDBUK

you can stream them with moonlight/limelight. Never tried it / don't have required hardware.

I will try a fresh install tomorrow but something in me says it's a 4.0.2 issue... The beta I ran work perfectly on all consoles I put on there with just installing gamecon (which in v4 automatically installs db9 drivers directly if i'm correct?) and this command 'sudo sh -c 'echo "gamecon_gpio_rpi" >> /etc/modules && echo "options gamecon_gpio_rpi map=0,0,2,0,0,0" > /etc/modprobe.d/gamecon.conf && reboot'' which then was enough to setup the controller on the next boot and play on all mentioned consoles