Goodbye fbalpha, welcome fbneo
-
@shavecat said in Goodbye fbalpha, welcome fbneo:
Is it better then the lr-mame2003-plus ?
That's 2 different emulators with support for different games (even if they have a lot in common), i would say they are complementary. If you are looking for accuracy, savestates support, funky features using those savestates (netplay, readahead, rewind), and maybe other funky features like RetroAchievements, FBNeo/FBAlpha is usually the recommended emulator over old mame cores when usable (i.e when the game is supported, has no known issues, and your device is able to handle it). Furthermore, reported issues are generally fixed quickly.
@shavecat said in Goodbye fbalpha, welcome fbneo:
how do i instaal Fbneo ?
That kind of question when the answer is 2 posts above is seriously depressing.
-
@barbudreadmon hello. thank you for great work. now i see trouble in RaspberryPi 3A+
i upgrade RetroPie and see Fbneo - him work on Zero and B3+ - and cant work Pi 3A+
Need help for play my loved games ) -
@SergioPoverony Please open a new topic and provide the info requested in https://retropie.org.uk/forum/topic/3/read-this-first. A log file (
/dev/shm/runcommand.log) would be useful. -
-
Where do I get a clrmamepro dat for the version of fbneo installed by retropie?
I see in the first post that there is a link to the very latest versions of fbneo dats on github, but assume these will be for the very latest fbneo code on github.
Retropie fbneo compiled binaries are likely is a bit behind (understandably). Where are the dats for the binary release of fbneo which is installed by retropie?
Thanks. -
@pi2user open RA menu, copy commit in the bottom-left corner, replace it in the following url :
https://github.com/libretro/FBNeo/tree/<copied_commit>/datsHowever, keep in mind that using binaries instead of sources is a bad idea :
- there is absolutely no guarantee that the binary version isn't plagued by a major bug, since they are done with arbitrary commits and without consulting me first, you won't get support though.
- you won't benefit from improvements, fixes and new stuff added daily.
-
@barbudreadmon Thanks for the answer, that's what I was looking for.
Do you plan on tagging some commits as a 'release' at some point? This could help the retropie team decide on when to make a binary and then they could provide support and a link to a dat based on a version that stays the same for a period of time.
For end users, the release system does work really well.
Apologies in advance if this has been asked and answered elsewhere. -
@barbudreadmon just to get it right: i just updated from source yesterday and realized that there are more improvements (thank you at this point for your great work!).
As the version is permanent on "0.2.97.44", can you say that one should update every two weeks or so as you mentioned in the post above that "you won´t benfit from imrpovements, fixes and dew stuff daily"Or the other way around: will there ever be something like 0.2.94.45 or will this .44-release be worked on for a long time but never change in name / version?
-
@sirhenrythe5th i would recommend updating regularly from sources and make a report if you find any issue (if it doesn't require a major rewrite, it generally get fixed in the next 2 days)
Technically, current code is still pre-0.2.97.44, there was no official 0.2.94.44 release yet. There will be official releases in the future, just not sure when or if we'll keep the current versioning.
-
Got it, thank you very much once again @barbudreadmon!
-
Hello,
fbneo doesn't appear to be doing well on Street Fighter 3: 3rd Strike.
I have a model 3B+ with default settings.
-
@GreenHawk84 said in Goodbye fbalpha, welcome fbneo:
fbneo doesn't appear to be doing well on Street Fighter 3: 3rd Strike.
Please be more specific, it is running perfectly fine for me.
-
second this, runs great on a default Pi3B+
-
@GreenHawk84 im running into the same issue since the update. Sf iii feels like it’s running ok, and most probably will not notice, but it is running slower at about 55-60fps with some minor audio pops and clicks. It’s trying, but the accuracy updates just push the pi a tad over the edge. I switched to fba2012 and it’s running fine on that.
-
@lostless i'm not getting those slowdowns on my pi3b+ with a fresh retropie, and it's running at standard clock, i'm not even using any overclocking (even though it's perfectly stable at 1475Mhz), are you using the latest fbneo from sources ? I improved performance in the input code last month (half of the improvement depends on having a recent retroarch 1.7.7 though, and retropie seems stuck with 1.7.6).
Anyway, the following things come to mind :
- some kind of intensive shader (i always use simple scanlines)
- i heard bluetooth can take a toll on the system (i'm always using wired)
In this situation and if you don't care too much about accuracy, i guess using fba2012 for cps3 is mostly fine as long as you don't play jojoba; otherwise i would probably consider using fbneo with frameskip, it's barely noticeable.
-
@barbudreadmon I’m using a the binary in RetroPie for fbneo. I’m always afraid to update fb, as performance typically goes down in the arcade emulation scene. I’ll give the latest build a try. If I’m still having issues, fba2012 is doing just fine.
-
@barbudreadmon said in Goodbye fbalpha, welcome fbneo:
Please be more specific, it is running perfectly fine for me.
Yes, the game is running slower and the audio has issues (crackle sounds). I just updated fbneo from Source, and the same issue occurs.
-
@GreenHawk84 said in Goodbye fbalpha, welcome fbneo:
Yes, the game is running slower and the audio has issues (crackle sounds).
As i said, it's running at a stable ~59.5 fps here with a fresh retropie setup, no customization/overclocking at all, so there is something slowing it down on your setup. All the things you can try :
- should be a no-brainer, but don't use readahead/rewind with cps3
- try overclocking (shouldn't be necessary but can give the little boost you need)
- don't be greedy with shaders, scanline is perfect for a raspberry, performance-wise and rendering-wise
- avoid bluetooth if you can, over the years i've seen various people saying games are stuttering with it
- make sure your cpu isn't throttling, it might happen with a bad power supply or if your pi3b+ is too hot
- last resort is the frameskip option, as i said it's barely noticeable
-
I am pretty sure I am clear on everything except maybe throttling. How do I confirm?
-
I can also confirm a massive drop in playability on CPS3 games in FBNeo after updating less than a month ago. SF III 2 used to run at 60 fps with no audio issues in widescreen mode. Now, it can't play it's own attract mode without obvious audio stuttering and slowdown. I'll be rebuilding with a 4.4 image soon which I will then upgrade to 4.5 without touching FBNeo. At one point I think someone was working on a Final Burn Alpha 2016 fork. Sure wish it had happened.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.