Hello All!
I recently updated to Jacaranda from Big Banana after wanting to use RetroAchievement subsets in RetroArch, and it went great for the most part! The only problem is that I often use the zc210 core, which requires manual configuration because the system files are not included.
I got it all set up, and the core is working if I manually launch it in RetroArch, but I’d like to be able to launch the games from the Explore option, like I could in Big Banana. I altered the assign.json file to include the new core, added a new directory in the assign directory at /opt/muos/share/info/assign, complete with a global.ini and zc210.ini.
When I go to assign a core, I can see my new entry as an option, but when I select the “Zelda Classic 2.10” option, it shows “No Cores Available”, despite the cores being installed in RetroArch and being fully functional there.
So, my ask is this: How can I manually add a Core that was manually installed to the Assign option in the Explore tab?
I’ve butt my head against it all day, and I’ve decided to reach out for help at this point. I hope that I’m simply missing something simple! Thank you all for your help
I’ve played with it a bit more, and I’ve found that if I put a core.cfg in the corresponding content directory in /opt/muos/share/info/content, I can get the core to assign, but now when I try to launch the game, the core doesn’t seem to launch. It may be a case of syntax at this stage, something case-sensitive or something. I’ll play around a bit more, but if anyone has any ideas or insight it would be appreciated 
I’ve been thinking about this a bit more, and I guess the REAL question that will lead to a REAL solution is: How do I get muOS’s front end to see the newly installed core in RetroArch?
If I could get muOS to somehow see all the new cores in RetroArch, then that would solve everything. I wish I could remember how I pulled this off in Big Banana, and why it isn’t working here…
I just created a new entry in the assign core menu for a new retroarch core we’re experimenting, the BennuGD core.
I created the new folder for BennuGD in /opt/muos/share/info/assign , then i copied global.ini and the genesis gx.ini from the mega drive assign folder, and edited them with the info from the new core, renaming what was needed.
And it just worked on the frontend without any issues.
I believe it should be some issues with malformed .ini files on your end.
If you don’t care on sharing your files, i don’t mind taking a look at them. I’m no expert but another set of eyes can help finding the issue.
The assign.json file is just for auto assigning a core to a folder, it will have no influence on the option being available at the assign core menu.
Thank you for your response!
That’s exactly what I did at first, except with the FCEUmm core instead. I’ve attached screenshots showing my current setup in the assign folder
If it helps, the github for zc210 is here, with instructions for setup that I used to get it working: GitHub - netux79/zc210-libretro: Zelda Classic 2.10 player Libretro port. · GitHub
Sharing the screenshots made me see the issue. I missed the section header in the zc210.ini file.
Correcting this resolved the issue, thank you for the sanity check!
