consider to use a NAS if you have tons oft ROM data.... Whatever you want :)

@Floob
Ok so I got an old MicroSD Card to install RetroPie on, Flashed my 8Bitdo Controllers back to 1.68 and started fresh, everything worked fine though a couple tweaks had to be made to the es_config as ES would not associate the mapping to the "a" button correctly. After doing this I copied the "all" to my desktop, swapped back to the old RetroPie and deleted everything that "wasn't" in the new setup, then proceeded to copy those files over and verify all the configs looked correct yet still no dice.

I finally said screw it, copied over the Gamelists and downloaded images and just reformatted the card and started a new install, as of now both controllers work fine (with the exception of MAME) registered on 1.68, So why i never did solve the issue with the old setup (must be a config file somewhere else on the system we simply aren't accounting for) The problem has been resolved by starting over. I have been careful not to mess with the settings menu or do any sort of updates to prevent it wanting 1.69+ to function properly as it did last time,.

@kaitlin4599 yep it runs just fine. Just replace the doom wad with the chexquest wad. Eventually the wad selector will be improved so you don't have to manually change things

I found this guide for you in French:

It's a video guide so it's easier to follow. I hope this is going to help you out.

On the pi sd card you need to put your roms in their correct folders at /home/pi/RetroPie/roms

@edmaul69

Yeah I did a bit of reading mate. I'm a noob with all this but looks like I'm sorted now.

@bigkurz

For MAME specifically, that setting resides in the mame.ini file. However, I've never been able to successfully locate that file in RetroPie or even discover where it could be put manually if need be. Perhaps someone can shed some light on this, but when located you'll want to look for the autosave option and change the 0 to 1.

RetroArch itself also offers this feature, but it will affect the rest of your emulators as well unless 'Configuration Per-Core' is enabled. The 'Per-Core' option is not to be entered into lightly as it can cause it's own set of problems, so it is generally not advised. Either way, that setting can be found at /opt/retropie/configs/all/retroarch.cfg. You'll want to change both savestate_auto_save = "false" and savestate_auto_load = "false" to "true".

@why Please format your posts when posting logs / configs

https://retropie.org.uk/forum/topic/3/read-this-first

I guess the question is then that if I have modified or copied files to locations such as /opt/retropie/emulators/retroarch/shader (which isn't a path that a Samba share can see and is located on the USB HDD not the SD Card) how do I make sure this is all backed up aswell??

I'm probably wrong as I am a Linux moron but I thought that when I followed the instructions here https://github.com/RetroPie/RetroPie-Setup/wiki/Running-ROMs-from-a-USB-drive that it placed a lot of configuration settings on the USB HDD that can't be copied with the Samba share??

For example, I know I have made changes to files such as /etc/emulationstation/es_systems.cfg which I assume are now located on the USB HDD but I cannot see these files through the Samba share. How do I backup files such as this??

@ruxton_bruce Yes, that works too, but it can come up again in another libretro core (like lr-fba-next) and you would have to add it to that config too. I was suggesting it for ALL.

@Belum

I was just about to recommend checking to see if your Raspberry Pi was located atop an ancient Indian burial ground, but I couldn't remember if you're supposed to walk toward or away from the light to troubleshoot that problem.

@Riverstorm thanks i'll take a look

Something like this:
http://alexba.in/blog/2013/01/06/setting-up-lirc-on-the-raspberrypi/

There are alot of tutorials on how to set lirc with an infrared remote in a linux system, you just have to google it.

Mine works perfectly fine. Only keyboard i own besides my very mini bluetooth one.

@meleu Hello:

Yes I agree. The temptation to do a script update is so alluring though!

I got the desktop version of RetroPie re-installed and working just fine. I think I will steer away from clicking the update scripts options for awhile.

Thanks again,
BC

@dankcushions said in Some FBA roms not working in latest build of Retropie/LR-FBA-next?:

fba-next recently got updated to a new set, with a new neogeo.zip, which might explain your problem.

@dankcushions and @Floob you nailed it. I actually had a hunch that it might be my neogeo.zip. I had all the right files in the neogeo.zip, but I found a complete FBA .2.97.38 romset (I previously just downloaded some FBA roms from website, still the correct version though), and looked at it's neogeo.zip.

When I placed that neogeo.zip file on the pi3, everything worked! Problem solved. I drilled down even further through trial and error, and found the bad file in my old neogeo.zip was "sm1.sm1". If I replaced it from the new neogeo.zip, that solved it as well. So frustrating, but I figured, as did @dankcushions and @Floob, that it had to be something with the neogeo bios....

Thanks guys, truly appreciate the help!