Goodbye fbalpha, welcome fbneo

barbudreadmon

@IanDaemon said in Goodbye fbalpha, welcome fbneo:

when I upgraded to FBNeo I lost the ability to play Food Fight

The game is working fine so i guess you are using a bad romset.

Riverstorm

@IanDaemon - Food Fight (foodf) should be working in mame2003 and mame2003-plus. With mame2003-plus I think markwkidd created a "bootstrap" which basically generates the .nvram file on the fly during game launch or it hangs and looks broken. It's seamless to the user. I don't remember if mame2003 has the bootstrap code but I know you can copy the .nvram file over from m3plus to 2003 and it works fine.

There's several games that need .nvram files or they don't boot correctly so I keep clean copies with the ROMs for new setups. I've never needed to do that for FBNeo though as they have always just worked.

barbudreadmon

@Riverstorm said in Goodbye fbalpha, welcome fbneo:

I've never needed to do that for FBNeo though as they have always just worked.

Because on latest mame romsets (the ones FBNeo uses), the nvram is part of the romset for games that need it.

Riverstorm

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

Because on latest mame romsets (the ones FBNeo uses), the nvram is part of the romset for games that need it.

@barbudreadmon - Thanks for that it makes things a lot easier! :)

GreenHawk84

Okay so upon replacing the generic power supply with an official Raspberry Pi power supply, it seems the game runs a lot better than before. I still think that FBA2012 is working a little better, but apparently I was using a bunk PSU.

barbudreadmon

@GreenHawk84 said in Goodbye fbalpha, welcome fbneo:

apparently I was using a bunk PSU

Yeah, hardware defect was the most likely suspect from the beginning, assuming you were really using default settings.

@GreenHawk84 said in Goodbye fbalpha, welcome fbneo:

I still think that FBA2012 is working a little better

Use whatever you want, as far as i'm concerned the pi3b+/FBNeo/cps3 combination is perfectly smooth on my side, and i prefer accurate emulation when available.

GreenHawk84

False alarm, my 3B+ still runs SF3 poorly. Everything else is fine. I have installed fbneo from source multiple times, defaulted my settings in retroarch (even though I never changed anything) and even turned off my simple overlay of side art for the game. Nothing works for fbneo (SF3), but fba2012 is pretty nice. I think I am going to give up on this for now, maybe something will improve for me later.

dankcushions

@GreenHawk84 how did you default your settings? there’s a right way, and a wrong way...

GreenHawk84

@dankcushions I just went into the Retroarch UI and selected the option to reset.

dankcushions

@GreenHawk84 that’s the wrong way, hence you won’t see it in any of our docs. it gives you retroarch defaults, which are very different from retropie defaults, and probably include rewind, and a bunch of other non-performing features.

right way: https://www.reddit.com/r/RetroPie/comments/7gupd2/how_do_i_reset_retroarch_settings/

but tbh, now that you used that option i don’t know what your .cfg setup will be like. you’re on your own...

HACHI201

My fbneo can't run, he will return to the selection interface, my device is Raspberry Pi 3b+, do you know how to solve it?

mitu

@HACHI201 open a new topic and provide the information asked in the Read-me-first topic, linked at the top of the forum.

barbudreadmon

@HACHI201 said in Goodbye fbalpha, welcome fbneo:

do you know how to solve it?

Imho, usual "i didn't bother reading the arcade documentation and don't know what's a romset" crap.

sirhenrythe5th

@barbudreadmon 😂👍 full ack!

GreenHawk84

@dankcushions if you think my .cfg is jacked, do you have a copy of a default .cfg I can just replace mine with?

Riverstorm

@GreenHawk84 - Just go to your fbneo folder and rename your current retroarch.cfg file (for backup, troubleshooting or you can delete it). I like to keep it for a while by adding .bak to the original name or my initials or whatever.

Then copy the retroarch.cfg.rp-dist file (it should be located in the same folder) and rename it to retroarch.cfg. This should restore default settings for the core but keep your original settings handy for reference. It usually works best if you exit ES back to a prompt while doing it or that may cause a potential issue too.

There may still be some global settings that are potentially causing issues but the core settings are usually an easy reset. Also you could check ROM level settings if you use them.

GreenHawk84

@Riverstorm I will try this, thank you. Is there a global .cfg I can use to replace mine? There has to be a way to default everything without re-imaging.

dankcushions

@GreenHawk84 there should be an rp-dist version of the global retroarch.cfg, too. check in /opt/retropie/configs/all/

Riverstorm

@GreenHawk84 - It's located where @dankcushions pointed out here /opt/retropie/configs/all/retroarch.cfg.rp-dist. The same steps should work but it might be beneficial to have a PuTTY or serial connection to the Pi also.

You should be able to navigate ES once you reload ES or reboot the Pi but all game input settings will be lost if set globally (which they usually are) as well as any other 'global' default changes. Basically you'll need to reconfigure all your settings and inputs like a new setup. The global retroarch.cfg is definitely more ruinous to your setup than the core one. :)

I would make a backup of that particular retroarch.cfg file and use something like WinMerge to compare what lines have changed or use it to restore later if it doesn't correct the issue. It's about 30k in size or 900 lines.

Riverstorm

@GreenHawk84 - A couple of other things you could try.

Rename /opt/retropie/configs/all/retroarch-core-options.cfg and launch a game. That should generate a new core options file with the defaults for testing. The file stores settings for all cores so you'll want to restore it later.

You could also check the folder /opt/retropie/configs/all/retroarch/config/FinalBurn Neo and rename or delete FinalBurn Neo.cfg, fba.cfg (and/or arcade.cfg if you're using Arcade). They are the core, directory and game overrides if present might be causing your issue.

Also rename or delete any game related settings that would be named <game>.cfg and/or <game>.opt. Each game may have both files.

Might as well check for <game>.zip.cfg files too just in case, usually located in the ROMs folder. Rename it to stop any overlays, backdrops, etc. from loading.

You sure imaging a spare card with a new image wouldn't be easier for a quick test. ;)