RetroArch-2014-09-04 Android: Updated: RetroArch[7f34615]
Win64: Updated: RetroArch[7f34615], common-shaders[fa258e3], 4do[961812b]
NOTE: For best results with Android port, be sure to uninstall previous version before installing newer versions. MAME/MESS/UME 2014 based on MAME-SVN r31751
Fixed, I also added a saves folder and added the path to retroarch.cfg for saves and savestates.
Though you are right, the entire file needs completely updated.
Thanks for the Update Lordashram…guess this way be your last nightly build before we get the official release??
There is no official date for 1.1 yet.
Fixed, I also added a saves folder and added the path to retroarch.cfg for saves and savestates.
Though you are right, the entire file needs completely updated.[/quote]
In my opinion there is no need to include a skeleton config or at least it shouldn’t be named retroarch.cfg. After the first run one is generated anyway
Hi,
I’m having a problem with the latest android build on JXD s5800. When I change the controls and then go back to the game retroarch freezes. If I save the config and exit after changing the controls going back to retroarch only 3 directions seem to have saved and no other buttons
Big Thanks to Lordashram for all the x64 builds. Just wondering if this is a bug, or conflicting buttons. In Mame, if I load in a game, let’s say Outrun, now bring up the rgui and click resume and it always goes to the emulated machine’s Test menu. For me, it does this on any arcade machine that has a test menu, and makes it tricky to do things in the rgui without having to reset the running machine.
Yeah this is because RGUI button config conflicts with MAME’s own button config. This has even an issue for a while now and was hoping it would have been sorted but sadly not, trying to play Street Fighter 2 was a nightmare as the heavy punch and kick buttons bring up the mame ui menu and such stuff. You’d have to go into the mame options and reconfig a lot of buttons to stop this from happening, which is a hassle
Thanks, Blockaboots. Just glad it’s not just me. Would changing the test button in Mame itself, via the Mame in-game menu, or is this not saved when you exit ?
I’m also having an issue with controls on the latest Android build, both saving and autodetection. It showing in RGUI that the controller was detected, but it’s not remapping the inputs. Also, the on-screen controls don’t shut off when they’re turned off in the Android settings.
Another issue is with the MAME 2014 and 2010 cores freezing with shaders enabled. For some reason, I can’t get Outrun to run on Nvidia Shield at all. It locks up while decompressing the ROM. Works on Shield Portable, but without shaders, as previously mentioned.
Same pb for me with Shield Tablet ,after setting input manually , it freeze when resume content . i have to load a new content else it freeze with the current .
Same apply for me ,detected but not mapped.
Now i had a 4.4 device to test , so i ve tried your apk on a shield tablet android 4.4 , and ume works great ! but i had to change in path setting “the extract directory” to set in something like that : /storage/sdcard1/Android/data/com.retroarch
with mupen64plus-libretro on shield tablet just get an solid color on screen like reported , when changing core option to glide64 i finally get video but with many glitch .
Also Retroarch freeze when i resume content while i’am on rgui . but if i use overlay , i can enter and leave rgui mode without freeze.
Nice tip about using the overlay button to exit the menu 7rtype. That method works for me too.
RetroArch-2014-09-18 Android: Updated: RetroArch[db33f26], Beetle PCE Fast[24f71aa], Beetle PSX[09f6939], Beetle SuperGrafx[d90d58e], Mupen64plus[d96ab91], SNES9x-Next[8f8541c], UME2014[f69fbfa], VBA-M[642eff8]
Win64: Updated: RetroArch[db33f26], common-shaders[f9e671e], Beetle PCE Fast[24f71aa], Beetle PSX[09f6939], Beetle SuperGrafx[d90d58e], MAME/MESS/UME2014[f69fbfa], Mupen64plus[d96ab91], SNES9x-Next[8f8541c], VBA-M[642eff8]
NOTE: For best results with Android port, be sure to uninstall previous version before installing newer versions. MAME/MESS/UME 2014 based on MAME-SVN r32043
UME now loads games in Android 4,4 on default configs, so a big thank you to who fixed that but I don’t have time right now to see. Also, I trimmed down quite heavily the retroarch.cfg that comes with my Win64 builds. I also updated my hash.zip in my dropbox to latest MAME.
Great news,
But the input CONFIGURATION AUTODETECTION is not working anymore for Nvidia Shield(Android)…
Maybe because. Autoconfig is not include in asset folder ?
Thanks for the update it’s got rid of the freeze problem after changing controls. However picodrive has stopped working for me now. I just get a black screen.
Wheres the Hash folder supposed to do in the root?
Is there or will there be a way to set up button configs for each core separately? As take the N64 core for example, on a 8 button pad (6 face buttons and 2 should buttons) the buttons arent mapped ideally, if you try and alter them then it also alters the button config for the RGUI
I use android 4.1, but for some reason, the save directory goes to the retroarch.com thingy outside the sdcard0 and sdcard1. It does that despite the settings check for loading the save data from game’s directory, so I had to go to retroarch TV mode to do that every time I load a game. It managed to reset every time for save data and save states, but not for everything else.
Maybe because. Autoconfig is not include in asset folder ?[/quote]
are there something I can do to fix it?