Ok for font i only re-enable old font , we have to check if the behavior is the same with mame 0.182 .as is the same mod for crash i will look at later maybe this week-end.
BTW, i finally sucess to build mame2014
Ok for font i only re-enable old font , we have to check if the behavior is the same with mame 0.182 .as is the same mod for crash i will look at later maybe this week-end.
BTW, i finally sucess to build mame2014
Thanks r-type, I’m going to test it now and will post my results here later.
r-type, I did some more tests this weekend with both MAME2014 and MAME2016 cores, here are the results:
MAME2014: it doesn’t work. Every game crashes upon start and when I try to load just the core, it does nothing. It’s the same results I had with the latest 0.181 core built for more modern Android OS. Here’s the LOG, so you can see what’s going on with this core:
rcoltrane.50webs.com/Log_2017-01-29_15-07-40-mame2014-crash.txt
MAME2016:
The OSD menus are improved, but now the effect of missing lines is inverted. Now, only the 1st line doesn’t display its value on the right side of the screen, while all the rest is ok (go figure ). However, the Dispswitch screen is working perfectly now with all the games I have , so this issue is solved.
Some games stopped working and crashes when I try to run them. From the games I have, the ones that crashed are: blstroid (Blasteroids), mk (Mortal Kombat), mk2 (Mortal Kombat 2) and mk3 (Mortal Kombat 3. All the other games I have are working fine. Here’s the LOG file of the mk2 crash, maybe it helps to understand why these specific games stopped working:
rcoltrane.50webs.com/Log_2017-01-29_14-46-35-mame2016-crash-mk2.txt
These games are working fine with the older 0.174 core, so it’s a new issue that appeared within this new core. If you need LOG files for each game I can provide them, just let me know.
One final thing I would like to comment is that I noticed that the previous MAME2016 core (older) has a bigger size that the one you are compiling now. Here’s a photo of the sizes of the cores:
rcoltrane.50webs.com/mamecoressizes.jpg
The ‘mame_libretro_android.so’ file is the old 0.174 core and the ‘mame2016_libretro_android.so’ is the new one you are compiling now. Why are the sizes so different?
Thanks!! RC
Mame 2014 and 2016 are now back in updater compiled with ndk10 , so update you core!
For mame2014 your log show Failed to open libretro core: “/data/data/com.retroarch/cores/mame2014_libretro_android.so” update the core with updater will solve you problem with 2014 core.
for the issue 1 , yes OSD have problem ,not sure how to fix this without using real font manager like in upstream .
for the issue 2 , regarding your log it’s seem a divide by 0 error is raising , I will look at when I will have some spare time.
for size mame2014 is smaller , because old mame was only arcade , newer are like ume = mess + mame so bigger.
mame_libretro_android.so is current core like 0.182 now.
Thank you so much for putting up mame, mess and ume2014. That is awesome
r-type, I’ve updated my MAME2014 through Retroarch and it’s working fine now! And man, this core is great!! All my games are working with this one and they are even faster. All OSD menus are fine and are working properly, and this core saves NVRAM as well. However, it just needs one more fix…the name! This core is based over MAME 0.159, which was released in 25 Feb 2015. So, it should be named MAME2015.
Thank you so much for this MAME2014 (2015) core! And I hope you can figure out what’s causing those crashes in MAME2016. If you need further testing, please let me know
Yes was 0.152 so 2014 at origin. And yes 2014 was great and faster for android device. Atetris is a good example to point speed issue with newer buld. But also newers mame are more accurate.
For mame2016. I’ve test to revert to 26 may 2016 commit and games like blstroid work fine. So pb are in the in between merge files.
@rcoltrane can you try this one ,
I revert to 26 may 2016 so one day and few commit after mame0.174 release , and I backport some commit I’ve done in 2016, so OSD menu and aspect should be Ok , and also backport old font from 0.170 maybe it will fix menu , i let you check.
game like wbml,mk,blstroid… should now work as expected .
If it’s fine i will push change in the mame2016 repo.
r-type, I’ve tested this new MAME2016 core you posted yesterday and the crashes with blstroid, mk, mk2 and mk3 are gone! The OSD menus are all working fine and the text in all OSD menus/submenus are fine!
One last game is crashing, but it was crashing in the old 0.174 build too that’s why I didn’t report it before. The game is Kung-Fu Master. This is now the only game that is crashing in my library with this latest MAME2016 core. All other things are just fine, congratulations!!! Sidenote: kungfum doesn’t crash in MAME2014 though.
Here’s the LOG file for Kung-Fu Master crash, let’s see what’s going on there:
rcoltrane.50webs.com/Log_2017-02-01_23-14-33_MAME2016_Kungfum_Crash.txt
Just one final question: MAME2014 is saving NVRAM too, which is not being saved by MAME2016. Is it too difficult to ‘insert’ the save NVRAM code from MAME2014 into MAME2016? Well, thinking about it it might be interesting to enable savestates instead, since the official MAME 0.174 build supports savestates for almost all games. I’ll check Retroarch’s MAME core options to see if I can enable savestates and if it works, we won’t need to record NVRAM files anymore, since the states saved will store high scores as well.
And again, thank you very much r-type for listening to me and fixing everything!!
nice if it works , i 'll have to revert the current 2016 and apply the fix .
I’ll take a look at KFM although it seem to be a netlist pb . For nvram , I thinks savestate are supported in mame2016 , maybe @Tatsuya79 can confirm this.
I think that’s here yes.
It works more or less depending of machine emulated.
Now that it is updated to mame182 my mame config doesn’t work anymore. Is there going to be an update to bring back tab menu?
? The update to 182 should not break the config. Tab menu is always Select + x on android. Nothing change here.
That’s wierd I can’t grab it anymore. My phone yes
Yes if I load RetroArch mame on my phone it doesn’t work unless I add my config to it. Which is select plus l3 for UI toggle then l2 for tab menu. It used to work on my phone with my config but now it doesn’t. I tried select plus x and no go. Very confused.
Weird it works fine on my phone without config.
It is me and another board member are having same issue. I uninstalled and tried again
I loaded a mame game and it came up just using left trigger . Great. But when I load a mess game on shield nothing responds to bring up tab.
Yes mess by default use kbd as full emulated You need to use a mame.ini to define a key to toggle. In partial emulated then tab or select x will work.not sure i will have time to look at this week to make a combo. For toggle kbd rmulation mode
Thanks yes the toggle I was talking about I made it for mame but it works on phone but I can’t get it to work on shield. Hey I noticed mame 2016 is gone from updater. Thanks for getting back.