Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

  • Hi all, I would like to see a FBA 0.2.97.43 repository is well. Keeping the latest FBA would be good for people that don’t want to change to FBN and don’t want to keep updating their rom sets. I understand that you can just opt to not update your system, but what if you are building a new system?


  • @Evert said in FB Alpha 0.2.97.43 Pre-Compiled Version:

    Hi all, I would like to see a FBA 0.2.97.43 repository is well. Keeping the latest FBA would be good for people that don’t want to change to FBN and don’t want to keep updating their rom sets. I understand that you can just opt to not update your system, but what if you are building a new system?

    Exact! You centered the problem perfectly. It is not a question of updates, everyone can do it, but the maintenance of the same is the problem, especially if at any moment 50 roms change and if you update the system by mistake you go crazy to bring everything back as it was before. In my opinion, the romset mode used for mame is and still remains the best way to maintain an efficient and error-free system.


  • @dankcushions said in FB Alpha 0.2.97.43 Pre-Compiled Version:

    IMO it's not a good idea. it increases the support burden of the team having to support (or decline to support) older versions of the software. also, FBAlpha is now final burn neo due to a tricky internal issue so i think it's better to move on from these old versions.

    it's really not a challenge to obtain the latest final burn neo romset, and if you don't want to have to get it, just don't update? :)

    In my opinion, having a repository with precompiled files for old versions can only help to create "clean" romsets. There wouldn't be much to do, we're talking about a dozen files if we really want to create them from pi0 to pi4.


  • @shift said in FB Alpha 0.2.97.43 Pre-Compiled Version:

    especially if at any moment 50 roms change

    it never happens, apart from totally new romsets, maybe 10 romsets every 3 months get some changes, considering the work to redump a game, the very concept of having 50 arcade games redumped at once is totally unrealistic, and it's not as if it was done for fun, it's done to fix issues, see comment for the last change of that kind we did (https://github.com/finalburnneo/FBNeo/commit/dff89e148e4daeda61fbf3231ebcc976a1d6ed12) : the game was previously broken in level 3.

  • Global Moderator

    @shift said in FB Alpha 0.2.97.43 Pre-Compiled Version:

    In my opinion, having a repository with precompiled files for old versions can only help to create "clean" romsets. There

    On the contrary, it will add more confusion for the users (which one do I get ?), make it very difficult to support the numerous cores (which one of the 5 cores are you using ?) and add even more confusion in the ROMset selection. Not to mention that - as @barbudreadmon said - bug reports for already fixed games would probably add more noise and would negate the work put on by the FBNeo developers.

    It will not happen in Retropie, but feel free to 'freeze' (backup) your version once in a while if you find it useful.


  • So we are having lots of problems with piFBA and FBA2012? Don’t see many posts with regards to issues or requests for help on those cores. Having an FBA2017 for 0.2.97.43 would be no different.

  • administrators

    @Evert feel free to manage your own versions then?


  • @Buzz, I was replying to the comment that it would add to much confusion. I disagree with the confusion part, hence my comment. I also don't think that there should be a repo for .41 .42 and .43, but an FBA end of life repo at .43 would be cool.
    I would assume that since the repository already existed, there would be no extra workload to manage or maintain this as there is nothing to update. If there is additional work then no worries, let's not do it. But, that was not the reasoning for not doing it in the above comments.


  • @Evert First of all, there has always been confusion because of fbalpha2012 (and its neogeo/cps1/cps2/cps3 forks which are just trimmed version of it), for years fbalpha2012 issues ended up being reported to fbalpha repository, making me lose my time trying to reproduce them while they were actually fixed long ago, and while the name change stopped those bug reports from happening on the github repository, it's still happening sometimes on discord & forums. In the first place most of those people using fbalpha2012 & reporting issues about it are just confused and don't even know there is a better version of this core. The fact retrogaming distribution are still using a "fba" folder for every fb-related emulator makes things worse, because when someone says "fba" you never know if he is speaking about pifba, fbalpha2012, or fbneo. So adding more confusion with a fbalpha2017 core ? Easy for you to say since you won't deal with the aftermath, but no thanks.

  • Global Moderator

    @Evert said in FB Alpha 0.2.97.43 Pre-Compiled Version:

    I understand that you can just opt to not update your system, but what if you are building a new system?

    back up your lr-fbalpha.so binary i guess.

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.