FBA new core option

[barbudreadmon]

@voljega said in FBA new core option:

I confirm pgm and cave games are clearly not running at full speed on overclocked pi2 nor non-overclocked pi3.

It's a bit better at least for pgm on pi3 but still not full speed

Image is fine but sound cracky/lagging

Not for me xD
I did a pull request to recalbox's fbalpha makefile, i hope it will help.

[barbudreadmon]

I ran htop while running a few of those games, one of the core topped at 90% of load while the other 3 were idle (i don't think i can do something about this), i suppose it could cause speed issues if your system is at stock frequency or if you have something running in background. Do you know what was the last version of fba where you saw pgm/cave games running at full speed on your raspberry ?

[Substring]

@voljega fba was "better" on recalbox 3.3.0-b17 ? or 3.2.11 ?

3.3.0-b17 uses commit 39a6baafc5b80fda617fe0d72aa8747fdea5f9e2
3.2.11 uses commit c6b13e90127ec9c6c21cfd19d95da3b6cf296cd6

[barbudreadmon]

Actually, none of those games run on Cave hardware, too bad that's the one i spent an hour checking xD. I'll check Pgm tomorrow.

[voljega]

@subs I don't think it was better before, those games never worked at full speed for me.
I'm there since Recalbox 3.2 I think

[barbudreadmon]

@voljega said in FBA new core option:

@subs I don't think it was better before, those games never worked at full speed for me.
I'm there since Recalbox 3.2 I think

By the way, what's your raspberry pi 3 clock settings exactly ? i'm backporting some old fba code and i need to test if some of it would solve your speed issues.

For reference, pgm games have no issue at all for me with those settings :

dtparam=audio=on
dtoverlay=sdhost,overclock_50=84
arm_freq=1350
gpu_freq=550
over_voltage=5
sdram_freq=550
sdram_schmoo=0x02000020
over_voltage_sdram_p=6
over_voltage_sdram_i=4
over_voltage_sdram_c=4
gpu_mem=384

[voljega]

@barbudreadmon I have not modified at all the clock settings on my pi3

[barbudreadmon]

@voljega ok, i'll use stock settings to test my speedhacks then.

[Substring]

@voljega i remember people saying PGM and psyko games running slow on a pi2, but they looked (almost) fine on my pi3

[barbudreadmon]

@subs As i said, they run totally fine on mine, never saw them under 59.9 fps. But perhaps my overclock settings are agressive, and my system is better optimized, so i'll try to lower the requirements with a few speedhacks.

[voljega]

OK I must have mixed something a little because my test results are better than what I remember on PI3 :

https://docs.google.com/spreadsheets/d/1F5tBguhRxpj1AQcnDWF6AVSx4av_Gm3cDQedQB7IECk/edit#gid=32876421

Thoase are tests with non overclocked Pi3 and overclocked Pi2 (this one overclocked only through the ES menu)

[barbudreadmon]

By the way, with latest commit, every control issue should be solved.

[gkralicek2]

FYI, PGM games on my OC Pi3@1400 run full speed (59.9-60fps) exception made for the 2 most recent titles released in 2005 : "Spectral Vs Générations" and "The killing blade Plus" which perform only around 54-57fps max during gameplay.
The same games executed on my OC Pi2@1100 display around 50-54fps max with slightly choppy sound everytime the framerate drops (42-46 fps only for Spectral vs Generation & The killing blade plus with almost constant choppy sound during gameplay)

All those framerate tests have been performed using earlier versions of FBA_libretro core (v0.2.97.30 and v0.2.97.34) which appear to be less resource-consuming. The same tests run on versions 0.2.97.37 or 0.2.97.38 of the FBA core result in a drop of approximately 7% in performances compared to earlier releases, thus degrading a bit more the experience :=(

[barbudreadmon]

@gkralicek2 what about v0.2.97.36 ? "The killing blade Plus" performs around 57-60fps for me with v0.2.97.36, and my OC is lower. What's more, unlike porting v0.2.97.30/34 code to current fba, porting v0.2.97.36 code to current fba is something within my skills.

[voljega]

@barbudreadmon said in FBA new core option:

By the way, with latest commit, every control issue should be solved.

What do you mean by that ? In which game for instance ?

[paradadf]

@voljega there are a lot!

For example:

• Ace Attacker (FD1094 317-0059) - no button working
• Angel Kids (Japan) - impossible to go left
• Arkanoid - Revenge of DOH (World) - the sensitivity is super high (?)
• Asterix (ver EAD) - player 2 can't access the game
• Bikkuri Card (Japan) - payout screen can't be skipped
• Bomb Bee - the sensitivity is super high (?)
• Bullet (FD1094 317-0041) - only coin and start button working
• Caliber 50 [No sound, imperfect inputs] - directions don't work
• Check Man - only coin button working
• Chance Kun (Japan) - only coin button working
• Cutie Q - the sensitivity is super high (?)
• Dark Planet [Dial doesn't work very well] - directions not working properly
• Deroon DeroDero [No sound] - only directions working
• DownTown / Mokugeki (Set 1) [No sound, imperfect inputs] - directions not working properly
• Excite League (FD1094 317-0079) - only coin and start button working
• F-1 Dream [Game is bugged, use the bootleg instead.] - weird directions on turns
• Ganbare! Marine Kun (Marine 2K0411 JPN) - only coin button working
• Gee Bee - the sensitivity is super high (?)
• G.I. Joe (World, EAB, set 1) - coin to pass black screen, but impossible to select
• Heavy Barrel (US) - directions nor working properly
  etc...

Maybe some of these aren't directly related with the input system, but you get the idea

[voljega]

@paradadf yeah but i assume each one of those is a different issue or so, how is it possible that they would be all corrected in a instant ?

[paradadf]

@voljega I was just mentioning the first ones from my list which have some kind of input problems. And as I said before, I'm not certain that all those were directly related to the input handling, but some for sure. I can't differentiate the root of the problem

[barbudreadmon]

@voljega not really different issues, most of them were missing inputs because the old input handling was hard to maintain, i rewrote it.

What we were doing before :

• Compare button's display name with a list of 305 display name we indexed
• Use the first one matching, adapt it through core option
• If no match, skip the button

What we are doing now :

• Use the button's normalized name, there is around twenty of them, and, unlike display names, they are programatically understandable.
• Get the number of "fire" button (= buttons used in gameplay) used in the game, if lesser than or equal to 4 "fire" button tell if it is a neogeo game or not, if greater than 4 "fire" button tell if it is a street fighter or not
• Use a different mapping for each of those 4 cases, adapt it through core option

NB : I didn't debug the analog inputs yet, but that's a different issue.

[voljega]

@barbudreadmon Cool ! I'll retest everything not working when it's released then