Closed Tartellu closed 5 months ago
I don't know what you did, but there is nothing right with this set up, your game location is in program files but somehow it looks for "launcher.exe" in system32? Anyway, best move is to reset the Manager, go in AppData -> Local and delete the folder SAManager.
The system32 path may be from launching the program with admin rights. Maybe the Manager was trying to run Launcher.exe
using relative paths?
Ok so I did try a couple of your suggestions, I tried deleting the folder in AppData and I still got the same error. I decided to go back to the old launcher and found that it also gave me the same error, I even uninstalled and reinstalled the game. I think it is something on my end, the launcher works perfectly fine with SA1 but when I launch SA2 it will recognize mods but will crash. I first downloaded this launcher through the upgrade path provided through the old SA2 Mod Loader. I think my SA2 has always been broken for me as I only recall getting it to work once with my game so I don't think its anything wrong with your program. Sorry that I left such a big comment but thank you for helping me!!!
Do you have sonic2app.exe? The error mentions launcher.exe, but the Manager originally uses sonic2app to start the game, if you renamed it, it won't work.
yes, I validated my files and replaced it. The old mod manager would strangely boot into the sonic2app but would take forever to load once I got into the game, the new one won't even do the for me.
Can you try to manually re set the game location in the Manager Config tab?
Yes, I moved the game files to my desktop and it still crashes.
Found the issue, it was related to custom executables included with mods. Whatever mod you're using that did this is probably not something you should be using. Mainly because it's using Launcher.exe
as its executable name, so it's either some customized launcher (which is maybe fine to use) or it's just a mod packaged with the game's shoddy launcher program or a renamed sonic2app.exe
(or the decrypted executable) under the title of Launcher.exe
Regardless, thanks to this report, we found the bug and got it fixed as of bf7be21.
Exception Report