@jmebd That kind of questions, it is better for you to ask them in the kodi oficial forum, or another forums more dedicated to that kind of subject. I have a PVR backend configured + some clients but I am no expert in this, it is a very simple setup and I don't use it much. My provider transmits the channels in h264, I never had stuttering problems or whatsoever, even on RPI 1. And this is a retrogaming forum, surely you will find better support for your doubts in more appropriate places.

in 3.6 I had no problems, but in 3.7 I had a similar issue, it seemed that my folder permissions had changed mid way through. I ended up putting the MicroSD into my Linux machine and completing the copy once I edited the folder permissions.

I just go my first Raspberry pi a few weeks ago, so I am no expert

never mind, was changed to work with a controller, not a keyboard. plugged my ps4 controller in and it worked right away.

@jimd0586 said in Mame versions and Gyruss:

This thread brings up a good question. FBA is for NEO Geo right? So can FBA run some MAMEs? I am confused. Some of the posts here suggest that FBA can run standard MAME files.

for the most part, when there's crossover, FBA will run things faster, but it's possibly less accurate.

FBA (and there are several versions on the pi) runs a subset of MAME roms. the full gamelists are on the wiki.

I had the same problem with my overclocked PI3 (retropie 3.7).
I think your problem is the same.

Remove your overclocking settings. Try. Yes, it takes about an hour to build. At the end add again their overclocking settings.
Cheers

@BuZz thanks, it's working now.

@PingSpike I followed the thread @HoolyHoo is linking to above a couple weeks ago and it works great. You need to use GPIO3 if you want to be able to use the same button to turn on the Pi from idle (connected to AC, but shutdown). Also, there is sometimes a delay (polling rate for background BASH script?) so you have to hold the power button in for a second or two before the system recognizes it, but it has never failed to shutdown safely.

I'd really like to get mholgatem's GPIOneer working on Jessie so I can get my volume up/down buttons working again--no delays, any command can be assigned to a GPIO button (or combination of buttons) and web-based config editor.

I don't think there's really a "fix" for L2 and R2, it's just something you kind of have to work with. Whenever you configure the triggers, it'll probably do a double entry. So it will do something like 3- in L2 and then it will fill in R2 with 3+ as well. You can either go into your joypad configuration located in /opt/retropie/configs/all/retroarch-joypads/ and straighten things out manually. Or you can wait until you're at the bottom of the configuration, and you can scroll back up with the DPAD and redo the entries that aren't correct by pressing A and trying again. It's mostly just a mild annoyance after you've done it a few times, but it's something that when it happens the first time, it can be frustrating to figure out.

Ok thank you

@kruuth
When in the config menu, try

Setup / Configuration Edit RetroPie/Retroarch configurations Advanced Configuration Manually edit Retroarch configurations /all/retroarch.cfg

Hey that's sweet.
Thanks very much.

Yes, as it doesn't check if a keyboard is plugged in or not

https://retropie.org.uk/forum/topic/297/failed-failed-to-start-usbmount-dev-sda-service/2

@bamsi found a work around for same problem with my ps3 controller. I just manually configured retroarch settings in the retroarch menu. Watch video at link https://retropie.org.uk/forum/topic/100/made-some-progress-on-2-generic-shanwan-ps3-controllers-via-bluetooth-on-pi-3-retropie-3-6

I got it working with another bin + cue :)