GSX Working At Departure Airport But Not Arrival Airport

[Toy_Turnip]

Hi all,

So loving GSX so far worked flawlessly my first flight on both departure airport and arrival airport.

Today I flew the same route but at the arrival airport the GSX in sim menu was stuck loading, then when taxiing I decided to check if it was working again but same thing. This time it said Could not find valid navdata at this position.

Seems to keep happening now even though it worked the first time.

Take care,
Daniel

[Ursli80]

Hello,

that's exactly what happened to me today from LOWW to LSZH. I'm normally a LSZH resident and therefore know that it always works there.

Best regards
Urs

[Toy_Turnip]

Its rather strange. I'm new to GSX so not sure if it was somthing iv done incorrectly or not, i'm only using GSX profiles from ini builds launcher so stright from the devs of the airports.

If I have any updates ill post them here

[downscc]

Same but different problem.  In MSFS2024SU2 GSX3.5.5 used for pushback at KSFO.  On arrival at FSDT KORD, I attempted to request Gate C-16 and couatl crashed.  Problem log indicated a UTF-8 error (no .py file for kord).  Restarted couatl and repeated same problem so I taxied to C-16 and parked myself without GSX marshaling.  After shutdown, I again tried GSX and it worked normally.  I later started a new MSFS session, loaded aircraft at KORD 28R and this time the gate request worked as expected.

[BIGLESA]

I installed GSX Pro and have attempted to update it, as well as run the "Check" option in the installer. However, every time I try to launch GSX Pro in MSFS, it seems to freeze and fails to load. When I use the "Restart Couatl" option, it throws an error (attached). Below is the log message:


problem raised by addon <no traceback available>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 8: unexpected end of data
{'User Pos': (38.94802550970878, -77.44837491762306, 93.5093 m, 4.72237 m, 5.582233570923274, 0.008958222866447818, -0.003490658476948738, -0.0002616515098898376, 4.611624034881592, 1.0), 'Airport': 'KIAD'}

[virtuali]

You all don't have the latest update installed. We haven't updated the version number, because we wanted to get some feedback first, so just run an update Check now.

[atsugi]

I did the update and still have this issue. I had to restart the application, and then it works. There is definitely something wrong.

[Ursli80]

Hello Virtuali,

I performed the update today around 9:00 a.m. (Swiss local time) and then this "problem" occurred.

Tomorrow, Friday, I will be back in the morning and then I will do the update as usual in this case.

Thanks for your info and help.

Besg regards
Urs

[BIGLESA]

Hi Virtuali,

I’d like to clarify that the assumption I didn’t apply the update is incorrect. I did update the product, but I’m encountering an issue that appears to be related to the add-on itself.

I was able to uninstall the program, and MSFS then ran without any errors. The log message is very specific, though I’m not sure how to interpret or resolve it. It states:

"Problem raised by addon <no traceback available>"

This clearly seems to be an issue with how the add-on is reading airport data, and it’s currently preventing the simulator from functioning properly.

I haven’t made any changes other than installing the latest update. I would appreciate your support in resolving this.

[Alexair]

Same issue on my side. Works fine on DEP airport and doesn't work at all on all DEST airports. That since the latest update.
On installer :
3.5.5 IS INSTALLED
3.5.5 IS LATEST
I even tried a check.
Something is broken since the update. Same message : Could not find valid navdata at this position

[virtuali]

I’d like to clarify that the assumption I didn’t apply the update is incorrect. I did update the product, but I’m encountering an issue that appears to be related to the add-on itself.

I don't do "incorrect" assumptions. Nowhere I said you didn't apply the update. I said you don't HAVE the update, which doesn't imply you didn't tried to update, it simply means what it means: you don't have it.

When you see a version listed, the ONLY thing you can be sure of, is the manifest.json file of the main package has been updated. It doesn't say ANYTHING if the whole update has been completely applied to each and every file. That what the CHECK function does.

However, even the CHECK function does is not 100% guaranteed you HAVE the latest files, because if you are located on a local node that hasn't got the latest files, you won't get them no matter what, until that node is finally replicated, which normally takes a few hours, or a few days in the worse cases.

If for any reason you don't seem to get the latest file from the normal installer or you have reasons to suspect your issue might be caused by not having the latest update (and you DO have to reasons to suspect that: I just told you), you can try the OFFLINE installer, in the Sticky thread of this forum. That will be unaffected by possible network replication delays.

[Alexair]

I tried with the manual installer, but same issue. Still the "no navdata" issue and GSX still not working on all destination airport...

[virtuali]

I tried with the manual installer, but same issue. Still the "no navdata" issue and GSX still not working on all destination airport...

And where is your log ? Without it, we cannot possibly say what is really happening. Thanks to an user who HAS posted a log, we found a completely different cause, which was a corrupted livery. That why logs are important.

[Ursli80]

Hello Virtuali,

I ran the updater today, as announced. Then two flights: LGSM to LCLK and LSZH to LOWW, but I couldn't do anything at the destination airport until I restarted the client.

I'm sorry I don't have better news.

I'll make sure to attach the log next time.

Best regards
Urs

[Alexair]

Here is the log from today's flight.
Still the same issue. Tried with 6-7 different aircraft and 7-8 different destination airport. All with the same result.

Running in mode: Microsoft Flight Simulator
SharedMemInterface connected
Python 3.7.9 Stackless 3.7 (tags/v3.7.9-slp-dirty:8ad319a856, May 22 2021, 22:48:12) [MSC v.1916 64 bit (AMD64)]
wxPython 4.2.0
Couatl v5.0 (build 5792)
log started on Fri Jun  6 17:32:18 2025