You can simply rename the Mame2014 core, to any of the existing Mame cores name (i chose Mame2000). We can bypass this though, by tricking Retroarch. This is a little tricky as it is no longer available for download and so the Core Info doesn't exist on the libretro server anymore.
Now you have to install Retroarch and manually sideload the Mame2014 core. Other latest gen CPUs might work as well, i don't know. There are many smartphones with this Soc, but the best would be one with minimal CPU throttling (OnePlus 7 is a good choice).
I am talking full speed, with smooth slowdown in those tense bullet hell moments, overall a very enjoyable way to experience these gems, anywhere, anytimeįirst you neeed a smartphone with Snapdragon 855 (Snapdragon 845 - might- also work with some more tweaking). So, after extensive tests i can now come with a guide, numbers and tips for anyone that wants to play the cv1000 shmups on android smartphones. Thanks for the info friend, and if you ever think of doing a dynarec for android, be sure that at least one person will be forever grateful I honestly doubt that the latest Mame could be faster than this one, but i will definitely test it as well and hopefuly it'll be close (because there are two cv1000 games not available in 0.157) So far it is the fastest (at least 30% faster than 0.160 based core) and it allows for a lot of room in terms of tweaking.
I found one of the earliest Mame cores compiled for android that supported Cv1000 driver, based on a 0.157 version, and managed to add it to RA (i will explain how in a future post detailing all my findings). I mostly aim to find the sweet spot for the major slowdown moments, and so far so good
I'm aiming for playability and speed as close to originals as possible. The games vs different mame cores vs CPU %. I'm in the process of testing everything as thorough as possible.
There have been optimizations to that driver and the related components even outside of the recompiler since 2015, of note, very significant ones to the sound emulation when PGM2 went in, which was actually eating a fair bit of CPU time in many cases.Ī current version of MAME should perform better than a 2015 one, even on platforms with no recompiler.Īlso, yes, RA is garbage, although on Android you're unfortunately stuck with garbage.
I love to sit down in the subway or breaks at work, and analyse another boss pattern or discover a new stage 's great Well, to have all these amazing ganes in your poket and to literally enjoy them whenever, wherever you want/are, is the point. Yes, it seems that the values are not exactly the same for each game to trigger slowdown in certain moments (and for overall smooth sailing), but with trial and error, i'm narrowing down on it More important is the question: what's the point of playing those games on a damned phone Though the settings are different for each game, no way a fixed value sets it right for all, nobody knows the 'best' settings anyway, and even if they were found the results still wouldn't be exactly like the originals, more like another flavour of ports. Unrelated to the refresh rate/speed, I think you know the CV1000 driver requires underclock of the emulated CPU to somewhat reproduce the ingame slowdowns, since the blitter delay option can't do that by itself as far as we could observe. If you're setting the CPU to 35%, isn't that by definition not full speed?
The guys FinalBurnNeo (the new FBA) are working on coding the driver for FBN emulator as well, and if we take into account the trend of FBA drivers to the at least twice as fast as Mame's, this will hopefully mean speed improvements that will allow less powerful devices to run these gems With these settings, the games perform much better than the ios ports (which are very fresh in my mind). The input lag is somewhere around 4 frames at most, and the overall experience is just great. Activating the option, adds a few % to the speed (while adding a barely noticeable and infrequent scrolling stutter). The Mame emulated CPU must be set around 35%, and this way the game slows down beautifully when all hell gets loose, and all this with Vsync and without threaded video option in Retroarch. So i recently bought an OnePlus 7 smartphone, and of course the first thing i did was to test the infamous Cv1000 shmups via Retroarch with Mame2015 core.