FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: jogabs on January 12, 2024, 08:41:14 pm
-
My GSX keeps crashing when my simbrief username is input. When i open it again nothing is show in the simbrief username field. It crashes even trying to get the panic log to work so the only file i can attach is the couatl.err that i put here in txt.
-
Still waiting for some help.
-
Your log is not useful, because it shows a restart AFTER the error.
Since you said GSX "crashes" when entering your Simbrief alias, you should post a log BEFORE you restart it, that is when the error message which say if you want to see the error comes out.
-
Now without restarting.
-
Is not clear from your log (because you renamed it. never rename a file, but ZIP it) if it's the Couatl.ERR or the Couatl.LOG.
The Couatl.ERR is just the panic log that shows just the error, but it doesn't give enough details about it. When troubleshooting a problem, you should enable Logging in the settings, and when the error happens, post the Couatl.LOG file, which is more detailed.
Don't rename the file, but ZIP it and attach the ZIP file to a post, so we are sure which file you posted.
-
It crashes even when trying to mark the option to create the .log file, as i said earlier on this topic.
-
zip file .err file.
-
The Couatl.ERR is just the panic log that shows just the error, but it doesn't give enough details about it. When troubleshooting a problem, you should enable Logging in the settings, and when the error happens, post the Couatl.LOG file, which is more detailed.
Don't rename the file, but ZIP it and attach the ZIP file to a post, so we are sure which file you posted.
-
Lets try it again.
IT CRASHES EVEN WHEN I TRY TO CHECK THE COUATL.LOG FILE TO WORK. IT CRASHES EVERYTIME I APLLY SOME CHANGE.
The only file that i get is the panic log.
-
IT CRASHES EVEN WHEN I TRY TO CHECK THE COUATL.LOG FILE TO WORK. IT CRASHES EVERYTIME I APLLY SOME CHANGE.
There wasn't any need to revert to rude shouting. The GSX manual has the solution to cover this case. Quoting from the manual, Page 34, the chapter aptly named "Enable logging when GSX can’t even start"
There might be cases where a problem is preventing GSX from starting, so you can’t access its interface to enable the Log file that can be sent to support to
troubleshoot the issue.
No use repeating the rest of the instructions here.