Products Support > GSX Support MSFS
CTDs are not caused by GSX
GruenePizza:
Hello, I mean, even if the title of this forum said something different, Couatl is currently doing CTDs for me.
Is there some kind of log file that Couple generates?
NNunumete:
MSFS support just told me that Coatl does cause my CTD's.
virtuali:
--- Quote from: NNunumete on November 28, 2023, 12:21:15 pm ---MSFS support just told me that Coatl does cause my CTD's.
--- End quote ---
That kind of Microsoft support is very clearly some low-level guy that has no idea how Couatl or even Windows protected mode works, he's only trained to tell you to check the Event Viewer and he's doing the same assumption that "just" because you have an event there, it "must" be the cause.
I'm sure you also have a Flightsimulator.exe Event there so, under that reasoning, it "must" be the "cause", because it's there in the Event viewer.
But the difference is, while Flightsimulator.exe surely can (and does) crash on its own, Couatl64_MSFS.EXE, as an external .EXE, CANNOT crash the sim but, instead, can be affected by the simulator crashing on its own, because it will disconnect abruptly without sending a proper closing signal, so we can't always do the required memory clean up that native win64 apps must do on exit, so you also see the Couatl .exe in the Event viewer, but it was the victim of Flightsimulator.exe crashing, not the cause.
NNunumete:
Update:
MSFS support responded with:
“I believe what is occurring is you are just overloading your PC with additional software / mods, thus leading to the MSFS crash. We see this quite often with GSX Pro in particular.”
Doesn’t really help me further….
virtuali:
--- Quote from: NNunumete on November 28, 2023, 10:40:22 pm ---
MSFS support responded with:
“I believe what is occurring is you are just overloading your PC with additional software / mods, thus leading to the MSFS crash. We see this quite often with GSX Pro in particular.”
--- End quote ---
This reply just confirms what I guessed:
They really have no idea why MSFS crashed, so they provided a very generic reply saying the sim is just overloaded, and tied this to GSX Pro, not because they know it's the cause, just because the program is quite popular, so they are getting a number of reports which is purely based on the fact there are many using GSX and several might have been misled by the Event viewer that Couatl was the "cause" of the crash, when it fact was the victim. I agree to a casual inspection.
This might seem reasonable, so many users reporting crashes in general and providing MS support with an Event viewer, are the reasons triggering that reply from MS support.
Now, it is possible that, rather than GSX/Couatl crashing the sim, the Navdata API (which is part of the sim) might have crashed itself, just because GSX made a call to it. This has been acknowledged in the SU13 release notes:
https://forums.flightsimulator.com/t/release-notes-sim-update-13-1-34-16-0-available-now/610338
--- Quote ---Requesting some data using the NavData API shouldn’t freeze the sim anymore
--- End quote ---
This shows that it was likely, until SU13, that calling into the Navdata API could freeze/crash the sim, and of course GSX requires the Navdata to work so, it is possible that not ALL known issues with it have been fixed, and this might also depend on which Navdata is used. And these bugs in the Navdata API (which is part of the sim and only MS/Asobo can fix), might have been the very reasons why MS support has accumulated some kind of history about "GSX Pro crashes", when in fact they were bugs in the sim which weren't fixed until SU13, and we are not sure if there are still issues left, that is not all bugs in the Navdata API has been fixed.
To provide for this eventuality, we added a new option in the GSX Settings to Disable GSX in Cruise.
Normally, while in flight, GSX makes a call to the Navdata API when you open its menu in flight, to get a list of the nearby airports and allow you to pre-select a gate before landing. Enabling this option will stop any communication with the Navdata API unless you are below 10k feet and are flying 250kts or slower so, even if you open the GSX menu during in flight accidentally, with GSX disabled, it won't do anything.
Also, enabling that option might help you with troubleshooting: if you are still getting a crash in flight, and you were flying over 10k feet or faster than 250 kts, you can be 100% sure it wasn't GSX.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version