Except for essentially an "RTFM" and a "read the manual" (which only advises to restart couatl - which does NOT fix the problem - I couldn't get any answers...
Of course it fixes the problem, as explained so many times:
- If you have just updated GSX, it will rebuild the models cache on the next startup, so it's NORMAL it will take longer to start. But, if you restart again
while is rebuilding the models cache you are causing the problem, because you are forcing it to start another cache rebuild from scratch on restart, so if you keep insisting on restarting, it will never complete, so it will never start.
This simply means, after having run the FSDT Live Update, you must just wait LONGER before deciding to restart, because most of the times is not even required, you only had to wait.
- Assuming the Couatl engine IS running (if you can restart it, it's assumed it *is* running), when the menu appears to be stuck there, it's because GSX is WAITING for the sim to call it back, and this requires both Simconnect and WASM working. If you have too many add-ons sending too many Simconnects commands OR you have a problem with another add-on using WASM that might have caused the whole WASM subsystem in the sim to either crash or malfunction, the menu might come even later than normal, even if GSX didn't had to rebuild its model cache, because the *whole* Simconnect is slowed down, or possibly stuck.
- As explained on the manual, a possible reason why Simconnect might be stuck, is having reached the maximum number of Simobjects in the sim, usually due to too much AI Traffic and/or too dense scenery and/or too high settings. If this happens, Simcoonnect first slows down then it eventually breaks down, requiring a simulator restart. If a simulator restart FIXES the problem, that's your proof the problem was this one.
