Oh I forgot to ask one thing… Is there a way of doing MAME core to read my .cfg and .ini game config files if I copy them from my computer to my Android device? If yes, where should I drop these files so Retroarch’s MAME core would recognize/read them?
I’m asking this because every time I enter an arcade game to play through the latest MAME 0.174 core, I have to access the internal MAME UI and set all the buttons, and this is kind of annoying 
Yeah, some of the MAME cores will create the necessary directory structure automatically while others will require making them manually, but I think it’s [savedir]/MAME/[whatever]
Latest mame core cause RA crash
Tested in galaxy s6 miui port
[QUOTE=brujo5;53619]Latest mame core cause RA crash
Tested in galaxy s6 miui port[/QUOTE]
Even if it is a useful and detailed information can you elaborate, post a logcat ? otherwise it works well for me.
Mame 2014 and all others cores work fine. Only hvae problem with mame 0.174
last mame core is 0.181.
Damn fixed after deleted all config files.
Work super fast in miui port. Thanks
I can confirm strange color issue (blue) with thumbnails and possibly elsewhere; appears this is a known issue. I’m also receiving random crashes of retroarch when selecting “close” from the quickmenu – this behavior is happening on two different devices.
Aside from the above, the “scan folder” option didn’t work for folders containing zipped files (there is a work around) – known issue: https://github.com/libretro/RetroArch/issues/3807
I can confirm the coloring issues, it also appears when using overlays; red appears blue.
I am using the 12-25 build
Can you try updating to a more recent build? We’ve done some work to hopefully resolve the red/blue swap.
Blue Color Bug is fixed. 04.01.16 build
w00t! Thanks for testing, Seedlord.
Tested the latest android .apk and confirmed that the blue color is fixed. However, my MAME core stopped working for good, no matter what I do. I’ve tried removing and reinstalling it from scratch, but Retroarch refuses to start my MAME games and crashes with the following message: “FAILED TO OPEN LIBRETO CORE”. How can I solve this issue? Please heeeeelp! I did several core updates taking different retroarch .apk versions but it just won’t open my MAME games anymore. The older MAME versions (2000 and 2003) are working, but I want the latest core, since these two are very outdated.
Just for the record, before updating my retroarch today, I was runnig the MAME 0.174 core without any problems. It was working just fine in my GPD XD device and it was quite fast. And besides MAME, I can run both Stella and Game&Watch cores without any problems. It’s just the latest MAME core that stopped working. And in my Motog Cellphone, I can update and run the latest MAME 0.181 core, so it could be something related to GPD devices only. Any clues or tips on how could I solve this issue is welcome! Thanks
Hi there!
I updated my RetroArch installation from nightly build 2017-01-11 to 2017-01-24. My retroarch.cfg contains the options
video_shader = "/data/data/com.retroarch/shaders/shaders_glsl/xbr/xbr-lv2-accuracy-smart-blur.glslp"
video_shader_enable = "true"
To disable shaders on N64 and PSX games my core specific configs for GLupeN64 GLES3 and PCSX-ReARMed contain
video_shader = ""
video_shader_enable = "false"
Config overrides in general are working. Only shaders aren’t disabled automatically when starting an N64 or PSX game. On my previously installed build it worked.
Have a nice day!
Try using the new ‘save core preset’ option to save a core preset for those cores using only ‘stock.glsl’.
Thank you for your advice.
Unfortunately it seems like an enabled shader will not be overriden neither via core config nor via core shader preset if it was enabled on global space.
What currently works well is to move shader settings to core specific configs or presets and keep it off the retroarch.cfg. So I created config override files for each core that should use the mentioned shader preset.
Onscreen Overlays (retropad) still don’t work for input on Shield TV for the useful parts it has.
Is anyone going to ever look into fixing this issue? It was said that the only thing needed is mouse support within RetroArch,and for example,the Shield TV Nougat OTA upgrade changed the UI to include mouse detection for highlighting options since the controller even supports mouse movement functions.
A neat bonus is that Opera for Android (a rather old version,no less) oddly supports right cliking in the omnibar via my K400 Plus keyboard.
Also,RetroArch works decently in a freeform window via the excellent “Taskbar” app,so that’s pretty cool as I can use a browser to check something or look up a guide when stuck without completely exiting out of it,too bad overlapping windows with full screen isn’t currently possible.
I am not sure that for each core we need different BIOS files? Like for mame2003 mame2014 cores we need different bios files when play some of the games? Where to get all these bios files for my android device? @anon24419061
I see some file called neogeo.zip . Some pepople say i need put this file into the content folder togther with the romfile?
I downloaded alot of the mame 0.78 roms .But found a lot of them just a black screen or not render correctly ?
I am using android . Do you have some idea over this ? How can I get them to work?
@anon24419061
Hello, having an issue with the nightlies. not sure what type of search terms to use to see if this had already been asked.
issue 1, when I load a PSX rom without any BIOS, the cores load the ROM fine. when I change directory to enable usage of factory BIOS RetroArch is unable to load the ROM. retro arch simply loads the factory BIOS.
issue 2, when changing state # for saving or loading this works and displays correctly. when saving or loading though display always shows loading or saving from state #0. saving and loading does happen from correct state #, but the display is incorrect at the bottom.
thanks for the hard work guys, RetroArch is amazing!