Android Nightly discussion thread

RetroArch Android devices
#221

Tested Mame cores again using latest nightly October 10 on my Shield Portable Kitkat.

I have two Mame cores (Arcade Mame 2003 and Arcade Mame 2014) and none of them work. There’s currently no Mame core available that works on my device. The error I get is that it asks me to “open archive as folder” or open in core, and regardless what I choose it then crashes “retro arch unexpectedly quit”.

Other cores such as fba work just fine.

This problem with Mame cores has been persistent for about 2 months in all nightlies.

It worked in the last release version so something went south during the nightly development of the Mame cores.

I updated info files and tried basically everything. I am not sure what else I can do to help fix this error.

I will not and should not have to upgrade to lollipop which is broken on the shield portable on so many levels (sound for example is distorted in lollipop)

#223

[QUOTE=rsn8887;29254]Tested Mame cores again using latest nightly October 10 on my Shield Portable Kitkat.

I have two Mame cores (Arcade Mame 2003 and Arcade Mame 2014) and none of them work. There’s currently no Mame core available that works on my device. The error I get is that it asks me to “open archive as folder” or open in core, and regardless what I choose it then crashes “retro arch unexpectedly quit”.

Other cores such as fba work just fine.

This problem with Mame cores has been persistent for about 2 months in all nightlies.

It worked in the last release version so something went south during the nightly development of the Mame cores.

I updated info files and tried basically everything. I am not sure what else I can do to help fix this error.

I will not and should not have to upgrade to lollipop which is broken on the shield portable on so many levels (sound for example is distorted in lollipop)[/QUOTE]

The same… I really losing any hope that mame will be fixed soon…

#224

I just want to add that Mame core is working perfectly on windows 64…

#234

I tested again on my nvidia shield portable kitkat. I wasn’t able to download latest nightly - the build bot did not show anything (is it down?). But when I click on core updater now the mame git core shows up in addition to mame 2003 and mame 2014. Lo and behold the mame git core works as expected - no issues apart from the occasional crash mid game.

The mame 2003 and mame 2014 cores still show the erroneous “open archive as folder” option followed by a crash.

#236

Waiting…

#237

Still waiting for testing a new version…

#240

Firstly, Radius, thankyou for all your hard work towards RetroArch.

Retro, please be patient. Chasing Radius is just going to reduce his motivation to find time for the project. The project team are amazing people who should be thanked and nothing else. This isn’t their job, and they have no obligation to the project or its community. We and it do not pay their bills. It is a hobby to them, which we are lucky to also benefit from. And like all hobbies, they do it because they enjoy it. If they start getting harassed, chased and scrutinized then its not going to be a fun hobby anymore. Which means, they will stop. Just back off and let Radius do what he can when he can.

#241

I tried the latest nightly October 15 on my Nvidia Shield Portable Kitkat, and there are still three mame cores available: Mame (2003), Mame (2014), and Mame without any year. The Mame core works fabulous, the Mame (2003) and Mame (2014) show different errors. One of them shows the “Open archive as folder” option, the other one just crashes after selecting it.

Since the Mame core works just fine and seems quite fast on my Shield, I am pretty happy with it actually. Thank you for adding that third Mame core at some point. I understand that the Mame (2003) core might still be helpful, because it will probably run some games faster. I am not sure what the use of the Mame (2014) core would be if the Mame core is up-to-date.

The Mame core also supports the analog controls on the Shield Portable very nicely now! Kudos to the Retroarch team for supporting this. I remember in earlier versions the analog sticks were supported, but always treated as digital inputs only.

I also quickly looked at the speed of the Retroarch Mame core against the program Mame4droid 0.139u1. Result: Retroarch is much faster, almost a factor 1.5 on some games I think. I tested this with heavy games such as Outrunners, etc. By the way Outrunners works great in Retroarch on the Shield Portable now, which is an amazing feat for a handheld console! It is such a great game, too!

#242

Having problems with choppy sound in the new mame core in my archos gamepad 2, is that normal? I am on the latest nightly, tested metal slug 3. and wild west cowboys

#243

Just tried mame4droid 0.139u1 and it runs most games fullspeed in the archos gamepad 2 much faster than the new mame retroarch core, I am curious which games are faster in the new core like rsn said.

#245

My understanding there is that newer MAME does not necessarily mean slower as in performance MAME, it means more accurate emulation, some games on Neo Geo for instance actually have a slowdown in certain parts as normal gameplay.

#246

Some drivers have increased accuracy, and yeah slowdown can be a part of the original game, but it’s definitely gotten slower across the board. You can take a mature driver like CPS2 and load the same ROM across 2003, 2010 and 2014 and watch the framerate drop.

While accurate emulation is often slower than inaccurate emulation, increased accuracy doesn’t necessarily mean increased requirements. For example, the performance of higan’s bgba core improved in a bunch of games when byuu emulated prefetch.

#247

Well I have been testing only a few games that I regularly play on my Shield Portable, but the Sega games Outrunners, Power Drift etc that I tested are much faster on Retroarch than on Mame4droid. Now it might well be that Neo Geo games run slower on Retroarch. I use the Finalburn core for SNK, CPS1,2, and 3. I have always preferred final burn over Mame if possible. SF3 and Red Earth runs in fullspeed using Finalburn core on Retroarch on my Shield portable, which makes me very happy. If only the dpad on that device would not suck so much.

#248

is MAME 2003 going to work again with the nighly version?..MAME GIT runs fine in my SHIELD but is too slow for my ARCHOS GAMEPAD in this device I always run MAME 2003 but with the nighly it doesn’t works :frowning:

fMSX Core with the last nightly Failed to save state.

#249

[QUOTE=Quickgold;29633]is MAME 2003 going to work again with the nighly version?..MAME GIT runs fine in my SHIELD but is too slow for my ARCHOS GAMEPAD in this device I always run MAME 2003 but with the nighly it doesn’t works :frowning:

fMSX Core with the last nightly Failed to save state.[/QUOTE]

Having the same problem in nvdia shield tablet.

#250

Is there a changelog for the nightlies?

#251

Close: https://github.com/libretro/RetroArch/commits/master

#252

Great. Thanks!

#253

Hi, I make a fresh install with the last nightly and here I have the same issue like windows, RA detects the device but you can’t bind any button and it says keyboard no joypad, you can see User 1 device Index ARCHOS GAMEPAD (same thing happend to me with My OUYA, my Shield and my nexus 7 with a NES30 Bluetooth Gamepad) but nothing you can do for bind, autoconfig doesn’t works either :frowning:

#257

Hi, now all works fine again with my pads but like in Windows, I have to change Bind Mode from AUTO to RETROPAD (with AUTO try to bind to keyboard), autoconfig with the ARCHOS GAMEPAD doesn’t works because the Archos Gamepad autoconfig file is wrong, I did save a new file.