You haven't posted the Coautl.LOG file but, instead, the Couatl.ERR panic log, which is a shorter log that is always enabled even with logging is disabled, but doesn't contain enough information about the problem, so it would be best if you enabled logging and, upon the error, post the Couatl.LOG file instead.
Looking what is there in the log, it seems GSX got bad data from Simconnect, the infamous error #99, which is a Simconnect internal error, which indicates something is wrong.
Bad data can come for a number of reasons:
- The scenery has a problem, like a missing jetway (scenery trying to use a jetway model that is not available), but you said it happens "everywhere", so this seems to be unlikely.
- You are using a 3rd party scenery, but you haven't disabled the GSX Jetway replacement file for it, as you always should with any non-default airport. This creates a conflict which results in getting bad data about jetways and their association with a parking. I'm not saying I'm sure you did this, but precisely since I cannot possibly know, I need to list this case as possible too.
- Simconnect is just being broken by having reached the maximum number of objects allowed in the scene, after which it starts to returns erratic results and bad data. This is usually caused by too much AI traffic, especially with AI Injection, and way more easily at large airports.
