Products Support > GSX Support MSFS

Spinning Menu after landing

<< < (4/6) > >>

b742f:

--- Quote from: virtuali on November 27, 2022, 04:40:33 pm ---
--- Quote from: b742f on November 26, 2022, 04:34:26 am ---I have a new airport error also not an airport I landed or departed but in the Middle East region.
--- End quote ---

Which error ?

--- End quote ---

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.

virtuali:

--- Quote from: b742f on December 16, 2022, 05:59:53 am ---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.
--- End quote ---

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.

Copper:
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
...

virtuali:

--- Quote from: Cipher on December 16, 2022, 07:27:08 pm ---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.
--- End quote ---

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.

Copper:
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page