FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: SuperSixBravo on October 24, 2022, 11:17:07 pm
-
Hi all,
I have a problem with GSX, it was fine before I have updated it using the latest version off line etc.
GSX works fine at the departure airport, but when I arrive at my destination airport (Simbrief imported ok and loaded the AC fine at the dep airport) but when I land and pull up at the gate, engines off etc, GSX just gives me the Spinning "Loading"
Cany anyone advise on this, I cant deboard my PAX or anything.
Many thanks.
-
I have the exact same problem. When I arrive (I tried different planes - PMDG 737-800, FBW A32NX - and about 5 different airports, both default and custom, with and without custom .ini profiles) and try to load the GSX menu to pick a parking spot it's just spinning infinitely. After minimizing the game it appears couatl is no longer running in the tray - I have no idea when exactly it stops, other that I am using it successfully earlier at the departure airport. After restarting couatl and returning to the game, GSX starts working again.
-
Same problem here. I also tried different airports yesterday with the latest version of gsx.
-
Please confirm if this happens only with the SU10 Navdata enabled, or it's unrelated to it.
-
I am using VR, SU 10 enabled, using MSFS SU11 beta. I found an error file from the 23rd (see attached). I just did a quick flight from EDDB to EDDF. Same problem. After landing the menu is just spinning. Please find attached the log from the latest flight. I will do the exact flight now again without SU10 enabled.
-
I just did a quick flight from EDDB to EDDF. Same problem. After landing the menu is just spinning.
Check if the Couatl program is still running by hovering over its icon in the Tray bar, and see if it works if you restart it manually.
-
I checked it. And is was off. It started itself again after I returned to MSFS Main menu.
-
I tested the same flight EDDB - EDDF disabled SU 10 API before starting MSFS. After landing the menu is loading and loading like before and a follow me car is coming. Closing the gsx menu made the follow me car disappeared. Opening the menu again (never ending loading) the follow me car arrived again. After arrival at gate and engine shut down I got the voice message, that I have arrived at the wrong gate and deboarding starts. But I couldn´t choose a gate before because of the menu is loading and loading. At this time GSX icon was all the time visible in tray.
I have attached the new log file. But gsx produced a new one after the flight (maybe after I exit to MSFS main menu?).
-
I will do the same flight again. I will save the log file before exit to MSFS main menu.
-
I restarted my PC and the I did the same flight again with SU10 API disabled. This time I had no issues with gsx. Everything worked.
-
I just did another flight from LEPA to EDDB. SU10 disabled like before. Same issue. After landing the menu is loading and loading. The tray icon is still visible. This time I haven´t return back to MSFS main menu. Please find attached the log file.
-
As I wrote the other post before, MSFS was still running. I have now restarted GSX via the tray icon. That's the only way I could start the deboarding now.
-
Can confirm too, although I only tested this with the SU10 Navdata API enabled. I "close" GSX after takeoff via the toolbar (so it isn't highlighted). When I arrive at my destination I have an endless loading menu when opening it again. When I then check my traybar icon and hover over it with my mouse it disappears. Seems Couatl silently crashes during the flight.
After a manual start GSX works again. Unfortunately I cannot provide a log right now as I've forgot to re-enable it after my last reinstall, but I'm happy to add one afterwards if needed.
-
same problem here
-
I tried to make a flight, and I cannot reproduce the problem. It would be helpful if you could provide some info about the flight you took, and the route taken.
-
I just finished a flight with PMDG 738 from WMKK to VTBS using simbrief flightplan. Departure RWY 32R. Arrival RWY 01L. FL370. SU10 API disabled. Using SU11 beta. I haven´t closed GSX in MSFS toolbar. After landing I called GSX menu. It opened. I wanted to choose a gate. As soon I pressed "suitable gates" the menu closed itself. Recalling the menu ended up in never ending loading. I parked at Gate C3. At Gate C3 I had installed before a gsx vdgs system. I could see the wall mount 42. But no text on it. The gsx tray icon is still visible. Please find attached the log file.
-
I did the same flight again. This time I closed the gsx icon in msfs toolbar after takeoff. After landing I activated it in msfs toolbar. Then the same issue like the flight before.
-
Please confirm if restarting Couatl from the Traybar icon will fix the problem.
-
Yes it fixes the problem
-
Same error for me. Couatl program is NOT running at the destination airport. I always need to launch the "start Couatl for GSX MSFS" icon, every time.
VR using the SU10 Navdata API enabled option. Never had this problem before the update.
-
I have the same problem since using the SU10 Navdata API, every flight I made since the activation GSX works fine on the departure airport but wont load at the destination airport. When i hover over the taskbar, the couatl logo disappears. My guess it closed itself some time during the flight. When I manually open the couatl by "Start Couatl for GSX MSFS", GSX works again.
Best,
Alex
-
Please confirm if restarting Couatl from the Traybar icon will fix the problem.
It has been happening for me for a while no matter what my departure and arrival airports are. It works on departure, gets stuck in the loading loop on arrival.
Restarting Couatl in the tray fixes the problem.
I have the SU10 Navdata API turned off.
-
yep having same issue i dont even have to make a flight plan just flying between two airports causes it. Su10 data is on hovering mouse over the couatl icon in tray the icon vanishes i can restart it from a shortcut on desktop then works fine
-
Happened again. Log attached.
-
I still can't believe the logfiles have no timestamps...
With timestamps one could see at which point in flight Couatl decided to stop.
I mean, come on, logfiles aren't rocket science, there are common best practices to properly deal with them...
-
It happens almost 100% of the time now, the only fix is to re-start Couatl
-
Are you investigating this @virtuali Umberto?
-
I have the same issue. It seems that the Coatl app has quit during flight or arrival because when I hover over its icon it disappears.
-
I have the same issue. SU10 API enabled.
Loaded at Airport KSJC. Opened GSX. Endless Loading. Nothing more happened.
Tried to close Couatl in TaskManager. Noticed, Couatl was not running. Tried to start it manually.
Appeared for 1 sec in TaskManager then automatically closed itself. Tried several times. Same results. I was not able to start the script at all.
It crashed 1 sec after starting the script.
After landing at destination (KJAC), tried to start GSX in the sim. Again. Endless loading.
Checked the TastManager. Script was not running. Tried to start it manually. Nothing happend at all this time.
I was not able to start the script.
I noticed during my last couple of flights that the Couatl script was not visible in the "Background process"-section of TaskManager when using the new API.
It usually did appear there before. But since using the new API it is not listed in the TaskManager anymore.
Went back to the "classic" GSX without SU10 Navdata API.
GSX works properly and Couatl is showing up in the TaskManager again.
I can manually close and start the sctipt without issues.
Seems there is something wrong with the new SU 10 Navdata API.
Somehow it instantly crashes the script and its not possible to start it manually anymore. Or start it at all.
So if you guys have the issue with the endless loading. Disable SU 10 Navdata API. Then GSX works fine again.
-
Seems there is something wrong with the new SU 10 Navdata API.
Somehow it instantly crashes the script and its not possible to start it manually anymore. Or start it at all.
So if you guys have the issue with the endless loading. Disable SU 10 Navdata API. Then GSX works fine again.
This may be true for some, but not for me. I have the spinning on departure every flight and have not yet turned on the SU 10 Navdata.
-
I also had checked the SU10 API enabled box. I flew 3 different airports. At start all worked well. I flew to destination airport and got to gate. Shut off engines. Tried to start GSX and just got program spinning and loading. Would not start. I unchecked the SU10 API and restarted sim. All back to normal starting, Landing at gate and restarting GSX after engine shut down.
-
Please confirm if restarting Couatl from the Traybar icon will fix the problem.
Confirmed. At 100% of the usage in every single flight the couatl Engine crashes exactly 1 time. So thats the reason why you see a spinning wheel when opening GSX in the menu bar. Restarting couatl via the system tray is solving the problem. Couatly get started and the GSX menu in the sim via the simbar is opening like it shoot.
-
Are you investigating this @virtuali Umberto?
We obviously are, and we gathered enough evidence from all these reports than the problem is not GSX ( it almost never is ), but it's the simulator that for some reason just stop calling GSX code back, which is how Simconnect normally works: your code is executed when Simconnect calls you back, so it seems it get stuck for some reason.
We think this might be an inherent Simconnect problem that possibly have been there since FSX, and a possible solution, is to add a "watchdog" code to ensure Simconnect is calling us and, if no calls arrive after a given amount of time ( like 30 or 60 seconds ), we might just do auto-restart, which will re-establish the connection.
We are working on the update right now, but it's not done yet.
-
Thank you Umberto
-
Hi Umberto, I am not sure if you have made any updates to resolve this problem yet, but GSX Pro still never works at the destination airport for me.
-
Hi Umberto, I am not sure if you have made any updates to resolve this problem yet, but GSX Pro still never works at the destination airport for me
We haven't done any updates, since we never be able to replicate this, GSX works at the destination airport 100% of the time here.
That's why I'm trying to gather some evidence, because any eventual fix is done "in the blind", without any hint about what is causing it but, if you read my previous post, the last evidence SEEMS to suggest that Simconnect simply disconnected, and I'm afraid this might be caused by using too many add-ons calling into it, possibly triggering some kind of bug in the sim itself.
It might be helpful if you provided with extra information, like:
- if you are using the SU10 Navdata option or not
- which other add-ons you use
- if you can fix the problem by restarting Couatl from the Traybar icon ( or starting it from the Desktop icon ) before landing.
-
Hello,
The problem still persist.
Today on all of my flights at the destination airport the GSX window was just spinning, manual start of couatl was required.
EGLL (Asobo), Fenix A320
LHBP (LHSimulations), PMDG 738
Is there any progress here? Seems this problem is existing since 6 months now.
-
There isn't any progress because, as I confirmed multiple times, we were never be able to reproduce it.
As already discussed several times on this forum:
- Several users reported the problem fixed by ENABLING Windows 8 Compatibility for the Couatl64_MSFS.EXE. Since those users were the majority, this option is now enabled by default.
- A few users reported the problem is fixed by DISABLING Windows 8 Compatibility for the Couatl64_MSFS.EXE. These very very few, but it's possible you might fall into this case.
- Some users also reported the problem to be fixed by also setting the "Run As Adminstrator" flag for the Couatl64_MSFS.EXE file.
I can only confirm I see no difference whatsoever, no matter the options used, it never crashes for me so, I can only trust other users reports and offers suggestions to try.