Goodbye fbalpha, welcome fbneo

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. ;)

GreenHawk84

@Riverstorm some bad stuff happened when I started deleting and replacing .cfgs. My controls for arcade games are gone yes, but also I had to go in and replace the values in es_input since Emulationstation menu controls also went out. I deleted the arcade .cfg but I didn't notice any default file to rename. I definitely put myself in a new mess. I also think even though I defaulted my main retroarch.cfg, SF3 is still running less than good. I don't feel like I should keep posting in this topic regarding my new .cfg issues lol.

Riverstorm

@GreenHawk84 - Ok, ah well, yeah some of the files may not exist if there is no ROM level overrides saved such as sf3.cfg or sf3.opt.

I am a bit surprised you lost the ES controls as they reside in /opt/retropie/configs/all/emulationstation/es_input.cfg. Basically a completely different file.

The arcade.cfg would apply only to ROMs in the arcade folder where as fba.cfg would only apply to those in the fba folder. FinalBurn Neo.cfg applies to either regardless of ROM location.

Hopefully you renamed them and it should be pretty easy to get back to where you started. I think it was at least worth a shot to try even if it didn't turn out favorably. I always seem to learn something new whether receiving or trying to help with things.

GreenHawk84

I went ahead and ordered a new 3B+ so see if placing my current SD into it will rule out a hardware issue.

I went in and deleted .cfgs and tried to default everything back, what a pain in the ass that was, I am not even sure if I did it right. Worse comes to worse, I create a brand new image and test on both 3B+ boards to rule out something within my current image. I really do not want to start over again.

dankcushions

@GreenHawk84 i can't imagine a hardware issue would ever manifest in one game(s) playing a bit slower. i can almost guarantee it is your configs being all jacked up, which seems the case from your last few posts. very easy to reinstate if you follow the above advice. there will be an rp-dist master version in every folder, but i fancy you got yourself into a mess that no-one will be able to truly fix without seeing the whole structure.

i advice starting a new thread and uploading all the relevant config files and screenshots of the folders in question. this is very off topic now.