Goodbye fbalpha, welcome fbneo
-
@janderclander14 said in Goodbye fbalpha, welcome fbneo:
Does anyone encountered a similar problem?
I never heard of it. Does it maybe happen on specific games ?
@janderclander14 said in Goodbye fbalpha, welcome fbneo:
I'm using the latest fbneo binary,
You mean latest from sources, right ? I've no idea how old is the version if you are installing from binary
-
@barbudreadmon Yes, it happens on all CV1000 games and the behavior is deterministic for all of them. And yes, the binary was compiled on Jul 23, 2022 sources.
-
@janderclander14 sorry, i have no idea what's going on with your setup
-
@janderclander14 it seems like there was a similar problem talked about here. Try out the steps el rika did, maybe there's a glitch in the way the .fs file is saving threaded blitter options.
-
@dodonpachi this issue wasn't about performance and was fixed back in may
-
@janderclander14 I don't have any answers, just chiming in to say I can't replicate this either.
d712362159f1c7410fc862638e3cc3b2 ddpdoj.zip fdb4f4321a418b167a440abbb36c8ffb deathsml.zipBoth of these are running 59-60 fps on RPi4 (2 gb) in lr-fbneo latest binary (843db9f, compiled 2022-07-25), both on initial and subsequent launches.
I don't have my sound up so I can't comment on the audio.
I haven't touched the core options.
Maybe comparing verbose logs of before and after might give some insight. Are your global and system
retroarch.cfgfiles default? -
Thank you all for your answers.
Verbose logging for the first and second runs are identical and do not show anything strange. My only settings different from default are threated video = off and one lightweight crt shader. I tried enabling the former and disabling the later but the result is the same: only deleting the .fs file corrects the issue.
This is certainly a strange problem that I haven't encountered with neither other cores nor other games with fbneo.
-
@janderclander14 we did a bit of profiling, emulation is not supposed to be more demanding on subsequent launches
Do you still observe the same behavior (subsequient launch being slower) if you disable the dips "thread blitter" in core options ?
note: i don't expect the games to run at full speed even on 1st launch with this dips disabled, but what i want to know is if it could be some kind of threading issue. -
@barbudreadmon Thanks for looking at it.
I did some tests with the dip options. These are the results with Deathsmiles BL:
- 1st run (no .fs file) default core and dip settings: 57-59 fps
- 1st run disabling thread blitter: 51-54 fps
- 2nd run (with .fs file) with thread blitter disabled (saved from the first run): 27-29 fps
- 2nd run enabling again thread blitter: 30-33 fps
Enabling/disabling the speed hacks option has a similar influence in both runs (3-4 more/less fps respectively).
By the way, is there any option to prevent FBNeo from creating the .fs file?
-
@janderclander14 said in Goodbye fbalpha, welcome fbneo:
57-59 fps
57 seems low though ? It seemed pi4 users were reporting full speed using the right settings. Are you properly overclocking your pi4 and downclocking the emulated cpu ? Are you using some kind of ressource-intensive feature ?
If disabling threading didsn't change that behavior either, then it's clearly something wrong with your hardware/setup and not a core issue. Threading was the only possible cause of randomness on core's side.
-
@barbudreadmon said in Goodbye fbalpha, welcome fbneo:
@janderclander14 said in Goodbye fbalpha, welcome fbneo:
57-59 fps
57 seems low though ? It seemed pi4 users were reporting full speed using the right settings. Are you properly overclocking your pi4 and downclocking the emulated cpu ? Are you using some kind of ressource-intensive feature ?
For this test I used the default core settings, which include 100% core cpu. Downclocking it to around 40-50% gives nearly constant 60 fps across all games. My Pi is also overclocked to 2 Ghz and according to 'top' the emulation uses 99% cpu, with the remaining 1% split among other secondary linux processes.
Anyway, I understand that this looks like some problem on my side, but I'm completely lost at what to look at : )
-
Updated to the latest lr-fbneo, and for some reason Mushihimesama runs significantly slower all of the sudden. I haven't tested any other cv1k game to see if they were effected. Was something changed recently?
EDIT: Strangely enough, this phenomenon also exists in the latest version of lr-fbneo when played on my Windows PC... which can run the same cv1k games at full speed on current mame. Something clearly went wrong here.
-
@dodonpachi said in Goodbye fbalpha, welcome fbneo:
Updated to the latest lr-fbneo, and for some reason Mushihimesama runs significantly slower all of the sudden. I haven't tested any other cv1k game to see if they were effected. Was something changed recently?
I just compared with early june version, and they ran at exactly the same speed. The only 2 commits from the past 3 months were to reduce memory footprint, notably for runahead's sake (you can now run cv1k with no input lag at all on a powerful enough computer), and i can't see how they would introduce any performance regression.
@dodonpachi said in Goodbye fbalpha, welcome fbneo:
DIT: Strangely enough, this phenomenon also exists in the latest version of lr-fbneo when played on my Windows PC... which can run the same cv1k games at full speed on current mame. Something clearly went wrong here.
MAME was always faster on pc, because they use a x86 dynarec. FBNeo should still run fine on any decent computer though, dink can run this on his 12 years old computer without downclocking.
Sorry but i can't reproduce this, so i'm not gonna be much help. It doesn't look like a core regression.
-
@barbudreadmon I would write it off as an anomaly with retropie, if not for the fact that my Windows PC has an i5-2500 CPU. Final Burn Neo shouldn't be a problem whatsoever.
I tried disabling runahead to see if that would help, and it didn't. I'm at a loss here.
-
@dodonpachi said in Goodbye fbalpha, welcome fbneo:
i5-2500 CPU
Dink is using an i7-2600, which doesn't really make any difference since we are talking about emulation (no heavy multi-threading), so i can guarantee it run fullspeed on that without having to downclock the cpu, with ressources to spare.
Maybe your screen is not running at the proper refresh rate or something ? If you are using some kind of ultra-hd screen, make sure it's not stuck at 30hz for some reason, i see that a lot. Otherwise maybe check everything is ok with the usual performance tips.
-
@barbudreadmon Both mine and Dink's CPUs seem equivalent here, and leagues above the CPU in a Pi 4B.
In retroarch, I did see a setting along the lines of "force 60hz" turned off. I'll try it when I get home later, but I don't know if that will be it. The way cv1k games run on the rig is now as if it were on a Pi 3 or something--not only is it visually slow, the sound is incredibly choppy. Maybe this is a video driver issue? I'll have to poke around more.
-
@dodonpachi said in Goodbye fbalpha, welcome fbneo:
I did see a setting along the lines of "force 60hz" turned off
That's just a setting to replace original refresh rate by 60hz, it's not gonna change anything about slowdowns, especially since i think refresh rate is already set to 60hz for our cv1k emulation.
-
@dodonpachi also turn off the RetroArch Rewind feature. Your symptoms are similar to it being toggled on. Hope that's the issue...
-
@roslof That was it!!!! Thank you, I would have almost never guessed that!
-
@dodonpachi said in Goodbye fbalpha, welcome fbneo:
@roslof That was it!!!! Thank you, I would have almost never guessed that!
That's one of the first things mentioned in the performance tips i previously linked to you though, you didn't read them ?
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.