Win64 and Android Test Builds

Oh I see, thought you were talking about windows, I found the option in retroarch and that’s working now. Thanks! :slight_smile:

I have to do this change for every core because I use “per core config”. Which reminds me this: could we make per core config works like ini files in mame? I mean every core will use the main retroarch.cfg + only the settings that have been changed while using this particular core will be written in the core.cfg and take priority ove the main cfg.

As it is right now I have to make changes in every one of them if something changes (happened with the screen ratio setting, now the input driver) or for some settings that aren’t copied at creation (turbo button speed).

I don’t use per-core configs since it’s a bit complicated as you mentioned. I use the --appendconfig, that overwrites the normal config with parameters in the custom config, that way I can have just the relevant things I want changed in a different file.

RetroArch-2014-10-10 Android: Updated: RetroArch[156449c], UME2014[e89da7d], Nestopia[3468f3c],VBA Next[136fe20], Yabause[1d29a7a] Removed: MAME2014

Win64: Updated: RetroArch[156449c], Genplus GX[258329c], MAME/MESS/UME2014[e89da7d], Nestopia[3468f3c], ScummVM[0a703f6], VBA Next[136fe20], Yabause[1d29a7a]

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 r32599

RetroArch-2014-10-10 Android: Updated: RetroArch[2ad61f1] Removed: MAME2014

Win64: Updated: RetroArch[2ad61f1]

Oops, one thing I forget to check was the manual gamepad input, previous RetroArch-2014-10-10 would crash after so many inputs, this version fixes that.

Thanks for the kind words, the real thanks is really Squarepusher and the other real devs as my contribution to this great program is very minor compared to them.

Really aching to know how different RetroArch will be in the 1.1 update on Android.

Will the Mupen core be any faster,will Rice be fixed,and does it have the Banjo-Tooie Unga Bunga Cave fix as well? Cool if GlideN64 ever gets added to RetroArch Android. (wished PJ64 emulator could magically get ported as a core) And most importantly,will the input mapping FINALLY be fixed since the post-stable versions?

Speaking of the Mupen core, this last update I included an updated Mupencore that is finally up to date for the Android port as that port has not been able to compile successfully for a few months now. That is why you have only seen me post updates for the Win64 port but not the Android port. I had to do a dirty patch to get it to compile after SquarePusher’s latest Android build fix did fix the biggest headache but not the last but minor one. It works fine but there is a better way than what my dirty patch does.

Thanks again for those builds.

Is there any trick to make glui works (crashing when I launch a game) or it’s just not ready?

Thanks for the update Lordashram! Any chance of doing a Linux build for a one off?, im really wanting the latest version to use on OpenELEC?

Is the 1.1 frontend actualyl working yet, can it be used in the next build at all??

This might not be released to the update to Genplus but have noticed on the game, Shadow Dance on the very first stage the fire in the background seem to have screen tearing, i have vsync and GPU sync enabled but it does seem to fix the tearing. Can this be removed at all?

@Tatsuya79, glui works for me. I only tested it on a few cores, What cores have you tried?

@BlockABoots, I haven’t played around with OpenElec in a while but when I can I will see what I can do.

I just played around with Shadow Dancer, USA NTSC version and if you were talking about the wavy burning city in the background, that displayed fine by me. I wasn’t using any software filters and no shaders, only vsync with no hard vsync…

Yeah that fire in the background as it waves is has like sync tear on it everything else is fine just the fire has the tear. Hmm, i to wasnt using any filters either and have the issue.

Mame, Mednafen PCE, DeSMume, Gambatte… it seems everything crashes on start. I don’t see anything relevant in the log. An Nvidia driver issue?

I join the log here as I tried to start Mame and I can’t load cheats anymore (from retroarch\system\mame\cheat.7z). I’m trying to figure out this:

I/O warning : failed to load external entity “file:///E:/Emulateurs/RetroArch64/system/mame/”

Just found what my glui problem was. It was starting with menu driver glui at retroarch start and then, as I use per core config, it used rgui while trying to launch a game because of the core cfg.

That’s again one of those per core config “update them all” problem. :lol:

I’m still having a problem with the latest build on my JXD7800B. The overlay won’t turn off and the JXDs gamepad isn’t recognised. Anyone getting this?

Yep still buggy! I roll back to 0918 build.

Unfortunately even 0918 doesn’t seem to work on the 7800B =(

I’m on the JXD S5800 and I’ve got the same problem with controls and overlay. Also getting a black screen freezee at the start of launching games on some emulators that used to work such as picodrive

try this …

1.uncheck the autodetection

2.use “custom binds” manually bind your gamepad key

3.check the autodetection

It should works like me :stuck_out_tongue:

Thanks for the suggestion. Tried that but same result unfortunately. I have also noticed that nothing is appearing in the game history list either.

Hi, is it possible to merge cores (libraries) from different builds of retroarch? I am using an old build for android (may 2014) because it works fine on the nvidia shield, but I would like to use the latest version of the mupen64plus core.

I have replaced the mupen64plus.so file with the one from the latest build and re-signed the apk with the apk-signer app, but it fails when I try to install it. Is there any way to do this?