-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RMG no longer launches following update on Feb 9th #337
Comments
Please read the notes of v0.7.3: https://github.com/Rosalie241/RMG/releases/tag/v0.7.3 |
I did that but it still wouldn't launch either. You might want to look into this |
Have you tried v0.7.5 yet? it fixes a crash someone was experiencing. |
I had. I updated it today when prompted to. I even had went thru and insured thru portable edition that it was busted |
The problem is that it's incredibly difficult to guess what the issue is when I'm unable to reproduce it on windows 11 or Linux on my system, the crash that I mentioned in my previous comment was only fixed because someone who had the issue was able to show me x64dbg screenshots after me guiding them through that process.
I'm sadly unable to reproduce your issue so it's difficult to guess where the issue lies unless I get a core dump of the crash, get a debugger stacktrace or unless I somehow add a stack trace logger after a crash to RMG. |
It does seemingly work on a clean install, but not when updating the previous version, either via installer, or portable edition. Don't think it is genuinely a good idea to break this and force people to re-install from scratch. |
That is expected, the notes from v0.7.3 mentioned it. |
Recently, I've tried to boot up RMG on my Windows 11 machine after having updated it on February 9th, and as of now it seems like the emulator can no longer launch. I've double-clicked to start the program several times to no avail, and updating the program caused it to be labeled by Windows Security as potentially dangerous after extracting the newest release of the emulator (but did not remove the program after scanning it)
The text was updated successfully, but these errors were encountered: