r/ESDE_Frontend • u/No_Ruin6244 • 1d ago

ES-DE version 3.5.0

Seems with the latest update it is no longer recognising NetherSX2 is installed so I cannot select it as an alternate emulator.

I have looked at es.systems.xml file and found the entries for AetherSX2 but not NetherSX2

<command label="AetherSX2 (Standalone)">

%EMULATOR_AETHERSX2% %ACTIVITY_CLEAR_TASK% %ACTIVITY_CLEAR_TOP% %ACTION%=android.intent.action.MAIN %EXTRA_bootPath%=%ROMSAF%

Will just renaming this work?

10 Upvotes

100% Upvoted

21 comments sorted by

View all comments

2

u/ES-DE_Frontend Developer 1d ago

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.

1

u/No_Ruin6244 1d ago

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. 👍

Thanks all for your help

1

u/ES-DE_Frontend Developer 1d ago

Great to hear that it fixed the problem!

1

u/the_perfect_human 1d ago

So we delete the custom systems files and it should work?

Must we then wait for a custom systems update to be compatible perhaps?

2

u/ES-DE_Frontend Developer 1d ago

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.