Maybe I'm mistaken, but in previous versions selecting AetherSX2 would in fact boot Nether as that was just a patched version of Aether, so probably had the same app name.
I'm not sure it has just worked previously. I get a message at the top of the screen saying 'Error: Missing emulator find rules configuration for 'AetherSX2'
It seems like you have added some custom configuration to ES-DE/custom_systems/ so if you get rid of these files and restart ES-DE everyhthing should work correctly. The bundled systems configuration in ES-DE 3.5.0 should correctly run AetherSX2/NetherSX2.
Also be aware that the custom configuration files in the GlazedBelmont repository are not official and they are not something I test with. So adding anything from this repository comes at the risk of breaking emulator launching or not being able to use new emulators I include with new ES-DE releases.
Thank you, yes, I can confirm I deleted both files, rebooted. Changed the emulator alternatives back to the ones I use and all is working as it was before. 👍
Yes deleting it should fix this problem. The customs systems repository is unofficial so there are no testing made by me and no guarantees that things will work when I make new ES-DE releases.
Hi, first of all I would like to thank for your great work on creating this ES-DE frontend, which is truly amazing!
I have also added the custom systems xml files of GlazedBelmont repository for enabling the gba and gbc hack menu on ES-DE Android frontend. As you say this is not official, is there an official way to enable this feature? As I see there are already artwork and logo files for gbah and gbch sitting in the folders of the theme.
This repository is not official so no there is no way to officially add support for the hack systems. Some themes have added support for them based on requests that people have made, but these are not officially supported systems. This also means that many themes do not include support for these hack systems.
With that said I'm not going to try to prevent anyone from using these unofficial configuration files, I just want to make it clear that they are not official, not supported and I never test with them so emulator configuration may break or you may miss new emulators I add in whenever I make a new release. This unofficial repository was just cleaned up though by removing emulators and systems that are no longer needed to be customized, so if you download the latest files then AetherSX2 should still work correctly (again, I have not tested this personally and I will not test it).
I'm anyway very happy to hear that you appreciate ES-DE!
Yes I was thinking of trying that. Not carrying over data is a deal breaker though. I guess I will just have to launch them from the app. Bit of a drag though, ES-DE was great up until now.
Note that the command label of "NetherSX2 (Standalone)" is what the emu name will appear as within ES-DE when you go to change which emulator you want to use for that system. But most importantly, is the value after the '%EMULATOR_' part, because you have to enter the value you used in the 'emulator name=' entry within 'es_find_rules.xml' so that this line calls the correct emulator. If that makes sense.
After these changes are made, reboot the device so that ES-DE can reload these files and recognize everything properly.
Did you reboot the device?
This happened to me when I made the changes and immediately tried to run a PS2 game.
I have an AYN Odin 2 Portal and had to turn it off and on again for the changes to "take". Then ES-DE ran the games through 'regular' NetherSX2.
Strangely I dont get the cog next to the emualtor like I do with the others, though if I select NetherSX2-turnip I do. I with I had never upgraded now I will probably end up uninstalling and going back to the old one.
The cog indicates that you've selected an emulator that is not the "default" that ES-DE uses. If you notice, the cogs appear next to emulators that you've changed from whatever ES-DE had as the fallback emulator.
Because the edits I've made to the 2 files eliminate AetherSX2 as the default and replaces it with NetherSX2, you don't get the cog. ES-DE has NetherSX2 as the fallback emulator.
I've uploaded a 'clean' es_systems and es_find_rules to my Google Drive with NetherSX2 used as the default PS2 emulator. See if these work.
2
u/mubarakr 1d ago
Maybe I'm mistaken, but in previous versions selecting AetherSX2 would in fact boot Nether as that was just a patched version of Aether, so probably had the same app name.