You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Diagnostic Mode toggle menu option always says "Enabled" regardless of the state of that setting and the game fails to launch with it enabled.
Steps to reproduce
Start fresh launcher instance
Enable Diagnostic Mode (Accept to install procdump)
CelesteConfig.xml will reflect Diagnostic Mode being enabled but the settings button will still say "Enable Diagnostic Mode"
Click "Play" in the launcher. Game will fail to start
Click "Enable Diagnostic Mode" in the settings again (To disable it, even though it says "Enable")
Change is correctly reflected in CelesteConfig.xml so it is actually disabled
Click "Play" and now the game opens fine
Expected behavior
Diagnostic Mode toggle menu option correctly updates to say Enable/Disable depending on setting state and game successfully launches with it enabled.
Extra
Reproduced on my personal machine. First discovered on another user's machine. It does launch procdump and Spartan.exe briefly but they exit before anything is ever displayed to the user, failing silently. There are no errors or warnings related to this in any of the log files or even in the windows event viewer.
The text was updated successfully, but these errors were encountered:
Describe the bug
Diagnostic Mode toggle menu option always says "Enabled" regardless of the state of that setting and the game fails to launch with it enabled.
Steps to reproduce
Expected behavior
Diagnostic Mode toggle menu option correctly updates to say Enable/Disable depending on setting state and game successfully launches with it enabled.
Extra
Reproduced on my personal machine. First discovered on another user's machine. It does launch procdump and Spartan.exe briefly but they exit before anything is ever displayed to the user, failing silently. There are no errors or warnings related to this in any of the log files or even in the windows event viewer.
The text was updated successfully, but these errors were encountered: