No longer shows up in the updater, at least on Android.
Take a look again, it’s there now. I’d use FB Alpha or even mame 2014 however
Alright was just making sure
Why, what’s wrong with Mame2016?
2 Likes
MAME 2016 has some quirks last time I tried, that 2014 does not have (analog controls in some games as I remember).
FB Alpha ihmo is better integrated with libretro API, you can access board settings / dip switches in the Quick Menu --> Options easily for example. It’s also faster than MAME, and takes less space on your storage memory.
FB Alpha ihmo is better integrated with libretro API,
your point of view! I prefers a lot mame internal menu that quick menu. (my point of view) for storage point , you can build only drivers you want (eg a tiny target with neogeo+cps1+cps2+some game you want -> only few 20Mo)
Also, FB Alpha has the sane behavior on staying in the upstream releases. MAME cores are always in some random commit after such release, you may find compatible problems with big rom sets.
Obviously, the biggest difference between MAME and FBA is that upstream FBA is friendly to libretro while upstream MAME is unabashedly hostile. You have to make some concessions in that case because they can and will cause trouble and breakages whenever it’s convenient.
It’s not really a big deal, like I said (may be a problem only with BIG rom sets). I use MAME 2014 here for some games and it’s really good.
honestly i update when i can ,so can be few days after the released bump version and maybe my unknowledge of git merge upstream is the cause of this. i don’t know how to fetch upstream to a define commit , i just do git fetch upstream and git merge upstream/master and then fix conflict if any. if some one give me the correct syntax for fetch upstream to the right commit (bump version) I ll try next time with 0.186.
If you can get the hash of the commit (in github, if you look at the list of commits, there’s a button on the right to copy that commit hash to your clipboard), then you can do: git checkout [hash] and it will take you to that specific commit.
does it apply when we fetch upstream ? it"s what i do https://help.github.com/articles/configuring-a-remote-for-a-fork/ https://help.github.com/articles/syncing-a-fork/
That’s a good question…
This seems to suggest that you can: but I’ve never done it myself.
@rtype: you almost had it:
git fetch upstream
This fetches all commits from the upstream repo in your repo, but does not modify your current branch.
git merge upstream/mame0185
This merges the tag named mame0185 into your branch. This way you do not merge all commits that were pushed to the upstream since the tag. Hope this helps.
1 Like
Nice , thinks for tips I’ll try this next upstream release!
I’m trying to do this actually but ?
git merge upstream/mame0186 give me merge: upstream/mame0186 - not something we can merge
i think its suppose to be git merge upstream/master, i often do this when updating my fork–unless, this is different?
This is what I usually do , but since we want now to merge to de 0.186 tag (a not some commit later )
Anyone with git knowledge ? I’ve read about git cherry-pick but not sure about the syntax to merge the uptsream mame0186 tag to libretro master.
else we will have to merge as usual 7/6 commits up to 0186 tag.
Edit : Ok I’ve merged and it not what i excpected 
if someone with better knowledge of git want to redone this in a cleaner way just ask @Twinaphex to revert this commit:
https://github.com/libretro/mame/commit/a5dea22ad1cd871115fa9493a30d356438c46b31
and redone the fetch upstream/merge to this commit (mame0186) :
MAME 2016 is missing from the buildbot again as of 9/2017. I’ve started an issue: https://github.com/libretro/libretro-super/issues/535
1 Like