FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: flare_alfred on February 19, 2025, 04:31:05 am
-
I noticed that the number of passengers boarding on GSX was different from usual.
In Simbrief, there were 20 people, but nearly 100 people boarded.
The GSX function itself was working correctly, but I remembered that I had reinstalled GSX due to a sound problem, and realized that I had not entered my Simbrief username into GSX. But in the end, even if I entered my Simbrief username, it was not reflected.
The details of the problem are below.
I also took a video.
1) I opened the GSX settings screen, entered my Simbrief username, and clicked the Apply button.
2) The GSX settings screen closed even though I had not yet clicked the OK button, and MSFS also became unable to accept any keyboard input (ESC key, etc.).
3) I waited 10 minutes and still could not do anything, so I forced MSFS to close and restarted it.
4) I started MSFS, boarded the aircraft, and then opened the GSX settings screen to check, and none of the settings changes I had made were reflected.
5) I opened the GSX settings screen, entered my Simbrief username and pressed the Apply button, but I was unable to operate MSFS either. (I couldn't enter any keys, but TrackIR was working.)
6) I waited 20 minutes, but still couldn't operate MSFS, so I used ALT+TAB to switch to the desktop and then back to MSFS.
7) I was able to operate MSFS and GSX worked, but all the settings I'd made were back to default.
8) I uninstalled GSX.
9) I reinstalled MSFS.
10) I reinstalled GSX.
I tested it, but the symptoms didn't change.
However, the GSX functions themselves are working properly, so the settings just aren't being reflected.
Please tell me what to do.
<Notes>
- The following folders have been set as exclusions in the antivirus software.
- Antivirus software was stopped when testing
- Windows 10 64bit (Japanese)
- Memory: 64GB
- SSD: 1TB free
Thank you.
-
Please provide your error log because, the Apply button not turning grey after having clicked, usually indicates an error.
-
Is this file ok?
-
You should enable logging, because the .err file might not include all information we need about the error. After enabling logging, the new file will be called Couatl.LOG instead, and be sure to take if after you opened the dialog and pressed Apply with no effect.
-
There is an option in the dialog to enable logging, but even when I turn it ON the change is not reflected so I cannot take a log.
There was no log file in the C:\Users\****\AppData\Roaming\virtuali folder.
Is there any other way to create a log file?
-
The log will appear on the next restart only, and if the option is enabled, you can be sure a log file will be created. The Sticky post in this section (and the manual at Page 38) explains how to enable logging manually, without the user interface.
-
I followed the instructions on page 38 of the manual, added the line logFile="couatl.log" to Couatl_MSFS.ini, and started MSFS.
However, the error shown in the attached image occurred.
I also performed a clean uninstallation of MSFS and GSX pro, then tried installing them again, but the result was the same.
How can I get the log file?
-
Couatl_MSFS.ini file.
-
I can't get an answer, what should I do?
Thankyou.
-
How long should I wait?
-
Your error is caused by the incorrect usage of double quotes, possibly because you might have used a word processor instead of a pure text editor to edit. If you NEED logging, you should change the file (with a pure text editor like Notepad), from this:
logFile=”couatl.log”
to this:
logFile="couatl.log"
Note the different type of double quotes used, the 2nd one is the "standard" type, the first one is the one used by word processors to make them more similar to the one used in books, but it shouldn't be used in this case.
If you don't NEED logging now, just remove the file, and the error will go away.
-
Thank you for the information.
I have obtained the log file, so I will attach it.
I would appreciate your help in analyzing it.
-
You posted a log with no errors. You must take it after the problem with the Apply button comes out.
-
Of course I clicked the apply button and got the logs right after the same problem occurred. It's clear from the timestamps.
Does this log not capture all errors?
-
Of course I clicked the apply button and got the logs right after the same problem occurred. It's clear from the timestamps. Does this log not capture all errors?
Check again, there must be an error, but it wasn't in your log.
-
I clicked the apply button to trigger the issue and repeated the process at least three times.
I have confirmed that the timestamp of the log file is the timestamp of the test immediately after it was run.
-
Your log still has no errors and I don't know which timestamps in the log you are referring to, since the log doesn't have any timestamps.
-
I don't understand what you mean.
The log has a timestamp that matches the time I started MSFS in my tests.
"log started on Mon Mar 24 12:23:22 2025"
Are you saying I didn't test it?
Thanks.
-
I meant you could refer to timestamps of the individual lines, not just the starting time.
-
To summarize your opinion, this error is an unknown phenomenon, and no matter how many times the test is repeated, the error is not recorded in the log, nor are the timestamps of each line recorded, so the cause cannot be determined.
In other words, does this mean that the problem I am having cannot be fixed?
-
Until you can provide with an error, I can't even being to understand the issue. Nobody else reported it. Are you using a non-Western version of Windows perhaps ?
-
Yes, I am using Japanese Windows.
Is the sound not working issue the same?
-
Yes, I am using Japanese Windows.
Is the sound not working issue the same?
Yes, very likely. We'll probably fix all these issues with non-Western windows for the next major update, which will move the whole code to Python 3, which is natively all Unicode. In the meantime, try the option to set the "Language for non-Unicode application" to English in the Windows regional settings.