As I already replied to you on the MSFS forum:
There wasn't any need to scroll those 38 pages. The GSX manual has a chapter dedicated to exactly that problem, named **GSX Toolbar menu stuck on Loading** at Page 97. There, you'll find all possible reasons and all know solutions to it.
However, to fully understand it, I suggest reading the main Troubleshooting chapter in the manual, which starts at Page 95 and covers all cases where the problem is related to the Couatl engine not started.
I'll add a few clarifications that are not entirely clear in the manual:
- When you just performed an update, the program needs to create its own objects cache, and this process can take (varies a lot depending on your system speed, how many add-ons you have, the antivirus not correctly configured, etc.) from 20-30 seconds up to a minute or so. This means, if you apply one of the suggestions found at Page 97 of the manual, which is to Restart the Couatl engine, if you are doing it during the first startup after an update, you are likely stopping the cache rebuild process, will restart again, and again, because you are restarting it too quickly before giving it a chance to complete. So, the 10-15 seconds of waiting time between restarts suggested at Page 97 of the manual, might need to be increased to up to a minute during the first restart after an update.
- In some cases, when you exceed the maximum limit of Simobjects in the sim, the whole Simconnect engine might break up, so the menu won't come, because the simulator simply stopped to call GSX. Because this is what is **really** happening when GSX "fails" to load the menu. Is not failing anything: it's just *waiting* for the simulator to call it back, because if the simulator won't call us back anymore, nothing will work so, it would be completely useless to show you a menu that will never work anyway so, at least, without the menu, you *know* if there's a problem, but if we let the menu show up without the sim ever calling us back, you might assume "GSX is bugged", because you would see a menu that won't do anything, because the simulator stopped talking to us, so it will surely not accept any commands.
As a general rule:
- If something CAN be fixed by restarting the Couatl engine, we would want to be notified by it, because it's *likely* something we CAN fix.
- If something CANNOT be fixed by restarting the Couatl engine, and it gets automatically fixed by restarting the sim, it's NOT something we can do anything about it, it's just a bug of the sim or a problem of so many objects and/or so many add-ons, that the whole Simconnect connection went broke and simply stopped to connect with us, so it's not something we can do anything about it.
According to your log, the Couatl engine and GSX started fine, and there are no errors reported so, your problem doesn't have anything to do with this thread, which is how to troubleshoot the Couatl engine hasn't started, which is not your case.
Instead, since your log doesn't show any errors, you are likely in the simple "just wait more between restarts" covered in the manual at Page 97.
If it doesn't work even after performing a restart and waiting long enough, you are in the 2nd "Simconnect stuck" case of my previous sentence: where the sim is not even calling us anymore, so you might try restarting the sim or restarting Windows. If it IS fixed by doing that, you can be SURE the problem doesn't have anything to do with GSX and, instead, is caused by one of the reasons I just explained as cause of that problem (too many Simobjects, too many add-ons sending too many commands to the sim, or just simulator bug)
