Once Retroarch 1.3.0 successfully installs over the previous installation - you launch it again. The official 1.3.0 apk is signed with a different key and therefore wont install “over” a package you had to sign yourself. I used the Android app “Zip Signer” to do that. To do this both apk packages have to have been signed “the same way” (after being packaged with the older version of the ScummVM core). Once you have done this - you install the Retroarch 1.3.0 apk (again, prepackaged with the older version of the ScummVm core, because the current one just crashes) over the previous installation. This is necessary to get Scummvm to save its settings.īecause older versions of Retroarch dont have a problem with setting up the ScummVM cores “save structure” (scummvm.ini stuff). Each time by selecting the corresponding menu options. Then quit Retroarchs second menu layer, then quit Retroarchs first menu layer. Once in Scummvm and without insane mouse speed, setup the save path in the ScummVM options (to somewhere on your Android sdcard partition). Once you have the Scummvm Interface laoded and Retroarch doesnt crash immediately - you are through the rough part. But for some reason - on the first start, and if you dont select a game with it the core does not crash Retroarch if you start it from the second menu level.)Įdit: If it crashes for you at that point - reload and try again by using the “load game, detect core” option in the second Retroarch Menu level. Usually - if you dont start the core from the first menu level the core crashes within seconds, and if you start it from the first menu level it has the mouse speed problem. (This by the way is the ONLY time and the only way you have a chance of it not triggering. If you are lucky - the insane mouse speed for the stick emulation doesnt trigger. From there selecting load core, loading the prepackaged ScummVM core. It is possible though - to install an older version of Retroarch, with the old version of the Scumm VM core integrated into the package - then launch Retroarch once - immediately start Retroachs “second menu level” by highlighting the first menu item (“start Retroarch” or something along those lines) and confirming (the old Android Versions differentiated between a first menu level (“App look”) and a second menu level (“Text only”)). When it doesnt even remember the games you have imported into Scumm VM this again becomes a 5 minute process - every time you want to launch a game (import game, set savepath, set game settings…) Rendering this entirely useless again - because ScummVM is a very setup intensive core. When you use an older version of the core, the core starts up and works perfectly - but none of the settings of ScummVM itself (I’m talking about data stored in the scummvm.ini) get stored.The current downloadable scummvm core (Android build) crashes the app entirely.Older versions of Retroarch had an issue where on the ScummVM menu (once the core was loaded) the mouse speed for left stick mouse emulation was so freakishly high - that you couldnt select any settings or import a game into ScummVM and then start it - without spending half an hour trying to position the cursor - thousands of times. So if you are a dev and want to do something about this - this is as much input as you will get from me. I will not open any tickets on the bug tracker - as I had a very bad experience with this in the past - I will list the problems, causes and steps that are necessary to get this working in here and in here only. The devs botched the ScummVM support in the current 1.3.0 version again - but with some ingenuity I got it working. Edit: One other user is reporting that the current build of ScummVM works fine one his android device - so I have to preface – the following is describing a workaround if in your case also - launching the ScummVM Core in RetroArch 1.3.0 crashes the app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |