Goodbye fbalpha, welcome fbneo

sirhenrythe5th

@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?

barbudreadmon

@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.

sirhenrythe5th

Got it, thank you very much once again @barbudreadmon!

GreenHawk84

Hello,

fbneo doesn't appear to be doing well on Street Fighter 3: 3rd Strike.

I have a model 3B+ with default settings.

barbudreadmon

@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.

sirhenrythe5th

second this, runs great on a default Pi3B+

lostless

@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.

barbudreadmon

@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.

lostless

@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.

GreenHawk84

@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.

barbudreadmon

@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

GreenHawk84

@barbudreadmon

I am pretty sure I am clear on everything except maybe throttling. How do I confirm?

Lyle_JP

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.

barbudreadmon

@GreenHawk84 said in Goodbye fbalpha, welcome fbneo:

@barbudreadmon

I am pretty sure I am clear on everything except maybe throttling. How do I confirm?

I'm not too sure how to confirm it, but here come a tips about the pi3b+ : if your cpu go above 60° (which happens quite easily, having a good cooling solution is highly recommended on the pi3b+, i'm using https://www.amazon.com/dp/B01LWURJMI, the fan is perfectly silent), it will throttle to 1200Mhz, which is unacceptable for cps3 with FBNeo, a software workaround would be to rise throttle temperature to 70° by adding temp_soft_limit = 70 in /boot/config.txt.

@Lyle_JP said in Goodbye fbalpha, welcome fbneo:

SF III 2 used to run at 60 fps with no audio issues in widescreen mode.

It's still running at 60 fps here on the same fresh RetroPie setup.

GreenHawk84

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

@GreenHawk84 said in Goodbye fbalpha, welcome fbneo:

@barbudreadmon

It's still running at 60 fps here on the same fresh RetroPie setup.

Not really sure why yours would be any different since I do not alter settings and I recently fresh installed on a 3B+? I checked the frames on SFIII and I am getting 58.2fps with dips as low as 53fps. My core temperature is 55C, I use heatsinks on my chips. If there is any data you want to see from my setup let me know.

Darksavior

Pi3b+ stock speeds. No bt. No wifi. Fresh 4.5 fully updated. No shaders. 70c temp soft limit. Flirc case to cool. Fb-Neo binary with sfiii 2nd impact:
60fps with minor .5fps dips. Widescreen mode ~52fps.

UPDATE: with latest Fb-neo from source:
SFiii2: Widescreen mode ~53fps. No real change.

SFiii3: ~60fps. Dips to 59.1fps when doing supers.

GreenHawk84

Can confirm FBA2012 is running SF3 at 60fps with occasional 59.1fps dips. Seems way better than fbneo. Very odd since we should all have the same stuff.

Darksavior

deleted

GreenHawk84

@lostless said in Goodbye fbalpha, welcome fbneo:

@GreenHawk84 im running into the same issue since the update.

Well at least I am not alone on this.

barbudreadmon

@GreenHawk84 @Darksavior Sorry, i don't know how to help you guys, as i said sfiii2 run at a stable ~59.5 fps with widescreen mode for me, if you are using the same default retroarch settings than me then i guess the only difference would be the active cooling, maybe the power supply, and maybe the pi3b+ itself ? After all there has always been occurences of "bad" quality and "good" quality pi, mostly noticeable when you overclock them. Another thing to explore might be that i used retropie_setup.sh right after installing ? I ran update then manage package > core > retroarch > from source then manage package > main > lr-fbneo > from source.