Was this core removed recently because it sucks (lol) or has problems?
Wondering because it’s the one i use. Haven’t noticed any problems but id rather not be sing a core that isn’t good enough to be included in core updater hehe.
Was this core removed recently because it sucks (lol) or has problems?
Wondering because it’s the one i use. Haven’t noticed any problems but id rather not be sing a core that isn’t good enough to be included in core updater hehe.
It’s still available to build from here, though: https://github.com/libretro/mame2016-libretro
I use mame2014 for Cave SH3 games, FB Alpha for everything else.
Hmm. MAME 2016 was MAME 0.174 … and current was also available (was 0.188 i believe) along side it. Why not just leave 2016 alone and let current be, well… current?
Where was MAME 2016 removed from? MAME 2016 still has its own github repository and ought to be available.
I can suggest several reasons it might have been removed if you’d like.
@markwkidd it’s not in some buildbot recipes while libretro-mame is, see here:
nothing new:
Thanks ensra
More characters
Its not been in the updater for at least a couple of months. After it got mafe a static core i remember some regression in the mame ui which made the core difficult to use.
My android romset is still .174 incase it comes back
i am not sure why it disappear from buildbot. Recipes are still there in libretro-super. @anon24419061 found that there was a mistake in the url of the recipe and fix it. Btw it build fine “by the hand” the issue is just with buildbot recipe.
For memory mame 2016 is mame 0.174 with ui / aspect regressions fixed. It is also the last mame building fine for Android api19 working on 4 and 5 device. It s why we keep it and create a 2016 core.