Hi, I’m new to MuOS but not to RetroArch.
I have cross compiled a core currently not in the MuOS package or in the extras list in the download. If I manually go into RetoArch turn on the appropriate menu options, I can install the core just fine, load content and play the games. But this is obviously a bit of a faff and I’d prefer to launch via the main content menu.
Also - using SSH I have uploaded the info file for the core and it’s all working and showing fine in RA. /opt/muos/share/emulator/retroarch/info
However, how can I associate a folder of games to this new core, when it’s not “seen” by the rest of the MuOS platform?
I’m reverse engineering this a bit, but it looks like /opt/muos/share/info/assign is where the assignments are set to tie a folder to a core. I’ve created a folder in there, and also added an .ini file which should run RetroArch with the wanted core. My new folder now shows us when I try and do a core association, but the .ini file isn’t recognised and doesn’t show up.
There is also the /opt/muos/share/config folder and my core folder and the .opt file was auto created in there from using it once in RetroArch directly by the looks of it.
I’ve also updates the folder.json in /opt/muos/share/info/name in the hope that this might be the place for MuOS to realise there was another core, but no dice.
So there are clearly some other files/lists/dbs I need to manually update to try and force MuOS to know about it’s new core, that’s not a default one.
Any help would be greatly appreciated!