@buzz Hi Buzz, just updated from source and it's all fixed. Thank you very much. And twinaphex for merging it as well, of course.

If you require 2 players with joystick and up to 8 buttons on each control (equivalent to SNES controller) you could hook up directly to the gpio using mkarcadejoystick module that is in the drivers in Retropie.

I have 2 cabinets using this system.

@mattyl42 hook a keyboard up to the pi and press f4 in emulationstation. It will kick you to the commandline. Type:

sudo nano /boot/config.txt

After you make your changes press ctrl +x and then y to save.

@corax i am pretty sure you will have some troubles with some packages, but you can try. However 14.04 is no longer officially supported or tested.

@mitu thanks very much will check those out

@edmaul69 My Raspberry Pi only has a PS3 controller paired with it, no keyboard or mouse, so that's troublesome for me. I'll just have to keep MSX emulation on the PC for now. :'(

Just to add a bit of info, I had this problem and @herb_fargus helped me fix it by telling me to try the enable/disable (which worked well). Thanks @buzz and @herb_fargus!

Link to my post in case there's any useful info there: https://retropie.org.uk/forum/topic/12750/01_retropie_copyroms-seems-broken-won-t-sync-bios-and-configs

@hank-scorpio

How do you have the controls attached to your Pi, are they connected directly to the gpio or is there a usb interface of some description?

Also, you should check out the read this first link at the top of the forum pages (https://retropie.org.uk/forum/topic/3/read-this-first) and complete the information requested in there in your post.

It's the controllers fault. Open it up and clean the button contact pads.

Yes, I can confirm that a rebuild of lr-fceumm worked. Thank you for taking a look at it.

Okay. Sorry, I misunderstood. My reading comprehension is really lacking, today.

When I paste the requested two lines into the terminal, the system jumps into running the first line before it accepts the second one. So I'm seeing the entire 50-udev-default.rules document in the terminal. Not sure whether the second line, which isn't being run, was intended to refine the command that does run, or what.

Here, at any rate, is the entirety of my 50-udev-default.rules. Complete with, erm, a typo as the pastebin paste title. Erm. https://pastebin.com/EfLAKAWX

If that isn't what you needed, let me know how to give you what you want and I'll do my best.

@meleu Hey there, sorry for the delay, came back from work a moment ago!

retroarch.cfg
es_input.cfg
8Bitdo NES30 Pro.cfg
DragonRise Inc. Generic USB Joystick.cfg

Thank you, btw I tried again tonight and I have the same issue!

ok,

i forget to enable ssh on the "new" 4.2 iamge... now the 17.3 version starts :)

here is the log from 4.2

http://paste.debian.net/984997/

thank you for your help!!! (i dont now why 17.3 starts now but it works :) )

@gtbfilms Bummer. The loss of shader was definitely a result of swapping out old for new configs. You can add a shader configuration line like I did above in the all/retroarch.cfg or like I did in the arcade config folder.

As for sound, I would be surprised if Retroarch configs are to blame for that, especially since it still worked in lr-mame2003.

@dankcushions aah thanks so its just waiting for me now haha

By the way, video signal on cps2 arcade machine was indeed 16:9, but the rendering was on a 4:3 screen. Rendering cps2 games as 16:9 is a bug, it was fixed on lr-fbalpha in late 2015, and was backported to lr-fbalpha2012 a few months ago.

About using the old lr-fbalpha2012 because you got the wrong roms, why not update your roms instead ? If you buy the wrong tire for your car, do you buy a new car or do you go back to get the right tire ? I can understand using lr-fbalpha2012 on a raspberry in a few specific cases (i'm mostly thinking about svg and killbld here), but lr-fbalpha is overall better because a lot of bugfix and compatibilty was added in the last 5 years.

@mitu Okey thanks for the reply :) i´ll give it another try