I did a couple flights earlier today in the Fenix with GSX integration and did not have any freezing or crashing of GSX. I’m not sure which announcement add ons you’re referring to but the cabin announcements that are in V2 don’t seem to cause any issues with GSX. I’d need to find the time to do more flights since it’s hard to draw any conclusions from two. So far though no GSX issues with boarding or deboarding.
I don’t think it’s because of Fenix. I use GSX with various planes and it crashes or freezes randomly, without any apparent reason. It’s the most unstable piece of software I ever used. I got used to it many months ago :).
2 Likes
The same here, but with FBW. Since last update GSX behaves a bit strange in some cases.
For example, in EDDK (AS), GSX crashes with errorlog when starting the Baggage cart.
In that case the cart has no trailers.
In EDDH (AS) the Baggagecart is complete, but can´t find a good path to the plane.
In another cases the cart shows only one trailer but behaves like tree ones.
Hope that helps to find some bugf, if so…
I will also try again tonight of tomorrow evening. Lately i didnt experience any GSX problems. Except after the latest GSX update and Fenix update it crashed a couple of times and i get a lot of freezing at airports. It’s gone from the moment i am more or less up in the air and it starts again when selecting a parking under 10000ft
There is a new option in GSX that disables it when your are above a certain flight level and re-enables it when you descend. Check if you have it ticked.
You should report this on FSDT support or the GSX channel on Discord and, the most important thing is of course the error log. This is not really the place to do troubleshooting but, of error logs are posted and they can be reproduced, the fix is usually posted very quickly.
The minimum number of carts (now variable) is 1 so, it’s not normal you have a baggage cart with no trailers and, looks like to be caused by having exceeded the maximum number of simobjects in the sim, usually caused by too many AI and too many objects in airports.
When the maximum number of objects is exceeded, not only MSFS won’t accept creating new ones (which explains why you had a tug with no trailers), but Simconnect will start to break apart, probably due to a lot of errors about the maximum number of objects, but that’s not also a given, sometimes it just stop working correctly, and that’s it.
The error log might help understanding if this is the case.
We heard reports of users saying it crashed silently with no error logs when selecting a gate and, after many tests, this could be reproduced more or less reliably.
Many months ago, when the Navdata API just came out with SU12, we got reports of crashes in flight, likely related to the Navdata API and, lots of users said setting Windows 8 compatibility for the Couatl engine helped. I couldn’t find any reason a program that is compiled using the current Windows SDK would run better with Windows 8 compatibility, but since it didn’t seem to cause any problems either, and some users said it really improved stability for them, we added it by default.
After SU13 came out, from the release notes, we learned those freezes/crashes were, in fact, bugs in the Navdata API itself, which are supposed to be fixed in SU13. Maybe not all of them are, which would explain why somebody might see a crash of the Couatl engine under 10k feet, because the ONLY thing it does when you are in flight, is to ask Navdata about the nearby airports, so you can pre-select a gate in flight so, and it’s a very simple task not remotely comparable to what happens on ground, suggesting the Navdata might still have issues.
With SU14 and now with SU15 Beta, it seems the Windows 8 Compatibilty flag not only is not required anymore but, it did more harm than good because, with SU15 Beta, we could reproduce a crash when selecting a gate on ground fairly consistently, like 1 out of 3 tries, especially after first entering in a session, that is when MSFS started the Couatl engine automatically.
After removing the Windows 8 Compatibiltiy setting, we couldn’t reproduce ANY CRASHES, no matter how hard we tried. As if, trying 10-15 restarts in a row, at different airports with different airplanes using different services. Zero, nothing.
Note that, every time I say the word “Crashes”, I mean the Couatl engine disappear with no errors logged, just an event in the Windows Event Viewer, and the Couatl icon gone from the Taskbar.
I’m not referring to logged error, which are not “crashes”, they are just errors in the GSX scripts, so the Couatl engine is cleanly reporting those, so we can take action and fix them (if people report them),
Also, I’m not referring to crashes of the sim itself, which cannot be caused by GSX or the Couatl engine, which runs externally, so it can’t just crash the sim, but can be made crash if the simulator crashes for other reasons.
In any case, we decided to disable the Windows 8 Compatibility flag in the last update, since it clearly improved things dramatically.
That’s why it’s puzzling to read a report saying the opposite: could be that in your system, Windows 8 Compatibility was really helping before?
Try setting it back and see if it makes a difference for you.
And please, it would be best if you post your findings on the FSDT support forum or the GSX Community channel on Discord, because this is not really the proper place to do troubleshooting.
1 Like
Coautl is dissapearing from the toolbar. But i will try to signup on discord. No error messages btw
I guys
I accedently baught a wrong product from FS dream, insted of buying GSX pro for MSFS i baught GSX bundle with GSX Level 2 Expansion, I mailed immidiatly to FS dream but no answer yet, any suggestion please ?
I’m sure they’ll sort you out, they are a reputable developer, give them a couple of days to respond to the email.
1 Like
That’s because you emailed us at 4:25AM so, even if it wasn’t technically Sunday anymore, at least take into consideration that not everybody lives and works in the same Timezone.
Of course, the email has now been answered, with instructions on how to exchange the FSX version you bought by mistake, with the MSFS version.
Next time you complain in public about any company “not replying”, AT LEAST wait the customary 24 business hours, and consider time zones as well.
12 Likes
disabled navigraph from my fenix v2 ESB and everything works normal… so not gsx but navigraph caused the issue… And now i think of it, since the new navigraph look i had some hickups in the sim
Just wanted to express my appreciation for your endeavours in keeping the addon improving. I remember a ‘searching start’ some while back but ever since you sure made up for it. Thanks for that, I love using the addon and the direction you’re heading into with it.
1 Like
I got an email from FS dream, so kind and professional, they will refund me. and i just bought the gsx pro for msfs 2020, thankx guys
9 Likes
I’m currently having an issue with GSX Pro where it seems to be freezing or locking out mid flight and it won’t work at arrival airport. It’s perfectly fine throughout departure phase. This is happening repeatedly and is a new issue for me.
Win 11. Decent build. 4070 Ti Super, 14600k, 32 gig ram etc.
Aircraft is Fenix A320. Not tested in other aircraft.
Anyone else having a similar issue?
There is a new option to disable GSX during cruise for people having this issue. Have you tried this option?
In order to the issues i have had… I think it was the rolling cash at most.
I forgot to switch ´em off again. Normaly i don´t use the cash, because of upcommig issues each time. And yes, same here again. Switchin OFF, problems away …
I’m more curious as to why you’d be using it midflight, what am I missing? 
I just have the couatl.exe mapped to a button on my streamdeck as 99% of the time when I have GSX issues it’s because the service crashed so I just push to restart and away we go.
Version 2.9.6 – March 21st, 2024
-
GSX Pro New: New method to start and restart the Couatl engine, using an auxiliary helper program which will be started by the sim (couatl64_boot.exe), which will monitor the Couatl engine and will restart it automatically. The program will exit automatically when the MSFS session ends.
-
GSX Pro Change: Windows 8 Compatibility setting enabled again following user’s feedback. The new restart method using the helper program, should fix any issues of the Couatl engine missing on arrival in any case.
-
GSX (all versions): Some GSX settings that might affect 3rd party automations can be read and optionally set.
-
GSX Pro (Change): Updated manual, covering the new developer features.
6 Likes
Can you still stop Couatl manually?