Jump to content
lilcza

Retroarch's MAME GIT(Nightly\.174) vs, Mame4Droid - Compatibility vs. Performance

Recommended Posts

Hey Everyone,

 

Wanted to get everyone to weigh in on their experiences with both. i have the .139u set that works with Mame4Droid, but as of lately i've been using the Mame Git (nightly) in retroarch with my .174 romset and havent had any issue of slowdown or anything.

 

Of course Mame4Droid using the older romset tend to be faster because of emulation inaccuracies, but with Nightly allowing more systems to be playable, i lean towards Mame Git and haven't experienced any slow down on the previously well emulated items, only things like Namco 22 or Model 1,2,3 have 60% speed.

 

So im about to just remove the old romset from my drive.

 

Anyone else have any thoughts on this?

Share this post


Link to post
Share on other sites

Ok so i've been testing out my new .174 rom sets and while much of the newer console items are broken in the Git setup, along with Midway Blitz games and Laserdisc items not working, the speed for the commonly playable items between Mame Git & mame4reloaded seems to be the same to me.

 

Regardless of what settings I changed, the performance on the higher end arcade items, doesn't seem to change.

 

Now I know there are alot more emulators that provide Mame or mame like experiances (i.e Tiger Mame, Jrioni Arcade)

 

If you found anything that maybe assists in making more games playable like KI not being a complete slideshow, or crusin' from running at 60% please leave that info here.

 

 

 

Honestly, we need more android devs out there to help out with the emulation scene as a whole.

 

Reicast (dreamcast) is DEAD

There are NO Android Dolphin Devs anymore, causing all the new releases to have broken controls and dolphin bar support is spotty at best.

Openbor is compiled but doesnt work well for controllers or hyperspin

Mugen has zero support except for Paintown which hasnt been updated to work on modern devices in years. And Dosbox allows only OLD dosmugen to work, not without some heavy tweaks.

MAME on android needs a huge Open GL ES 3.1 or Vulcan boost so that better games can be supported and played. 

 

But mainly the most recent versions need compile fixes to be 100% working on android. Not this currently handicapped version.

 

Look what uoYabuse did for Saturn emulation. The original Yabuse went from unplayable to near perfect emulation thanks to OpenGL ES 3.0 changes.

 

 

 

So i think im going to try to start a bounty for donations to android devs to assist with these things

 

I would love to help out with some smaller things if I can, i programmed at bit in C++ back in 2000.

 

But now that we have these amazing devices that can handle more, we don't have the great killer apps to truly make this amazing.

 

This would make Hyperspin closer to complete than ever on android.

  • Upvote 1

Share this post


Link to post
Share on other sites

What a great topic! I found it while trying to see the best setup for Android, and I am confused as to which one or ones I should download or if now any are made redundant by newer versions.  I'm aware of MAME versions and roms needing to match the version but am lost on the version variants.  There is 35b, 139, Reloaded, and the cores in Retroarch.  Also there are tons of "me too" distraction apps that look like builds of MAME with one or two games pre-installed.

It sounds now that RetroArch may be the one thing you need?

Share this post


Link to post
Share on other sites
On 8/24/2016 at 1:43 PM, lilcza said:

Ok so i've been testing out my new .174 rom sets and while much of the newer console items are broken in the Git setup, along with Midway Blitz games and Laserdisc items not working, the speed for the commonly playable items between Mame Git & mame4reloaded seems to be the same to me.

 

Regardless of what settings I changed, the performance on the higher end arcade items, doesn't seem to change.

 

Now I know there are alot more emulators that provide Mame or mame like experiances (i.e Tiger Mame, Jrioni Arcade)

 

If you found anything that maybe assists in making more games playable like KI not being a complete slideshow, or crusin' from running at 60% please leave that info here.

 

 

 

Honestly, we need more android devs out there to help out with the emulation scene as a whole.

 

Reicast (dreamcast) is DEAD

There are NO Android Dolphin Devs anymore, causing all the new releases to have broken controls and dolphin bar support is spotty at best.

Openbor is compiled but doesnt work well for controllers or hyperspin

Mugen has zero support except for Paintown which hasnt been updated to work on modern devices in years. And Dosbox allows only OLD dosmugen to work, not without some heavy tweaks.

MAME on android needs a huge Open GL ES 3.1 or Vulcan boost so that better games can be supported and played. 

 

But mainly the most recent versions need compile fixes to be 100% working on android. Not this currently handicapped version.

 

Look what uoYabuse did for Saturn emulation. The original Yabuse went from unplayable to near perfect emulation thanks to OpenGL ES 3.0 changes.

 

 

 

So i think im going to try to start a bounty for donations to android devs to assist with these things

 

I would love to help out with some smaller things if I can, i programmed at bit in C++ back in 2000.

 

But now that we have these amazing devices that can handle more, we don't have the great killer apps to truly make this amazing.

 

This would make Hyperspin closer to complete than ever on android.

The new dolphin dev. Has controls put back in. As far as mame they need to bring back retroarch mame2014 core. Openbor works great with controller. You have to set them in the game. The menu you use right stick for mouse and push to enter

Share this post


Link to post
Share on other sites

Reicast (dreamcast) is DEAD ?

I was playing Reicast fine through Hyperspin only a few days ago.

Why do you think its dead ?

Share this post


Link to post
Share on other sites
10 hours ago, cataclysm67 said:

Reicast (dreamcast) is DEAD ?

I was playing Reicast fine through Hyperspin only a few days ago.

Why do you think its dead ?

Think it's more development is dead on Android.

22 hours ago, phantasy said:

What a great topic! I found it while trying to see the best setup for Android, and I am confused as to which one or ones I should download or if now any are made redundant by newer versions.  I'm aware of MAME versions and roms needing to match the version but am lost on the version variants.  There is 35b, 139, Reloaded, and the cores in Retroarch.  Also there are tons of "me too" distraction apps that look like builds of MAME with one or two games pre-installed.

It sounds now that RetroArch may be the one thing you need?

You really should get MAME4droid reloaded with the corresponding 139 set because it just works and is stable. It's not massive so is worth it.

on from that it's the Arcade (MAME) core listed in RA online updater. That's the most current retroarch MAME core and has been on .174 for a while now. (I last download the core about 2weeks ago)

there are problems with all retroarch MAME cores. Think renderer needs to be set as alternate as MAME gui is fuzzy otherwise. Alternate is hard to read. It's just trial and error but most things will run ok. I'm not a big player of games or knowledgeable on compatibility. The retroarch MAME core brings the software list factor to android. That is the BEST thing about it. It allows for 10's of systems to work on droid that don't have an emulator. Although they are inherently a pain to get setup. It's back to core MAME basics. It you know MAME in/out you will be golden

Share this post


Link to post
Share on other sites

Im not too big on retroarch,  I prefer to set up my Hyperspin with individual emulators. MAME4DROID is awesome and 95‰ of my rom set works, so I honestly have no complaints,...  maybe update the interface layout so navigation is easier on the eyes, (something like mupen). I've downloaded final burn alpha .apk,  but I haven't  tried it out yet (looks promising) 

Reicast is dead? On the Reicast CI build page the latest build was November 2016 So somebody didn't give up. 

 

Share this post


Link to post
Share on other sites

I just got Killer Instinct, carnevil bio freaks CHD ROMs to load in Mame 4 Droid. It's slow but loads. I also got capcom play system III CHDS TO LOAD. You need to set speed hack to get 100 percent. You have to let the emulator rewrite the file then after it loads right up

  • Upvote 1

Share this post


Link to post
Share on other sites

Man you gotta do a little video of how to with this. I though CHD's on droid were a myth :) so never even looked

Share this post


Link to post
Share on other sites
26 minutes ago, thatman84 said:

Man you gotta do a little video of how to with this. I though CHD's on droid were a myth :) so never even looked

It's set up the same. zip file in roms folder with chd in a folder in roms folder. Example mame4droid/roms/kinst/kinst.

Then you have to download mame330u4 bios and stick all bios files in Rom folder. http://www.emuparadise.mobi/biosfiles/MAMEBIOS.rar

 

As far as cps3 just do the same file structure and open a game and let it rewrite.

Share this post


Link to post
Share on other sites

Well we got screwed by retroarch. They updated mame git from 174 to 181. Now there is no in-game mame options when you hit left trigger. Don't update

  • Upvote 1

Share this post


Link to post
Share on other sites
4 hours ago, badhemi said:

Total junk core. Pissed

I'm sure someone will have a backup copy of a non-updated core, no? I don't know what my build has but I can check

Share this post


Link to post
Share on other sites

Fore those not rooted I managed to setup up a local Online updater last night which will help with this problem in the future.

its definitely not simple and I need to find out some more details before testing it with older/custom cores. I will be able to have a core "per system" for GG, MD etc using Genesis core

i don't have the 174 core so if anyone does please post it

  • Upvote 1

Share this post


Link to post
Share on other sites

Sorry gang, been busy with work.

At the time i posed the initial post, mostly all of the said items were addressed months later.

Dolphin had zero devs. and just recently a forum member stepped up and fixed the controls.

Reicast was dead for months on the android apk side, not even questions on the forum were being answered.

Thanks to a few updates with the shield the right stick is now the mouse, which sadly the touch pad above the volume rocker on the shield controller is supposedly no longer compatible now. But i had to use a air mouse to navigate Openbor for the longest time, which still does not have native joystick support for more than 1 player that works correctly.

Also i know i had mentioned to use Alternate rendering for your mame, but it does cause a performance hit. So it's either blurry on the regular renderer or slow performance and clear.

Vulcan has also been introduced to Retroarch. I have not seen any real performance jumps as of yet.

I've been using my .174 mame set with no issues, but i have not updated my mame core to the .181 version yet.

But from what i see, things like laserdisc games and certain Atomiswave games do not work at all on android compared to Windows. I would love to know the differences.

I also need to reread @thatman84 tutorial for mess items, it couldn't get it working.

Share this post


Link to post
Share on other sites

Glad to see you drop in @lilcza, and makeing me a year younger is cool with  me :)

Let me know if that tutorial needs work, I have completely stayed away from MAME git except Atari5200. Just seems like time not well spent for me

  • Upvote 1

Share this post


Link to post
Share on other sites
On 12/28/2016 at 8:08 PM, badhemi said:

Well we got screwed by retroarch. They updated mame git from 174 to 181. Now there is no in-game mame options when you hit left trigger. Don't update

Someone thought it would be a good idea to remove default key bindings.    They added the OSD menu back with select-analog-stick-click, but there are still some issues (that existed with prior GIT core)

Retroarch team is working on building mame2010, 2014 cores again.

BTW, don't rage at emu coders working on things for free.   File a bug, let them know about the mistake or fix it yourself.     If you're doing something for the fun of it, negativity kills that interest.

Share this post


Link to post
Share on other sites
3 hours ago, reznnate said:

Someone thought it would be a good idea to remove default key bindings.    They added the OSD menu back with select-analog-stick-click, but there are still some issues (that existed with prior GIT core)

Retroarch team is working on building mame2010, 2014 cores again.

BTW, don't rage at emu coders working on things for free.   File a bug, let them know about the mistake or fix it yourself.     If you're doing something for the fun of it, negativity kills that interest.

I didn't mean to be rude. One guy was rude to me because I got Mame chds and philips cdi and neogeocd working on android and said they did it to screw me.. I got the bindings to work on it anyway. Sorry for the disrespect rez

Share this post


Link to post
Share on other sites

Badhemi, no worries man.  You've contributed quite a bit yourself.     Just wanted to remind this a hobby for everyone.

I do share your frustration with the constant regressions with Retroarch.   Their system is very complex and few of the coders involved test on Android.   They prefer development on linux and other consoles over windows, android, etc.    Also, Android keeps changing, causing additional problems as well.

As an example, with the upcoming Android N update, mame4droid will stop working if your roms aren't in the default location.

The author will need to fix this.

Share this post


Link to post
Share on other sites
6 hours ago, reznnate said:

 

As an example, with the upcoming Android N update, mame4droid will stop working if your roms aren't in the default location.

The author will need to fix this.

That's a nuisance, hopefully he can get it fixed up. 

I always try to limit my updates as becomes a chore to keep up instead of a hobby.

 

Share this post


Link to post
Share on other sites

For now I think mame181 has the best speeds but to fix the controls issues u have to be rooted because u need to get into hidden folders unless you've changed all default locations outside of android data folder

  • Upvote 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...