I got some of the Extra-Extra paks working on my Miyoo Mini using the MiniUI, but I can't get some of them to work on the newer MinUI, and I'm at a loss for why.
I am mainly just trying to run a few fighting games using CPS1, CPS2, CPS3, and FBA. I could not get CPS1 to run any games at all. On MiniUI, I could not get CPS1 to work at all, but the work fine for most games I had. The newer MinUI has a different file architecture, but after comparing them I eventually figured out that they are similar, except:
MiniUI requires the paks in the Emus directory to reside in a subdirectory named for each system, so Emus/miyoomini/*.pak in my case.
The launch.sh scripts use a different calling function, so the call to picoarch is replaced with minarch.elf (or sometimes nice -20 minarch.elf for some reason).
Then I placed them in the Emus subfolder to install them with MinUI. (This requires them to be on the SD card at the time of initial installation, which wasn't obvious from the many versions of instructions.) And this approach seems to have generally worked, because CPS2 works on MinUI just like it did on MiniUI. However, CPS3 and FBA do not; the games never load and the Miyoo Mini device is frozen until I pull the battery out. Looking at the logs, it seems to be a core dump. It does this for both emulator whether or not the need-swap option is used, but seems like it crashes prior to reaching this step. Here are example logs showing CPS2 working and CPS3 crashing:
One other difference I noticed in the new MinUI paks versus the old MiniUI ones is that the new ones all come with a default.cfg file. And there were some instructions on how to create a new config file for a DIY pak by copying some minarch.cfg example out of ./userdata, but those seem to be out of date because I couldn't find any such file. I'd be surprised if paks wouldn't working with this file, but maybe this might explain something. I tried creating configs in MiniUI (picoarch.cfg) and using them to make default.cfg, which didn't crash, but it did prevent all of the bindings from being assigned, so it seems that these are not in the same format for MinUI.
Anyway, I'm way out of my depth at this point, so I'm sort of asking for ideas but also just sharing what I learned in case its helpful for anyone else who has the same questions.
I got some of the Extra-Extra paks working on my Miyoo Mini using the MiniUI, but I can't get some of them to work on the newer MinUI, and I'm at a loss for why.
I am mainly just trying to run a few fighting games using CPS1, CPS2, CPS3, and FBA. I could not get CPS1 to run any games at all. On MiniUI, I could not get CPS1 to work at all, but the work fine for most games I had. The newer MinUI has a different file architecture, but after comparing them I eventually figured out that they are similar, except:
Emusdirectory to reside in a subdirectory named for each system, soEmus/miyoomini/*.pakin my case.launch.shscripts use a different calling function, so the call topicoarchis replaced withminarch.elf(or sometimesnice -20 minarch.elffor some reason).okay.png, and it also seems like there is not way to write message to the screen and to wait for user input. For whatever reasons, the work-around described in issue #1 and implemented in commit https://github.com/tiduscrying/MiniUI-Extra-Extras/commit/81f7546f46423423c219a036721d3f0c3afef3c9 doesn't work on MinUI.So I modified the MiniUI launch scripts to remove the large ROM messages and just set it to call
need-swapdirectly, as shown in the example below.Then I placed them in the Emus subfolder to install them with MinUI. (This requires them to be on the SD card at the time of initial installation, which wasn't obvious from the many versions of instructions.) And this approach seems to have generally worked, because CPS2 works on MinUI just like it did on MiniUI. However, CPS3 and FBA do not; the games never load and the Miyoo Mini device is frozen until I pull the battery out. Looking at the logs, it seems to be a core dump. It does this for both emulator whether or not the
need-swapoption is used, but seems like it crashes prior to reaching this step. Here are example logs showing CPS2 working and CPS3 crashing:CPS2.txt CPS3.txt minui.txt
One other difference I noticed in the new MinUI paks versus the old MiniUI ones is that the new ones all come with a
default.cfgfile. And there were some instructions on how to create a new config file for a DIY pak by copying someminarch.cfgexample out of./userdata, but those seem to be out of date because I couldn't find any such file. I'd be surprised if paks wouldn't working with this file, but maybe this might explain something. I tried creating configs in MiniUI (picoarch.cfg) and using them to makedefault.cfg, which didn't crash, but it did prevent all of the bindings from being assigned, so it seems that these are not in the same format for MinUI.Anyway, I'm way out of my depth at this point, so I'm sort of asking for ideas but also just sharing what I learned in case its helpful for anyone else who has the same questions.