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

Thanks for responding Buzz....ended up being a craptastic power supply.

Great! Glad you got this working correctly!

Yes, what you put between <theme> and </theme> in /etc/emulationstation/es_systems.cfg refers to the corresponding directory in /etc/emulationstation/themes/<CURRENT THEME>/. There is also a theme.xml file in there that it uses to know what graphics to show.

Here's a tutorial to help you create your own ES theme:
https://github.com/retropie/retropie-setup/wiki/Creating-Your-Own-EmulationStation-Theme

having same problem with libretro/retroarch, if i could just get keyboard control, i'd be ok. Noticed if you turn off the ps4 controller (hold ps button for 10 seconds) keyboard control works again...

I was adding them incorrectly. I took the syntax examples from retroarch.cfg which only defines keyboard keys. To add joystick buttons, _btn must be appended as seen below.

input_screenshot_btn = "0" input_pause_toggle_btn = "2"

Try my approach combined with Luetzels' here:
https://luetzels.raspiblog.com/?p=1870

Install the patched Bluez from the blog (overwriting default raspbian bluez – do not uninstall it first, just overwrite). Then Shanwan sixad. Reboot, then its working like a boss..

Try this first.

@johnnypanic Hey, any specifics on the build or fresh install steps that worked for you? Im going mad here trying to get this scraper to work. Originally tired on my original build but no joy. Just re-imaged to the latest release, updated the startup script, setup the scraper via f4 command line (and updated it) yet when i go back into emulisation, no info or images on any of the roms.

I created a bug. It should be fixed if you update to the latest code.

@gunschlinger you are correct. Not sure how i missed that. Glad to see you are using them.

@DanC_1987 You need to install the ds4drv ps4 driver still.

https://pypi.python.org/pypi/ds4drv

Problem is.. without the driver, it says 1 gamepad detected.. but can't be configured. With the driver, 2 gamepads detected.. it configures in the "main menu" setup, and can then navigate through emulationstation... but then it's unresponsive in games.. "controller not configured" message after starting any game.

I've read that updating all binaries and scripts should fix it, but it didn't. I still have a controller that navigates through emulationstation, but completely unresponsive in games. Seriously frustrating.

@codinghorror said in Advmame emulator not showing up in RetroPie 4.0.2?:

(Is there a good reason not to use advmame? I prefer it for vector games and the like?)

We generally prefer RetroArch cores for their ease of configuration. lr-mame2003 and lr-fba-next are a good compromise between a large ROM set and nice performance on Pi 2 and Pi 3. It's also easy to find the ROMs, search Google for "mame2003 reference set" or "fba 0.2.97.38 reference set".

However, AdvMame is the only way to play vector games smoothly.

If you put ROMs in the mame-advmame directory and mame-libretro directory, you'll end up with two RetroPie menu entries called MAME which can be a bit confusing/messy. You can work around this by using the arcade directory for one type of ROM (say all your vector games in arcade and all other games in mame-libretro), or you can use a theme with different AdvMame/libretro-MAME header images.