FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: Deltatristar500 on November 22, 2022, 07:21:08 pm
-
Hi, I cant get my GSX to come up for gate information once I land at any airport. Is there something I need to do on my part? I have the most recent update from the manual link here in the forums, then update GSX from the app afterwards.
-
Have you enabled the SU10 Nav API option? The spinning circle (in my experience) is when the airport cache is loading (it could take a while which isn't ideal when you just vacated) OR coualt has crashed and you need to restart. The Nav API does away with caching altogether and personally I have had much better experience with it enabled.
-
How long do I have to wait? I do have it enabled
-
If you have Nav API it should be pretty instant, have you checked coualt is running or if it is, restart it then hit GSX from the toolbar in the sim.
-
Hi, I cant get my GSX to come up for gate information once I land at any airport. Is there something I need to do on my part? I have the most recent update from the manual link here in the forums, then update GSX from the app afterwards.
What you could check is if Couatl is still running.. :D This happens for me too almost all the time. When I then hover with my mouse over Couatl in my tray (taskbar next to the clock) the Couatl symbol just vanishes. I then have to start Couatl manually again. Happens since one of the last updates I guess but I alway forget to check the log.
What might have helped (I have to re-test it to validate) is to close GSX (via the ingame menu, so that the icon is not highlighted) after departure or pushback and then to just start it during approach (once you're below 10.000 ft, before it won't open as you're too high). After that Couatl kept working, but I'm not sure if this is just a coincidence.
-
I have this issue also everytime, i have su10 nav enabled, wondering if i should revert back but su10 nav is much faster lets hope its gets fix in future updates. But at this stage we never get new features due to all su10 and su11 bugs that are introduced.
-
There IS a reason why we haven't jumped on using SU10 Navdata by default, and it's because:
- Is still not complete for what we need, let's hope today's SDK Q&A session will answer our question about the missing features, which was the most voted one:
https://forums.flightsimulator.com/t/sdk-q-a-ask-your-questions-here/552074/11?u=umberto67
- It MIGHT have issues, I think we were the first developer to have added full support for it, so there might be unknown or undocumented side effects we are still working to understand.
-
You recommend us to switch back to non su10 nav for the time being?
-
You recommend us to switch back to non su10 nav for the time being?
Well, if you never had issues with the airport cache before, and you are not using Marketplace airports, it might work better.
-
You recommend us to switch back to non su10 nav for the time being?
Well, if you never had issues with the airport cache before, and you are not using Marketplace airports, it might work better.
My log shows the airport it has a problem with. Tonight the last entries are ORUQ
-
My log shows the airport it has a problem with. Tonight the last entries are ORUQ
Please clarify if that's the airport you departed from, the airport you are arriving to, or just an airport you passed by during the flight.
-
My log shows the airport it has a problem with. Tonight the last entries are ORUQ
Please clarify if that's the airport you departed from, the airport you are arriving to, or just an airport you passed by during the flight.
All recent reports of this issue I've seen were about the endless spinning at the arrival airport.
Usually it helps restarting Couatl, so I doubt that it's the SDK at fault.
I usually preselect the gate prior landing and for me with SU10 Navdata API I usually press "Request Deboarding" and it stays in the state "Deboarding requested" indefinitely. Restarting Couatl fixes this issue, I can request deboarding with nothing changed apart from the Couatl restart.
On the Discord there's a very long thread, you might want to read it there:
https://discord.com/channels/1011680327346966590/1035644377302847488
-
My log shows the airport it has a problem with. Tonight the last entries are ORUQ
Please clarify if that's the airport you departed from, the airport you are arriving to, or just an airport you passed by during the flight.
I did not visit the airport, it is in the region I was flying to. I have a new airport error also not an airport I landed or departed but in the Middle East region.
After landing and I get spinning menu when I want to select my arrival stand, starting the app in the start menu, the GSX works Ok after the restart.
I do not have sceneries for any of these airports. I am using the MSFS Beta.
-
I have a new airport error also not an airport I landed or departed but in the Middle East region.
Which error ?
-
I have a new airport error also not an airport I landed or departed but in the Middle East region.
Which error ?
The spinning menu error. That was the end of the log before I started the couatl service
-
I have a new airport error also not an airport I landed or departed but in the Middle East region.
Which error ?
Updated Dec 13th version of GSX and same issue after landing anywhere the spinning menu happens I start couatl again through the start menu short cut and it works.
-
Updated Dec 13th version of GSX and same issue after landing anywhere the spinning menu happens I start couatl again through the start menu short cut and it works.
Are you using the SU10 Navdata ? If yes, have you noticed if it still happens if you disable it ?
In any case, we had another update today which fixed a bug with airports that had their name of exactly 32 characters ( the maximum supported by the Navdata ) when they were loaded with Navdata. It's POSSIBLE encountering any of these during flight might have cause that crash so, try the new update and see if there's an improvement.
-
For me this happens on every single flight (SU10 nav data API is active), so I highly doubt that it's because of specific airport's names.
It happened all over europe on flights with the following destinations:
LIRF from MK Studios
EFRO from MK Studios
LOWW from Gaya
EDDM default scenery
VQPR default scenery
EDDB from Aerosoft
...
-
For me this happens on every single flight (SU10 nav data API is active), so I highly doubt that it's because of specific airport's names.
I never said I was sure it would fix it but, we surely had a problem with those specific airports so, we fixed it, both because they weren't editable ( their name appeared corrupted ) and it could have been causing issues like that, since you never know what might happen when there's a stray string in memory, since all our Simconnect interaction is in C++, so issues like these needs to be fixed.
But we are fixing thing in the blind, because we haven't been able to reproduce it, so we can only make guesses.
As explained in other posts, we are trying to gather evidence, and the evidence so far SEEMS to say it's more LIKELY ( which doesn't mean it will *never* happen otherwise ) to happen when the usage of the SU10 Navdata is involved, because while the rest of Simconnect is tried and tested for the last 15 years (and yet there are still bugs in MSFS that never existed in FSX), this is the first time new functions has been added by Microsoft to it, after FSX SP2, so we are really testing something for the first time.
-
Here's by the way my distance after departure when Couatl disappears (see screenshot).
Couatl.err does not contain any recent information, it's last update based on file timestamp was far before I took off.
I just noticed now that couatl.log is not written by default, so I have no .log available. Will check on the next flight.
EDIT: Started Couatl manually after that happened - Now Couatl remained running until arrival with no issues.
Something happens upon departure that lets it quit and it's not something that happens in cruise but at a certain distance from departure airport.
-
Updated Dec 13th version of GSX and same issue after landing anywhere the spinning menu happens I start couatl again through the start menu short cut and it works.
Are you using the SU10 Navdata ? If yes, have you noticed if it still happens if you disable it ?
In any case, we had another update today which fixed a bug with airports that had their name of exactly 32 characters ( the maximum supported by the Navdata ) when they were loaded with Navdata. It's POSSIBLE encountering any of these during flight might have cause that crash so, try the new update and see if there's an improvement.
I did not uncheck SU10 navdata yet. But it still happens with latest update. Start flight, works great, depart, land, try to bring up gsx menu, and it spins, system tray icon disappears. Open shortcut from start menu, gsx works. Many flights one LEMD-EGLL this was the end of the log when GSX disappeared on landing.
-
I did not uncheck SU10 navdata yet. But it still happens with latest update. Start flight, works great, depart, land, try to bring up gsx menu, and it spins, system tray icon disappears. Open shortcut from start menu, gsx works. Many flights one LEMD-EGLL this was the end of the log when GSX disappeared on landing.
All the evidence we are gathering, seems to indicate there's nothing wrong with GSX, it just stops while it was receiving the nearby airports list from the Navdata. Which is why, I asked to try with the SU10 Navdata option Disabled, to understand if the crash is possibly caused by erroneous data being received from the sim.
Also, it might have been best if yYou didn't cut the log and posted a screenshot of what you think it's useful. I need to see the *actual* log, because it contains things we log precisely because we might need them in troubleshooting, which means ZIPPING and ATTACHING the actual log to a post.
Some indication of the route you took would be useful as well. And if you are using extra/3rd party Navdata as well.
-
I did not uncheck SU10 navdata yet. But it still happens with latest update. Start flight, works great, depart, land, try to bring up gsx menu, and it spins, system tray icon disappears. Open shortcut from start menu, gsx works. Many flights one LEMD-EGLL this was the end of the log when GSX disappeared on landing.
All the evidence we are gathering, seems to indicate there's nothing wrong with GSX, it just stops while it was receiving the nearby airports list from the Navdata. Which is why, I asked to try with the SU10 Navdata option Disabled, to understand if the crash is possibly caused by erroneous data being received from the sim.
Also, it might have been best if yYou didn't cut the log and posted a screenshot of what you think it's useful. I need to see the *actual* log, because it contains things we log precisely because we might need them in troubleshooting, which means ZIPPING and ATTACHING the actual log to a post.
Some indication of the route you took would be useful as well. And if you are using extra/3rd party Navdata as well.
I did 2 flights with SU10 navdata option disabled and it worked without having to restart the couatl service. I did not include details before because it was every flight I did at different areas of the world. Now I did what you said and it is the SU10 navdata option that was my issue. I turned it back on now because with it disabled I am not seeing VDGS at Asobo airports when I have used a gsx config. I updated to a new GSX version and will try again, and post full details next time it does not work. Thanks for the help.
-
Uberto, I also have systematically this problem with several airports. I also verified that with SU10 Navdata disabled, it solved the problem, but I have re-enabled it after my tests, because I need it for addon I bought on Marketplace.
For now, I have added a "start couatl" icon in my taskbar on the bottom, so I can easily launch the engine just before the landing, when I do not forget to do it ! Otherwise, I am punished with the spinning Menu and must do it after landing ! :D
My question is: can we hope you will found a solution ?
For your information, like you, I suspect it is the airport data loading which should crash couatl engine. But what is interesting is that, when you reload couatl manually, after landing, the engine didn't crash again, but, for sure, the airport data should be corrupted or incorrect, because it do not fit with the reality. I have had several time gate position, mentioned as available by Couatl choose menu, which were, in fact, occupied by an AI aircraft (and I am sure it was not because this aircraft took the place in the meantime I went there, moreover I have all traffics disabled). Hope it might help to understand the problem. Cheers !
-
For now, I have added a "start couatl" icon in my taskbar on the bottom, so I can easily launch the engine just before the landing, when I do not forget to do it !
The FSDT installer placed an icon named "Start Couatl for GSX MSFS" on your Desktop precisely for that reason.
For your information, like you, I suspect it is the airport data loading which should crash couatl engine. But what is interesting is that, when you reload couatl manually, after landing, the engine didn't crash again, but, for sure, the airport data should be corrupted or incorrect, because it do not fit with the reality.
I don't think the problem is bad data about the arrival airport. The crash might have happened in flight, due to other bad data it got while in flight.
We haven't been able to reproduce that crash in flight, it would be helpful if you added some details about your configuration like:
- the airplane you are using
- if you enabled the SU10 Navdata API option in GSX
- all the other add-ons you are using, especially those that will use Simconnect to connect to the sim, like AI traffic injection, FSUIPC, etc.
- the route for that flight.
- if you are using alternative Navdata scenery, like Navigraph
-
For now, I have added a "start couatl" icon in my taskbar on the bottom, so I can easily launch the engine just before the landing, when I do not forget to do it !
The FSDT installer placed an icon named "Start Couatl for GSX MSFS" on your Desktop precisely for that reason.
For your information, like you, I suspect it is the airport data loading which should crash couatl engine. But what is interesting is that, when you reload couatl manually, after landing, the engine didn't crash again, but, for sure, the airport data should be corrupted or incorrect, because it do not fit with the reality.
I don't think the problem is bad data about the arrival airport. The crash might have happened in flight, due to other bad data it got while in flight.
We haven't been able to reproduce that crash in flight, it would be helpful if you added some details about your configuration like:
- the airplane you are using
- if you enabled the SU10 Navdata API option in GSX
- all the other add-ons you are using, especially those that will use Simconnect to connect to the sim, like AI traffic injection, FSUIPC, etc.
- the route for that flight.
- if you are using alternative Navdata scenery, like Navigraph
PMDG 737-700 and -800
SU10 navdata option enabled
FSRealistic Pro but it did this before I installed it I think. No FSUIPC or AI traffic
Yes to Navigraph navdata