I.s.o adding Beta-channels and ‘upcoming features’, could you please finally start fixing the “waiting for the Couatl engine…” and “Waiting for the GSX Menu…” -issues. And STOP denying that there ARE issues?!
Then I suggest to read again what I just wrote in the previous post:
this first public Beta focuses on fixing the menu stuck on Loading in some cases.
3 Likes
@Umberto67 I am getting this error in 2020. I am on the latest GSX update. I’ve manually restarted Couatl multiple times and even given it Administrator’s permissions.
As you can see from my previous post, we posted an update that might fix this in the Beta channel, and in fact I would very interested knowing if it fixes it for you.
Of course, the update will go in the Release channel as soon we could get some feedback by affected users, because I was never able to replicate this, so the fix is done basically by guessing, and also taking into account that some systems might be slower than expected.
OK, in the meantime I have uninstalled GSX completely and reinstalled, I am booting up the simulator to test now. If that doesn’t work I will try the Beta version. Thanks!
EDIT: Uninstalling and reinstalling did not work, so I am now trying the latest Beta update.
A question about how GSX reads the path: %appdata%\virtuali\gsx
Sometimes certain GSX profiles come with multiple options; for example, one profile for winter operations and one for summer operations. If I create a subfolder here or have multiple original unzipped folders for later use, could this conflict or would GSX Pro only use what is at the top level of this path above?
After switching to the new Beta, nothing has changed. Still getting the same error message.
The Beta is supposed to fix the menu stuck but, the whole point of the message, is to alert you if something wrong happens so, maybe, the couatl engine really hasn’t started, so in that case the message is correct to appear.
This is not really the place to do troubleshooting, if you want a quick solution, I suggest checking the GSX Community channel on Discord, where we can understand what is your case.
No, Couatl has certainly started. I verified and even restarted it myself. The app just refuses to work.
Fact it has started, doesn’t guarantee there aren’t any other issue that will prevent GSX from starting. At that stage, GSX is waiting for the sim to call it back, that’s is the most common case if the menu get stuck, and no amount of coding on our side can fix that, the best we can do is to alert of the problem.
As I’ve said, this not really the to do troubleshooting, if you want a quick solution, I suggest checking the GSX Community channel on Discord, where we can understand what is your case.
All right, I will give it a shot. Thanks for your help!
Hello, just a question. My flightsimming was out of order for around three month, because of a PC crash. Since a bunch off weeks i´m back. Looks like i have missed somethings here and there.
OK, the question, where is the “extra ground clutter” checkbox gone ??
It’s gone: the installer now installs by default the lightweight version of the GSX Jetway replacement files, so we can contribute better to stay within the max Simobjects limit.
Note that, that option was only relevant to the GSX jetway replacement files, which were only used on default airports, so if you previous had to disable it because you suspected issues with too many Simobjects, that option wouldn’t haven’t done anything on 3rd party (but even handcrafted/premium airports) airports anyway, and the extra clutter would have been enabled only there, it won’t make any difference on non-default airports.
Covered by Umberto above: