FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: mico on December 29, 2025, 11:36:47 am
-
MSFS will crash every time after update GSX 3.7.4. It almost crashed after landing,sometimes crash when entering departure airport. MSFS is normal after uninstall GSX.
My ram is 16G. I don't know if it's because of it. I've seen other message about memory overflow .
-
Hello folks. Just wondering if any AIG traffic users got CTD after the latest update? I have no issues when 3.7.3 but get crashes every time now when I load in an airport and AI starts to inject. Uninstall no matter AIG or GSX can solve the problem, as a result it looks GSX conflicts with AI. Any idea how this happened or which function can be turned off to have both working together? So frustrated because I’m not an online flyer so AI is the key point for my enhancement.
-
I have to do more testing but if I remember correctly it could have been that the CTDs only started with 3.7.4 when I started injecting traffic. But I dont use AIG, I use FSLT.
The only thing I know for sure is that after uninstalling GSX 3.7.4 I never had any CTDs anymore. And when using 3.7.3 and all my other addons I never had any CTDs at all.
-
Same here and confirmed for lots of other people as well. After upgrading 3.7.4 we're getting major CTD issues. Never had a CTD with MSFS before. Deactivation of GSX and it runs normal again.
-
Yeah there are reports on that all over the place.
Does anybody know why there is no feedback at all from the GSX developer? Maybe he is on a long new years holiday and of course, may he enjoy it.
-
I am having the same problem in MSFS 2020. Please FSDT can we have a way to revert to the previous version?
This is a general problem not restricted to a specific external AI injector.
INFO:
Final line in SimConnect log:
355.08698 [364, 4792]RequestDataOnSimObject:RequestID=684, DefineID=-1386682032, ObjectID=11218, Period=1, Flags=0, origin=0, interval=0, limit=0
-
I am having the same problem in MSFS 2020. Please FSDT can we have a way to revert to the previous version?
This is a general problem not restricted to a specific external AI injector.
INFO:
Final line in SimConnect log:
355.08698 [364, 4792]RequestDataOnSimObject:RequestID=684, DefineID=-1386682032, ObjectID=11218, Period=1, Flags=0, origin=0, interval=0, limit=0
Absolutely. Its definitely 3.7.4 and at least a roll back to 3.7.3 should be made possible by FSDT as soon as possible.
-
I have CTD as well standing at the Gate and waiting for PB.
As I am writing Logbook with all my changes I am doing I can say, that MSFS 1.39.9.0 was installed on my maschine at 31th of december as well.
No clue what causes the issue but before it was very stable.
I will test without GSX today and see what happens...
-
Same issue for when starting AIGTech or BATC, always CTD before AI Aircraft injection. After unsintalling GS, everything worked perfectly.
-
Same issue for when starting AIGTech or BATC, always CTD before AI Aircraft injection. After unsintalling GS, everything worked perfectly.
I cannot confirm this. Did a test on EDDS Gate 15 with AIG. After starting PB with GSX the Sim did NOT CTD.
Confirmed.
I have now also carried out several tests:
1) If I deactivate ‘couatl64_boot.exe’ in exe.xml, load the simulator, manually start ‘couatl64_boot.exe’ after standing at the gate, request the jetways in GSX and then start AIG, there appears to be NO CTD.
2) If I reactivate ‘couatl64_boot.exe’ in exe.xml and follow the same steps as in 1, the simulator crashes as soon as AIG tries to load aircraft into the simulator.
It would still need to be checked whether there is also a CTD in scenario 2 if I do not request any GSX services (jetways, etc.).
-
Same issue for when starting AIGTech or BATC, always CTD before AI Aircraft injection. After unsintalling GS, everything worked perfectly.
I cannot confirm this. Did a test on EDDS Gate 15 with AIG. After starting PB with GSX the Sim did NOT CTD.
Confirmed.
I have now also carried out several tests:
1) If I deactivate ‘couatl64_boot.exe’ in exe.xml, load the simulator, manually start ‘couatl64_boot.exe’ after standing at the gate, request the jetways in GSX and then start AIG, there appears to be NO CTD.
2) If I reactivate ‘couatl64_boot.exe’ in exe.xml and follow the same steps as in 1, the simulator crashes as soon as AIG tries to load aircraft into the simulator.
It would still need to be checked whether there is also a CTD in scenario 2 if I do not request any GSX services (jetways, etc.).
This workaround seems to be effective until or if FSDT address the issue in 3.7.4. I had CTD's with GSX pre-loaded by exe.xml even if I did not request any GSX services before starting AIGTC. Now I have disabled GSX auto startup in exe.xml. I started the sim, loaded into my departure airport EGLL and started AIGTC. After traffic had been injected I manually started GSX. So far no CTD's.
-
I also found that rather than manually starting GSX after loading into the departure airport I could instead start GSX as soon as the World Map loaded and the sim did not CTD when AI traffic was injected.
I have tried a reinstall of GSX but that did not fix the problem. v3.7.4 is definitely broken and needs to be fixed or reverting to 3.7.3 made possible.
-
Yes that's also the way I've already tested by swiching GSX off then turning it on. However, my situation is even worse. When I'm all set at the gate with AI even all injected, I will still get CDT right away after I trun GSX on. The only solution for me is turning off GSX during the whole flight until approach to my destination then activate GSX. What's more funny is even by doing that, after I landed some major airports with huge amount of AI, CTD still comes before I taxi to the gate. Anyway, at least now everybody can confirm that's 3.7.4 gets our sims ruined and we just don't know when we can get our stable edition back. For those who ask for rolling back to 3.7.3? Forget it, I've been using GSX for over 10 years and never seen those arrogant developers give you that chance.
Hi,
I don't know how you are manually starting GSX but if it is by executing "C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe" directly it will cause a CTD with AI traffic injection.
If that is the case then execute "C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_boot.exe" instead.
Hope that helps.
-
Yes that's also the way I've already tested by swiching GSX off then turning it on. However, my situation is even worse. When I'm all set at the gate with AI even all injected, I will still get CDT right away after I trun GSX on. The only solution for me is turning off GSX during the whole flight until approach to my destination then activate GSX. What's more funny is even by doing that, after I landed some major airports with huge amount of AI, CTD still comes before I taxi to the gate. Anyway, at least now everybody can confirm that's 3.7.4 gets our sims ruined and we just don't know when we can get our stable edition back. For those who ask for rolling back to 3.7.3? Forget it, I've been using GSX for over 10 years and never seen those arrogant developers give you that chance.
Hi,
I don't know how you are manually starting GSX but if it is by executing "C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe" directly it will cause a CTD with AI traffic injection.
If that is the case then execute "C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_boot.exe" instead.
Hope that helps.
Thank you for your direction. Today I also pointed my clues to that folder. I’ve noticed in coutal64 folder there’s one couatl64_boot.exe plus three different couatl64_xxx.exe to match three different P3D/MSFS versions of course. However, sim only uses coualt64_boot when we load in an airport. I’m now curious what will happen if I delete all three couatl64, or just keep one of them in case of GSX cannot identify the right version after update. I’ll test tomorrow.
-
I have found the most reliable option is to start Couatl64_boot.exe AFTER the initial injection of AI traffic has completed.
I do not think deleting those other exe's will help and could make things worse.
Good luck.
-
Hi,
I don't know how you are manually starting GSX but if it is by executing "C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe" directly it will cause a CTD with AI traffic injection.
If that is the case then execute "C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_boot.exe" instead.
Hope that helps.
I started this .exe as well. It may have been a coincidence that the Sim didn't crash after I started the .exe file.
-
Hi,
I don't know how you are manually starting GSX but if it is by executing "C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe" directly it will cause a CTD with AI traffic injection.
If that is the case then execute "C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_boot.exe" instead.
Hope that helps.
I started this .exe as well. It may have been a coincidence that the Sim didn't crash after I started the .exe file.
I found Couatl64_boot.exe more reliable and that is how GSX is normally started by the exe.xml file. It probably does something necessary.
-
Are you using a 3rd party AI traffic injector ?
-
After another whole morning test I can say no good news. It doesn't matter which exe you shut off and restart, CTD. Temporarily turn off all those exes and restart after AI injected, it just gives you a few more seconds before you see CTD. I'm tired of this time wasting and useless test and uninstall GSX already. 100% sure it's AI related after 3.7.4 and seems whenever GSX detects the AI it just crashes the whole thing. Now we can only wait it's fixed and fly without pushback (defualt pushback sucks!) LOL.
-
As I already asked in other threads, can you confirm this happens ONLY if you use a 3rd party AI Injector (no matter *when* its started) ?
We only tested GSX with default AI traffic generation and I cannot replicate any crashes so, if this is confirmed to be happening only with an AI Injector, it's the only first step towards a possible fix on our side, assuming a fix IS possible.
-
As I already asked in other threads, can you confirm this happens ONLY if you use a 3rd party AI Injector (no matter *when* its started) ?
We only tested GSX with default AI traffic generation and I cannot replicate any crashes so, if this is confirmed to be happening only with an AI Injector, it's the only first step towards a possible fix on our side, assuming a fix IS possible.
Yes this happens only when using 3rd party AI injector. Switch off no matter GSX or AI injectors can stop this CTD. Furthermore, if just using 3rd party models but no injectors, msfs2020 will still defaultly inject those models and causes CTD. With sim's own models, no issues.
-
Switch off no matter GSX or AI injectors can stop this CTD.
Do you mean you have tried multiple injectors ? Does it happen with any of them, or just a specific one ?
-
Switch off no matter GSX or AI injectors can stop this CTD.
Do you mean you have tried multiple injectors ? Does it happen with any of them, or just a specific one ?
Please read the previous comments. It has been reported for FSLTL and AIGTC.
-
Using FSHud together with GSX also results in CTDs.
-
Same here. I updated to 3.7.4 on May 1, 2026. After that, the crashes started as soon as I enable FS HUD or BATC, which inject AI traffic. If I exit Couatl, the crashes stop. Could we revert to 3.7.3? Unfortunately, I didn’t check the forums before updating. If I had, I wouldn’t have updated to 3.7.4, like some other people did.
-
Same here. I updated to 3.7.4 on May 1, 2026. After that, the crashes started as soon as I enable FS HUD or BATC, which inject AI traffic. If I exit Couatl, the crashes stop. Could we revert to 3.7.3? Unfortunately, I didn’t check the forums before updating. If I had, I wouldn’t have updated to 3.7.4, like some other people did.
I'm using MSFS2020 with BATC or FSHUD, with AI Injection. I also use FSTL and AIG models.
-
After that, the crashes started as soon as I enable FS HUD or BATC, which inject AI traffic.
So it's clear the crashes are caused by the injection, I have BATC but I never used the injection, so I guess I can test this easily.
-
Alright, let me just try to be more clear so it's easier to find out which part is broken. Basically FSLTL and AIG both have two parts work together to inject AI to sims, which are base model pack and the injector. Everyone knows this for sure. What someone might don't know is, different model pack can also be used by different injectors, which means FSLTL can inject AIG models or reverse as well. Technically even you don't have any injectors but only models installed, the sim will also inject them just like inject those default msfs made models. So base on above, we can get the following combinations:
1. AIG models with AIG TC - 100% CTD
2. AIG models with FSLTL injector - 100% CTD
3. AIG models with no injector but msfs injects - 100% CTD
4. FSLTL models with FSLTL injector - less CTD but not 0
5. FSLTL models with AIG TC - didn't test but should be the same as #4
6. FSLTL models with no injector - didn't test
7. Default models injection(No AI addon) - No CTD
-
Please read the previous comments. It has been reported for FSLTL and AIGTC.
And it's precisely because I read the previous comment that I have asked, because from that sentence alone, is not possible to understand if:
- if it happens with a specific injector only
- if it happens with JUST those TWO
- if it happens with ANY AI injector
- if doesn't happen with ONE (or more) AI injector
All possible valid outcomes that couldn't be surely verified by the simple "It has been reported for FSLTL and AIGTC" sentence which, as such, only indicates it happens with those two.
-
So base on above, we can get the following combinations
You listed 7 combinations, with only one (default AI models with no injection causing zero CTD, assuming this is WITH GSX enabled...). Have you tried ALL of those 7 with AND without GSX ?
Also, it doesn't seem you ever tried a combination with some AI Injector but using default MSFS models. I'm trying to understand if the problem if the injection process itself, or the models, or both.
-
just to add for me I use PSXT for traffic injection with AIG models and get the CTD with 3.74 MSFS2020
-
Hey!
So I use MSFS 2020, PSXT with AIG/FSTL Models, and receiving the CTD. I also had the CTD when on VATSIM, using the same models.
Today I unlinked GSX from the sim, and used PSXT with no issues.
I know there's a thread stating "CTDs are not caused by GSX" but unfortunately, it appears they may be. Plenty of users removing GSX from the equation and all is working as expected. :/
-
I know there's a thread stating "CTDs are not caused by GSX" but unfortunately, it appears they may be. Plenty of users removing GSX from the equation and all is working as expected.
Of course CTD are NOT caused by GSX, that has been explained so many times. It seems that multiple users confirmed the crashes happens ONLY with an AI injector, not with GSX alone so, if anything, CTD might be "caused" by using both, if "caused" is the right term.
Because the real issue might just be the dreaded max simobject limit that, by using BOTH (add GSX objects + injected AIs), is exceeded, so what is *really* causing the CTD is exceeding that limit.
In any case, I just tried now with FSLTL, using two different injectors, first the one from FSLTL, and then with BATC. Made 5-6 Boarding at KLAX, no issues whatsoever. Installed FSLTL fresh, using all default options. In BATC, I have the AI density set to the suggested value of 5 so, again, all default.
-
Yes I did all combinations with or without GSX. Those are the result with GSX on. Without GSX everything works fine and smothly. For your second question I assume nobody will use a professional injector to inject a default model so I can't give you the answer. Base on the information we've got now, I would believe it's models problem. I remember for your new update you brought out a funtion for taxi which can creat route to avoid AI, I don't know if these have any relationship.
-
I would believe it's models problem. I remember for your new update you brought out a funtion for taxi which can creat route to avoid AI, I don't know if these have any relationship.
If they had it, I'm sure you would have noticed a crash only happened when calling the progressive taxi function, but nobody reported it this way. GSX won't read any AI unless:
- you open the 2d map AND enable the AI traffic layer
OR
- you start the progressive taxi function.
OR
- you select a gate, so it would offer the option to remove an AI on that gate.
Since I see several reports saying it happened while Boarding, it seems to indicate it's "just" a matter of too many *injected* objects, since both GSX and any AI generator injects Simobjects.
As I've said, I tested it with both FSLTL and BATC injectors, doing (many) Boarding in GSX, on a very large airport (KLAX), and I couldn't replicate any crashes. As I've said, I used all defaults for both FSLTL and BATC, and I turned off MSFS own AI traffic and also the parked airplanes, so the ONLY AI present were the injected ones.
What has changed in 3.7.4 is this:
GSX Pro Change: LOD Levels has been changed for ALL vehicles, to take advantage of the different LOD curve introduced with MSFS 2024 SU4, improving object detail in the short/mid distances.
This because we heard so many times users complaining our previous LOD levels were far too restrictive, so we took advantage of the new SU4 LOD curve, which shows better LOD for a longer time in a non-linear fashion, to improve visual pop-up quite a bit. Maybe this new less restrictive LOD is "just" too much for the sim to handle ? Nothing is free is this world: if you hate pop-up like everybody, you must accept the improved LOD would surely take more memory.
Maybe opening the default fps counter and checking your RAM/VRAM situation might be helpful.
-
Interesting, sacrifice msfs2020 users's simobjects limitation to accomadate a new introduced msfs2024 function, and for those small RAM users even they don't deserve to fly anymore, can I understand like that? Do you really think everybody can afford 64/128GB RAM (mine is 32GB)? Totally speechless. Give us a chance to roll back to 3.7.3, I'd rather to keep it forever until I update to msfs24 to enjoy your brilliant new function.
-
We did not have these problems at all before 3.7.4 so whatever changed in that version is the issue here.
I have 64GB of ram and 24GB VRAM.
-
[...]
GSX Pro Change: LOD Levels has been changed for ALL vehicles, to take advantage of the different LOD curve introduced with MSFS 2024 SU4, improving object detail in the short/mid distances.
This because we heard so many times users complaining our previous LOD levels were far too restrictive, so we took advantage of the new SU4 LOD curve, which shows better LOD for a longer time in a non-linear fashion, to improve visual pop-up quite a bit. Maybe this new less restrictive LOD is "just" too much for the sim to handle ? Nothing is free is this world: if you hate pop-up like everybody, you must accept the improved LOD would surely take more memory.
Maybe opening the default fps counter and checking your RAM/VRAM situation might be helpful.
Thanks Umberto for investigation. I think it's not worth discussing who is crashing what. The problem is, we cannot use the combination of GSX and AI models (even with VATSIM) any more.
Which logs or data do you want us to collect?
-
I have to do more testing but if I remember correctly it could have been that the CTDs only started with 3.7.4 when I started injecting traffic. But I dont use AIG, I use FSLT.
The only thing I know for sure is that after uninstalling GSX 3.7.4 I never had any CTDs anymore. And when using 3.7.3 and all my other addons I never had any CTDs at all.
The problem does not seem to be restricted to one specific injector or AI traffic data source for injection. For example this user appears to be using FSLTL for injection of default FSLTL models only. (Not using AIG data).
I inject traffic with AIG Traffic Controller (AIGTC) which only injects AIG model data.
FSLTL can inject FSLTL and or GSX models
Beyond ATC (BATC) can inject FSLTL and GSX models.
FSHud can be used with various sources, including:
FSLTL
FS Traffic
AIG Traffic
External Traffic: FSHud can also handle traffic injected directly into FSHud through the FSHud REST API.
-
Interesting, sacrifice msfs2020 users's simobjects limitation to accomadate a new introduced msfs2024 function, and for those small RAM users even they don't deserve to fly anymore, can I understand like that?
First, this was just a THEORY, which I came out since I cannot reproduce a crash with two different AI injectors, so I tried to assume it MIGHT have been due to just "too much stuff" being pushed, to increase the visual quality.
And no, you are entirely wrong saying we "sacrificed" MSFS 2020 users: LOD it's LOD, the difference it's just what the sim considers a "proper" lod with its diagnostic tool. Our previous LOD levels were reported to be correct by the MSFS diagnostic tools (and users *hated* us for stick to them, now you want to go back...) and MSFS 2024 diagnostic tools UP TO SU4. After SU4, the response to the LODs has changed, so the diagnostic tool in 2024 is still reporting the improved LOD as correct, that's it, but you would see some improvement in 2020 as well, although now the 2020 diagnostic tool would probably report the LOD levels to be out of specs, which shouldn't be a problem, since that's the case for almost every other add-on out there (except GSX): users hate visual pop-ups, so other developers simply don't care about respecting the suggested LOD (as we did), so we were wrongly accused to have bad LODs JUST because we were the only ones fully respecting the direction of the sim own diagnostic tools.
Now, I really not sure anymore if this is the case, as you can see from other posts saying they are getting the crash which I cannot reproduce, with the same memory configuration I have ( 64 GB RAM, 24GB VRAM), so it might not be memory exhaustion after all, but I had to consider this, since it was the only thing that really changed from 3.7.3 to 3.7.4, since interaction with AI (in the Map, which is something new) was already there in 3.7.2.
-
Thanks Umberto for investigation. I think it's not worth discussing who is crashing what.
Of course it's worth, that's the first step towards understanding a possible fix, assuming a fix it's even possible, or at least some workaround. Don't misunderstand me: I'm NOT saying this to "put blame on somebody", when there's a CTD, it's ALWAYS something in the sim, since NONE of these add-ons can directly crash the sim, since they are all (GSX and various AI Injectors) external .EXE that can only make Simconnect calls to the simulator, they don't have ANY access to the sim process.
So, it's clearly an indirect effect: some addon makes what is a perfectly legit Simconnect call to inject some object, and it must triggering something in the sim that makes it crash, we cannot directly "fix" this, we can only try to understand WHAT is causing this ( too many objects, too large objects, too many simconnect calls, etc. ) and workaround it.
The problem is, we cannot use the combination of GSX and AI models (even with VATSIM) any more.
I fully understand the problem you are having, which I still cannot replicate. Note that, I must say I tried using the default A320 from iniBuilds, because I always proceed this way: if a report says there's a crash with FSLTL injection + GSX, I first try to isolate that, and proceed by adding further stuff AFTER because if I just test something with "everything in", it would be almost impossible to understand the real cause, which might as well be a combination with even more factors, like the *combined* effect of AI Injection+GSX injection+Airplane own Simconnect calls, and of course the baseline increased memory usage of a detailed 3rd party airplane.
So yes, of course I'll try to do the same with several add-on aircraft, trying to replicate the crashes which I'm still unable to, with GSX+FSLTL+BATC+default A320.
Which logs or data do you want us to collect?
I already indicated something that might have been useful in my previous post:
Maybe opening the default fps counter and checking your RAM/VRAM situation might be helpful.
-
I have 64GB of ram and 24GB VRAM.
I have a multi-display setup, several hardware and software controllers, hundreds of addons, and my settings mostly on ultra. All of which my system can handle with good performance.
Currently I am loaded into the sim using AI traffic and a DELAYED manual start of GSX (after traffic injection) and my system is using 51GB RAM 14.4GB VRAM and averaging around 40% CPU usage.
I did not see any significant increase in VRAM usage when I manually started GSX.
During the initial AI traffic injection process there was no significant change observed in CPU, GPU, RAM or VRAM usage.
I conclude that system performance is not an issue in my case.
So my system is capable of all that but since 3.7.4 if GSX is in the startup sequence in exe.xml it will instantly cause MSFS to CTD as soon as AI traffic injection starts.
-
I have 64GB of ram and 24GB VRAM.
Same here, i9 10900, RTX 3090.
Currently I am loaded into the sim using AI traffic and a DELAYED manual start of GSX (after traffic injection) and my system is using 51GB RAM 14.4GB VRAM and averaging around 40% CPU usage.
VRAM usage mostly checks out ( I have 13 GB taken at default KLAX with the default iniBuilds A320 V2 ), but RAM usage in your case seems to be very different, although it would have been useful if you posted a screenshot of the dev mode fps counter, so I can be sure we are looking at the same thing.
if GSX is in the startup sequence in exe.xml it will instantly cause MSFS to CTD as soon as AI traffic injection starts.
Of course I'm using GSX in default mode ( starting with EXE.XML ), and I still can't replicate a crash. See a video I just made, now with the Fenix A320, at default EDDF, using FSLTL models and Injectors, my settings are Ultra preset EXCEPT for all default AI traffic disabled, so the only AI generated are coming from the Injector.
https://youtu.be/ll3EH7cCDck (https://youtu.be/ll3EH7cCDck)
Now, please let me clarify this: I'm not trying to "deny" some users are affected, the whole point of the video is to show:
- The problem is not easy to reproduce as it seems
- I'm working at it, doing tests.
Now, for full disclosure, I'm running a slightly updated version of GSX, that contains some fixes for some likely (but maybe not) unrelated problems with .NET. They should be unrelated, since they would happened with 3.7.3 as well, but in case they are, I suggest trying the Beta updater I posted here and see if it makes any difference:
https://www.fsdreamteam.com/forum/index.php/topic,33890.msg213168.html#msg213168
-
Yes my RAM usage is high at the moment simply because I happen to be running a load of other things at the same time as the sim at the moment, including multiple MSEdge open tabs. Although it is better not to do that for performance reasons my system handles it and that is not typical usage when I am using the sim.
So even with nothing other than what is required for running MSFS I still get the GSX problem, so it makes no difference in my case.
By the way, it is normal and recommended practice to disable MSFS default traffic when using third party injected traffic.
-
So even with nothing other than what is required for running MSFS I still get the GSX problem, so it makes no difference in my case.
Have you tried the updated version I posted ?
-
I will get back to you on this later.
Right now I have to take my wife to hospital for her cancer and post-operative knee replacement surgery treatment. So, priorities...
-
I will try the new Version later on.
You are using MSFS2024 right? This problem might be related to 2020 only - I suppose.
-
You are using MSFS2024 right? This problem might be related to 2020 only - I suppose.
Yes, of course I'm trying with MSFS 2024 first, because switching sim it's another variable I need to introduce progressively. I'll test with 2020, of course.
-
After installing the beta updater, MSFS 2020 no longer CTDs. I tried twice to reproduce the issue, but everything continues to work.
Only tried with FSHud
-
After installing the beta updater, MSFS 2020 no longer CTDs. I tried twice to reproduce the issue, but everything continues to work.
That's encouraging, we updated to the latest QLM libraries and fixed a couple of .NET issue that in theory should only have affected the couatl engine itself (possible crashing in flight or when closing the sim, but not causing the sim to crash), at least that was what was reported by users in the other thread about the clr.dll crashes.
And yes, I tested MSFS 2020 now under a similar situation ( Fenix at default EDDF with FSLTL injection ), no issues as well:
https://youtu.be/c3-KqUVEOgQ (https://youtu.be/c3-KqUVEOgQ)
-
I tested the updated version (from BOX) and CTD again after starting AIG Traffic injection.
1) Start MSFS 2020
2) Load at Gate 15 in EPWA
3) Not requesting GSX services
4) Start AIG Traffic Injection > CTD
Event log:
Application: AIGTech - Traffic Controller.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32, IntPtr)
at Microsoft.FlightSimulator.SimConnect.SimConnect.AICreateParkedATCAircraft(System.String, System.String, System.String, System.Enum)
at AIGTech.Connector.Interface.MSFS.SimConnect_MSFS+<>c__DisplayClass55_0.<AICreateParkedATCAircraft>b__0()
Exception Info: System.Reflection.TargetInvocationException
at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at AIGTech.TrafficController.App.Main()
And second:
Fehlerhafter Anwendungsname: AIGTech - Traffic Controller.exe, Version: 0.9.4.3, Zeitstempel: 0xf7b36fbc
Fehlerhafter Modulname: KERNELBASE.dll, Version: 10.0.26100.7462, Zeitstempel: 0xe9f9d656
Ausnahmecode: 0xe0434352
Fehleroffset: 0x00000000000c782a
Fehlerhafte Prozess-ID: 0x2F24
Fehlerhafte Anwendungsstartzeit: 0x1DC80999A3F1C03
Fehlerhafter Anwendungspfad: M:\Tools\AIG_TrafficController\AIGTech - Traffic Controller.exe
Fehlerhafter Modulpfad: C:\WINDOWS\System32\KERNELBASE.dll
Berichts-ID: f3c7a2af-adc6-4d08-8f38-d5d1463d0cc1
Vollständiger Name des fehlerhaften Pakets:
Fehlerhafte paketbezogene Anwendungs-ID:
-
I tested the updated version (from BOX) and CTD again after starting AIG Traffic injection.
Considering the last post from Mark823 (using FSHud) reporting no CTDs with the Beta update, in addition to my further testing with MSFS 2020 (using FSLTL), that would suggest that not all AI injections are the same. Or maybe not all AI models sets are the same.
The issue seems very complex because we are getting conflicting reports:
- The main thing that changed from 3.7.3 to 3.7.4 was the increase in LOD quality, to reduce visual pop-ups. This clearly must have some cost, even if I wouldn't expect a crash, unless you are really short on memory, which wasn't the case according to other user that seems to have plenty of RAM/VRAM available.
- But if it was a problem of changed objects LODs, it couldn't possibly be fixed with an updated couatl engine, as Mark823 reported, and 3.7.3 also had the same couatl engine as 3.7.4, yet users are saying the issue started with 3.7.4.
That is without saying I'm still unable to replicate ANY CTD, with any simulator, so I can only rely on users reports.
-
I did FPS monitoring tests. Please find the results
-
This log is quite telling:
Application: AIGTech - Traffic Controller.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32, IntPtr)
at Microsoft.FlightSimulator.SimConnect.SimConnect.AICreateParkedATCAircraft(System.String, System.String, System.String, System.Enum)
at AIGTech.Connector.Interface.MSFS.SimConnect_MSFS+<>c__DisplayClass55_0.<AICreateParkedATCAircraft>b__0()
The AIG traffic controller app crashed when it tried to create an AI airplane. Maybe it hit the in-famous max Simobjects limit, which is known to not only break Simconnect, but CAN cause the sim to crash.
However, the NUMBER of Simobjects created by GSX is absolutely unchanged in version 3.7.4 compared to 3.7.3 and nothing changed in the way they are created or when.
The only change in 3.7.4 was the LOD levels but again, it this was the real cause, it couldn't possibly be fixed with an updated GSX, as reported by Mark823, who said his crashes stopped with the Beta update and of course both my latest tests for which I posted videos were made with it as well.
In addition to that, if the LOD levels were a problem, it should be visible as a significant increase in RAM/VRAM allocation when GSX is started (because we are creating objects that are likely taking more memory than before, since their better LOD levels enter in view a bit earlier now), which according to your report, doesn't seem to happen.
-
I did FPS monitoring tests. Please find the results
Please explain where and when the CTD happened: after some time ? Doing something ?
-
I did FPS monitoring tests. Please find the results
Please explain where and when the CTD happened: after some time ? Doing something ?
Immediatly after AIG is injecting aircrafts.
-
I tested in FAOR and moved to EPWA with Teleport. After pressing "Select airport" in Teleport GSX crashed with report:
[00:00:00.031] Running in mode: Microsoft Flight Simulator
[00:00:00.047] 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)]
[00:00:00.047] wxPython 4.2.0
[00:00:00.063] Couatl v5.0 (build 6226)
[00:00:00.063] log started on Thu Jan 8 13:51:35 2026
[00:00:00.063]
[00:00:00.063] connecting to SimConnect...
[00:01:01.391] connected to SimConnect after 13 attempts
[00:01:01.516] connected to bglmanx
[00:01:01.516] RunningMode::pathToInstalledPackages M:\XboxGames\Microsoft Flight Simulator
[00:01:01.516] Loading addons
[00:01:01.516] Loading addon common
[00:01:01.656] Addon common loaded
[00:01:01.656] Loading addon LiveUpdate
[00:01:01.656] Addon LiveUpdate loaded
[00:01:01.656] requesting AddOn list to bglmanx
[00:01:10.406] Simulator version: 11.0.282174.999
[00:01:12.188] bglmanx list contains 33 AddOn(s)
[00:01:12.188] Loading addon LFSB
[00:01:12.360] Addon LFSB loaded
[00:01:12.360] Loading addon GSX
[00:01:12.422] Current sim directory is M:/Tools/Addon Manager/couatl64
[00:01:13.156] Addon GSX loaded
[00:01:13.156] Loading addon GSX.airports.kiah_fsdt_MSFS
[00:01:13.172] Addon GSX.airports.kiah_fsdt_MSFS loaded
[00:01:13.172] Loading addon KIAH2
[00:01:13.172] Addon KIAH2 loaded
[00:01:13.172] Loading addon GSX.airports.kord_v2_fsdt_MSFS
[00:01:13.188] Addon GSX.airports.kord_v2_fsdt_MSFS loaded
[00:01:13.188] Loading addon GSX.airports.ksdf_fsdt_MSFS
[00:01:13.188] Addon GSX.airports.ksdf_fsdt_MSFS loaded
[00:01:13.188] Loading addon GSX.airports.lszh_fsdt_MSFS
[00:01:13.188] Addon GSX.airports.lszh_fsdt_MSFS loaded
[00:01:13.188] Loading addon GSX.airports.cyvr_fsdt_MSFS
[00:01:13.203] Addon GSX.airports.cyvr_fsdt_MSFS loaded
[00:01:13.203] Loading addon GSX.airports.keyw_fsdt_MSFS
[00:01:13.203] Addon GSX.airports.keyw_fsdt_MSFS loaded
[00:01:13.203] Loading addon GSX.airports.kclt_fsdt_MSFS
[00:01:13.203] Addon GSX.airports.kclt_fsdt_MSFS loaded
[00:01:13.203] Loading addon GSX.airports.lfeq_fsdt_MSFS
[00:01:13.219] Addon GSX.airports.lfeq_fsdt_MSFS loaded
[00:01:13.219] Starting system monitors
[00:01:13.219] [KIAH2] is active
[00:01:51.438] Main Menu loaded
[00:01:51.985] Slew mode False
[00:01:55.828] Common onAppStart
[00:01:55.828] createDefaultContainer
[00:01:55.828] Current locale is German_Germany.1252
[00:01:55.828] Initializing audio...
[00:01:55.828] Available devices:
[00:01:55.828] OpenAL Soft on Lautsprecher (Realtek USB Audio)
[00:01:55.828] OpenAL Soft on Cabin Speaker (2- USB Audio Device)
[00:01:55.828] OpenAL Soft on GSX Speaker (3- USB Audio Device)
[00:01:55.828] OpenAL Soft on ATC Ausgang (VB-Audio Cable B)
[00:01:55.828] OpenAL Soft on MIP Speaker (Sound Blaster Play! 2)
[00:01:55.828] OpenAL Soft on CP Headset (3- Sound Blaster Play! 2)
[00:01:55.828] OpenAL Soft on Realtek Digital Output (Realtek USB Audio)
[00:01:55.828] OpenAL Soft on ATC Eingang (VB-Audio Cable A)
[00:01:55.828] OpenAL Soft on FO Headset (2- Sound Blaster Play! 2)
[00:01:55.844] Created OpenAL device: OpenAL Soft on ATC Ausgang (VB-Audio Cable B)
[00:01:55.844]
[00:01:55.860] Device info:
[00:01:55.860] Major version: 1
[00:01:55.860] Minor version: 1
[00:01:55.860] Frequency: 48000
[00:01:55.860] Refresh: 50
[00:01:55.860] Sync: 0
[00:01:55.860] Mono sources: 255
[00:01:55.860] Stereo sources: 1
[00:01:55.860] Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFT_device_clock ALC_SOFT_HRTF ALC_SOFT_loopback ALC_SOFT_loopback_bformat ALC_SOFT_output_limiter ALC_SOFT_output_mode ALC_SOFT_pause_device ALC_SOFT_reopen_device
[00:01:55.860]
[00:01:55.860] Context info:
[00:01:55.860] Vendor: OpenAL Community
[00:01:55.860] Version: 1.1 ALSOFT 1.23.1
[00:01:55.860] Renderer: OpenAL Soft
[00:01:55.860] Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX-RAM AL_EXT_ALAW AL_EXT_BFORMAT AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_BFORMAT AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_EXT_SOURCE_RADIUS AL_EXT_STATIC_BUFFER AL_EXT_STEREO_ANGLES AL_LOKI_quadriphonic AL_SOFT_bformat_ex AL_SOFTX_bformat_hoa AL_SOFT_block_alignment AL_SOFT_buffer_length_query AL_SOFT_callback_buffer AL_SOFTX_convolution_reverb AL_SOFT_deferred_updates AL_SOFT_direct_channels AL_SOFT_direct_channels_remix AL_SOFT_effect_target AL_SOFT_events AL_SOFT_gain_clamp_ex AL_SOFTX_hold_on_disconnect AL_SOFT_loop_points AL_SOFTX_map_buffer AL_SOFT_MSADPCM AL_SOFT_source_latency AL_SOFT_source_length AL_SOFT_source_resampler AL_SOFT_source_spatialize AL_SOFT_source_start_delay AL_SOFT_UHJ AL_SOFT_UHJ_ex
[00:01:55.860]
[00:01:55.860] Using EFX 1.0 extension, with 4 auxiliary send(s)
[00:01:55.860] Using EAX reverb
[00:01:55.860] Created OpenAL device: OpenAL Soft on Cabin Speaker (2- USB Audio Device)
[00:01:55.860]
[00:01:55.875] Device info:
[00:01:55.875] Major version: 1
[00:01:55.875] Minor version: 1
[00:01:55.875] Frequency: 48000
[00:01:55.875] Refresh: 50
[00:01:55.875] Sync: 0
[00:01:55.875] Mono sources: 255
[00:01:55.875] Stereo sources: 1
[00:01:55.875] Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFT_device_clock ALC_SOFT_HRTF ALC_SOFT_loopback ALC_SOFT_loopback_bformat ALC_SOFT_output_limiter ALC_SOFT_output_mode ALC_SOFT_pause_device ALC_SOFT_reopen_device
[00:01:55.875]
[00:01:55.875] Context info:
[00:01:55.875] Vendor: OpenAL Community
[00:01:55.875] Version: 1.1 ALSOFT 1.23.1
[00:01:55.875] Renderer: OpenAL Soft
[00:01:55.875] Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX-RAM AL_EXT_ALAW AL_EXT_BFORMAT AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_BFORMAT AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_EXT_SOURCE_RADIUS AL_EXT_STATIC_BUFFER AL_EXT_STEREO_ANGLES AL_LOKI_quadriphonic AL_SOFT_bformat_ex AL_SOFTX_bformat_hoa AL_SOFT_block_alignment AL_SOFT_buffer_length_query AL_SOFT_callback_buffer AL_SOFTX_convolution_reverb AL_SOFT_deferred_updates AL_SOFT_direct_channels AL_SOFT_direct_channels_remix AL_SOFT_effect_target AL_SOFT_events AL_SOFT_gain_clamp_ex AL_SOFTX_hold_on_disconnect AL_SOFT_loop_points AL_SOFTX_map_buffer AL_SOFT_MSADPCM AL_SOFT_source_latency AL_SOFT_source_length AL_SOFT_source_resampler AL_SOFT_source_spatialize AL_SOFT_source_start_delay AL_SOFT_UHJ AL_SOFT_UHJ_ex
[00:01:55.875]
[00:01:55.875] Using EFX 1.0 extension, with 4 auxiliary send(s)
[00:01:55.875] Using EAX reverb
[00:01:55.875] Created OpenAL device: OpenAL Soft on Lautsprecher (Realtek USB Audio)
[00:01:55.875]
[00:01:55.906] Device info:
[00:01:55.906] Major version: 1
[00:01:55.906] Minor version: 1
[00:01:55.906] Frequency: 48000
[00:01:55.906] Refresh: 50
[00:01:55.906] Sync: 0
[00:01:55.906] Mono sources: 255
[00:01:55.906] Stereo sources: 1
[00:01:55.906] Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFT_device_clock ALC_SOFT_HRTF ALC_SOFT_loopback ALC_SOFT_loopback_bformat ALC_SOFT_output_limiter ALC_SOFT_output_mode ALC_SOFT_pause_device ALC_SOFT_reopen_device
[00:01:55.906]
[00:01:55.906] Context info:
[00:01:55.906] Vendor: OpenAL Community
[00:01:55.906] Version: 1.1 ALSOFT 1.23.1
[00:01:55.906] Renderer: OpenAL Soft
[00:01:55.906] Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX-RAM AL_EXT_ALAW AL_EXT_BFORMAT AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_BFORMAT AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_EXT_SOURCE_RADIUS AL_EXT_STATIC_BUFFER AL_EXT_STEREO_ANGLES AL_LOKI_quadriphonic AL_SOFT_bformat_ex AL_SOFTX_bformat_hoa AL_SOFT_block_alignment AL_SOFT_buffer_length_query AL_SOFT_callback_buffer AL_SOFTX_convolution_reverb AL_SOFT_deferred_updates AL_SOFT_direct_channels AL_SOFT_direct_channels_remix AL_SOFT_effect_target AL_SOFT_events AL_SOFT_gain_clamp_ex AL_SOFTX_hold_on_disconnect AL_SOFT_loop_points AL_SOFTX_map_buffer AL_SOFT_MSADPCM AL_SOFT_source_latency AL_SOFT_source_length AL_SOFT_source_resampler AL_SOFT_source_spatialize AL_SOFT_source_start_delay AL_SOFT_UHJ AL_SOFT_UHJ_ex
[00:01:55.906]
[00:01:55.906] Using EFX 1.0 extension, with 4 auxiliary send(s)
[00:01:55.906] Using EAX reverb
[00:01:55.906] resetVars() with Simconnect
[00:01:55.906] GSX is starting
[00:01:55.906] [GSX] Simulator version is 11.0.282174.999
[00:01:55.906] isPBRAvailable returned False
[00:01:55.906] isRTTAvailable returned False
[00:01:55.906] GetSimObjectsFolder() returned M:\Tools\Addon Manager/MSFS/fsdreamteam-gsx-pro/SimObjects
[00:01:55.906] GetAdditionalSimObjectsFolder() returned M:\Tools\Addon Manager/MSFS/fsdreamteam-gsx-world-of-jetways/SimObjects
[00:01:55.906] GetAdditionalSimObjectsFolderV5() returned
[00:01:55.906] gateDistanceThreshold = 25 m
[00:01:55.906] [KIAH2] started
[00:01:56.172] Initial camera state: 15.0
[00:01:56.672] GSX started
[00:01:56.922] Start searching for add-on Packages
[00:01:57.094] Packages that contain manifest.json with gsx-pro in dependencies:
[00:01:57.094] Creating model cache...
[00:01:59.563] GSX SimStart
[00:01:59.563] GSX SimStop
[00:01:59.563] GSX SimStart
[00:01:59.688] FacilitiesCache.refreshSubscribe()
[00:02:06.688] File 'M:\Tools\Addon Manager/MSFS/fsdreamteam-gsx-pro/SimObjects\GroundVehicles\FSDT_Passengers_Seated\sim.cfg' ignored, can't read max_speed_mph
[00:02:11.375] File 'M:\Tools\Addon Manager/MSFS/fsdreamteam-gsx-pro/SimObjects\Landmarks\FSDT_WorldOfJetways\sim.cfg' ignored, can't read max_speed_mph
[00:02:16.141] File 'M:\Tools\Addon Manager/MSFS/fsdreamteam-gsx-world-of-jetways/SimObjects\Landmarks\FSDT_WorldOfJetways\sim.cfg' ignored, can't read max_speed_mph
[00:02:16.922] Model cache created
[00:02:17.563] Preload operators thumbnails...
[00:02:18.719] Preload operators thumbnails DONE
[00:02:43.078] GSX SimStop
[00:02:44.063] GSX SimStart
[00:02:45.016] GSX SimStop
[00:02:45.110] resetVars() with Simconnect
[00:02:47.110] USER airplane title reported by Simconnect is FMGS A320 Condor D-AICP
[00:02:47.110] Loading aircraft.cfg from m:\xboxgames\microsoft flight simulator\community\fmgs-a320-neo\simobjects\airplanes\fmgs_a320_neo
[00:02:47.110] Loading engines.cfg from m:\xboxgames\microsoft flight simulator\community\fmgs-a320-neo\simobjects\airplanes\fmgs_a320_neo
[00:02:47.110] Loading flight_model.cfg from m:\xboxgames\microsoft flight simulator\community\fmgs-a320-neo\simobjects\airplanes\fmgs_a320_neo
[00:02:47.110] Loading gameplay.cfg from m:\xboxgames\microsoft flight simulator\community\fmgs-a320-neo\simobjects\airplanes\fmgs_a320_neo
[00:02:47.110] Loading systems.cfg from m:\xboxgames\microsoft flight simulator\community\fmgs-a320-neo\simobjects\airplanes\fmgs_a320_neo
[00:02:47.235] this airplane has 10 exits
[00:02:47.235] Model: "A20N" (length: 4)
[00:02:47.235] Title: "FMGS A320 Condor D-AICP" (length: 23)
[00:02:47.235] Airplane major/minor version 320/0
[00:02:47.235] GSX SimStart
[00:02:47.235] ATC_ID_SIM read from Simconnect is D-AICP
[00:02:47.235] Searching airplane
[00:02:47.235] Searching airplane FMGS_A320_NEO
[00:02:47.235] Searching airplane FMGS_A320_NEO/320
[00:02:47.235] Searching airplane FMGS_A320_NEO/320/0
[00:02:47.235] Using aircraft data from SimConnect
[00:02:47.235] Auto Modular Merge is False
[00:02:47.235] fmgs a320
[00:02:47.235] Airplane Title = fmgs a320 condor d-aicp
[00:02:47.235] icao_airline not found in aircraft.cfg, we'll use the airline code from Simbrief, if available.
[00:02:47.235] Airframe-specific GSX-D-AICP.CFG not found in m:\xboxgames\microsoft flight simulator\community\fmgs-a320-neo\simobjects\airplanes\fmgs_a320_neo
[00:02:47.235] Airframe-specific GSX-D-AICP.CFG not found in C:\Users\peter\AppData\Roaming\Virtuali/Airplanes\fmgs_a320_neo
[00:02:47.235] Found gsx.cfg file at C:\Users\peter\AppData\Roaming\Virtuali/Airplanes\fmgs_a320_neo\gsx.cfg
[00:02:47.235] icaoType A20N overriding icao_type_designator A20N from aircraft.cfg
[00:02:47.235] Aircraft group is ARC-C
[00:02:47.313] Aircraft Ceiling is 2.2 m
[00:02:47.328] AIManager: Starting AI tracking...
[00:02:47.328] AIManager: Subscribed to ObjectAdded
[00:02:47.328] AIManager: Subscribed to ObjectRemoved
[00:02:47.328] AIManager: Subscribed to 6Hz frame event
[00:02:47.328] GSX Pro version 3.7.4 is installed, checking remote version on update
[00:02:47.516] GSX Pro latest version is 3.7.4
[00:02:47.844] AIManager: Querying AI aircraft within 6000m...
[00:02:47.860] AIManager: No AI aircraft found in range
[00:02:50.531] [GSX] Waiting for airport data... (1s)
[00:02:50.531] FacilitiesCache.unsubscribe()
[00:02:50.531] FacilitiesCache.refreshSubscribe()
[00:02:52.719] [GSX] Waiting for airport data... (20s)
[00:02:52.781] FacilitiesCache.unsubscribe()
[00:02:52.781] FacilitiesCache.refreshSubscribe()
[00:02:53.547] [GSX] Waiting for airport data... (40s)
[00:02:53.610] FacilitiesCache.unsubscribe()
[00:02:53.610] FacilitiesCache.refreshSubscribe()
[00:02:59.000] [GSX] Waiting for airport data... (60s)
[00:03:00.000] FacilitiesCache.unsubscribe()
[00:03:00.000] FacilitiesCache.refreshSubscribe()
[00:03:05.188] requestFacilityData FAOR
[00:03:05.235] requestFacilityData DONE FAOR
[00:03:05.235] Loading airport FAOR
[00:03:05.250] Using airport customization from user Python faor-inibuilds
[00:03:05.578] Loading user customizations from C:\Users\peter\AppData\Roaming\Virtuali/GSX/MSFS\faor-iniBuilds.ini
[00:03:05.578] jetwayHeightsDict = {'faor_jetway_type1': '4.0', 'faor_jetway_type2': '5.05', 'faor_jetway_type3': '5.05', 'faor_jetway_type4': '4.20', 'faor_jetway_type3b': '4.5', 'faor_jetway_type3c': '4.5'}
[00:03:05.766] [GSX] onEnteredAirport FAOR
[00:03:05.860] FacilitiesCache.unsubscribe()
[00:03:05.906] This plane is missing the attachModelSeats definition=None
[00:03:05.906] No valid FSDT_Passengers_Seats.xml for airline None
[00:03:05.953] Jetway status REST, power = (None,2), air = (None,1)
[00:03:05.953] Requested parking services to Apron A|Stand A7
[00:03:05.953] Marshaller distance readout disabled by user preferences
[00:03:05.953] aircraftEngaged
[00:03:05.953] creating SimBrief object
[00:03:05.969] Trying SimBrief with username: https://www.simbrief.com/api/xml.fetcher.php?username=captpero
[00:03:06.844] SimBrief data fetched successfully with username
[00:03:06.844] Icao airline was None
[00:03:06.844] Icao airline set by Simbrief to CFG Condor Flugdienst GmbH None language ('en-de', 'euro')
[00:03:06.875] Parsed 12 waypoints from SimBrief navlog
[00:03:06.875] The loaded flight plan from FAOR doesn't match the one on SimBrief, from FMMI to FMCZ
[00:03:06.875] emulateMenu_MSFS
[00:03:08.063] Detected entry from main menu (camera state: 16.0 -> 2.0)
[00:03:08.063] Auto-repositioning scheduled from main menu
[00:03:11.141] Auto-repositioning to parking 12
[00:03:19.188] Parked: distance error = 0.00 ft, offtrack error = -0.00 ft, heading error = 0.00 deg
[00:03:32.500] emulateMenu_MSFS CHOICE 5
[00:03:32.500] channel.balance = -1
[00:03:32.547] Requested assistance services at Apron A|Stand A7
[00:03:32.547] FSDT_GSX_SetGate 12 7 0
[00:03:32.563] Jetway status REST, power = (None,2), air = (None,1)
[00:03:32.656] emulateMenu_MSFS
[00:03:35.469] emulateMenu_MSFS CHOICE 1
[00:03:35.469] channel.balance = -1
[00:03:35.485] FSDT_GSX_NUMPASSENGERS is 0
[00:03:35.500] EMPTY WEIGHT = 93697, FUEL TOTAL QUANTITY WEIGHT = 7262, TOTAL WEIGHT = 136692.328125, MAX GROSS WEIGHT = 174165.0
[00:03:35.500] Payload:35733/73205 lbs.
[00:03:35.500] Set passengers to 162 (payload of 35732 / 220).
[00:03:35.516] FSDT_GSX_NUMPASSENGERS is 0
[00:03:35.516] Estimated number of passengers is 162
[00:03:35.641] AssistanceServices.showMessage() Handling by Nas Colossal WHITE
[00:03:35.641] AssistanceServices.showMessage() This gate has a standard jetway. WHITE
[00:03:35.641] AssistanceServices.showMessage() Jetway operating WHITE
[00:03:35.641] setNumVagons()
[00:03:35.641] FSDT_GSX_NUMPASSENGERS = 0.0
[00:03:35.641] FSDT_GSX_MAX_NUMPASSENGERS = 0.0
[00:03:35.641] FSDT_GSX_SIMBRIEF_CARGO = 0.0
[00:03:35.641] FSDT_GSX_SIMBRIEF_UNITS = 0
[00:03:35.641] FSDT_GSX_SIMBRIEF_FUEL = 0.0
[00:03:35.641] FSDT_GSX_SIMBRIEF_MAX_TOW = 0.0
[00:03:35.672] EMPTY WEIGHT = 93697, FUEL TOTAL QUANTITY WEIGHT = 7262, TOTAL WEIGHT = 136692.328125, MAX GROSS WEIGHT = 174165.0
[00:03:35.672] Payload:35733/73205 lbs.
[00:03:35.672] Set Wagons according to Payload
[00:03:35.672] Set 2/3 wagons, according to loading ratio of 48.81%
[00:04:04.266] Jetway status FULLY_ATTACHED, power = (None,2), air = (None,1)
[00:04:04.266] AssistanceServices.showMessage() Jetways operation completed GREEN
[00:05:03.766] Stopped infinite generation of Passengers
[00:05:31.125] emulateMenu_MSFS
[00:05:33.063] emulateMenu_MSFS CHOICE 5
[00:05:33.063] channel.balance = -1
[00:05:33.125] AssistanceServices.showMessage() This gate has a standard jetway. WHITE
[00:05:33.125] AssistanceServices.showMessage() Jetway operating WHITE
[00:05:56.500] Jetway status REST, power = (None,2), air = (None,1)
[00:05:56.500] AssistanceServices.showMessage() Jetways operation completed GREEN
[00:05:57.438] emulateMenu_MSFS
[00:05:59.797] emulateMenu_MSFS CHOICE 5
[00:05:59.797] channel.balance = -1
[00:05:59.860] AssistanceServices.showMessage() This gate has a standard jetway. WHITE
[00:05:59.860] AssistanceServices.showMessage() Jetway operating WHITE
[00:06:17.938] Slew mode True
[00:06:18.156] Traceback (most recent call last):
[00:06:18.156] File ".\GSX\assistanceServices\jetwayOperations.py", line 453, in _trigger
[00:06:18.156] Exception: requestJetwayData Internal error (dwIndex == 99)
{'User Pos': (-26.132875851432278, 28.232988658623466, 1690.49 m, 2.71875 m, 276.35498779296876, 0.006118051953273931, 0.003490658476948738, -0.00031063284561868085, 2.7096721046447754, 1.0), 'Airport': 'FAOR', 'Requested parking services to': 'Apron A|Stand A7', 'Requested assistance services at': 'Apron A|Stand A7'}
-
Can someone confirm that the crash is reproduceable at different airports?
For me it looks like some are working without CTD and others (EPWA) causing a CTD when using GSX and AIG is injecting traffic.
-
I tested it at KMSP, the same airport where MSFS crashed to desktop several times before.
Just to mention, I don’t think it’s a model issue. I’m using FSHud together with the AIG flight plans and models.
I did notice that FSHud injects around 20 aircraft less.
Maybe you can test what happens if you reduce AIGTC injection.
-
I tested it at KMSP, the same airport where MSFS crashed to desktop several times before.
Just to mention, I don’t think it’s a model issue. I’m using FSHud together with the AIG flight plans and models.
I did notice that FSHud injects around 20 aircraft less.
Maybe you can test what happens if you reduce AIGTC injection.
FYI: KMSP is running on my system (default airport) without CTD. Strange... Maybe related to some models that are getting in conflict with the new LOD change of GSX?
-
I have just returned home and do not have time to deal with this at the moment, but I have a question for anyone who has tried the test version.
Are you able to revert to 3.7.4 after testing?
-
I tested it at KMSP, the same airport where MSFS crashed to desktop several times before.
Just to mention, I don’t think it’s a model issue. I’m using FSHud together with the AIG flight plans and models.
I did notice that FSHud injects around 20 aircraft less.
Maybe you can test what happens if you reduce AIGTC injection.
For info:
I did my recent MSFS 2020 testing of 3.7.4 at EGLL iniBuilds London Heathrow and VHHH WF Scenery Hong Kong International, always with AIGTC injection limited to 75%.
-
New very interesting finding:
1) Starting in EPWA Gate 15 at current time (1500z), load AIG - no CTD
2) Close AIG > Restart AIG > no CTD
3) Close AIG > Change time to 13.15z > Load AIG > CTD
Reproduceable. So it looks like the new GSX Version gets in conflict with an or multiple AIG model?!
Can someone pls try to reproduce this with MSFS2020?
-
I created SimConnect log files to determine whether a particular aircraft or model is the last one loaded, in order to find out if it is causing the CTD.
The strange thing is that the crash occurs at a specific point in EPWA and is reproducible.
And it happens on default EPWA as well.
Conclusion:
- not depending on a specific aircraft model
- not depending on a scenery
I have no idea how to keep on searching...
-
Hi
I have CTDs few days ago. I post my tests in other topic about same problems. I use GSX and Beyond ATC traffic, that uses AIG and FSLTL models.
Last Saturday I had my first CTD in EHAM between 14.00 and 16.00 zulu. My GSX autostarts then BeyondATC injects traffic and CTD. No problem in other airport (LGAV at that time). EHAM on Sundays NO CTDs. Today (Thursday at 19.00 in EHAM) first Beyond ATC injects traffic, then start manually GSX and CTD again.
I see in BEYONDATC support forum topics about this issue and they have a main suspect (GSX)
-
Can someone confirm that the crash is reproduceable at different airports?
For me it looks like some are working without CTD and others (EPWA) causing a CTD when using GSX and AIG is injecting traffic.
I did test in all major Asian airports (RJAA RJTT ZSPD VHHH VTBS WSSS etc) with 100% AIG injections and CTD all over the place. I tried to reduce injection to 50% or even 20%, still CTD. Big airports with most AI is the best sample because before 3.7.4 I didn’t get any issues for that heavy load or heavier. I don’t think the issue is related to a certain model because I’ve talked to AIG and they didn’t change any model last several weeks. Now if we talk about simobjects amount, the only resolution is reducing AI injection, however, you can see my test result, reducing amount in big airports doesn’t help at all.
-
Regarding to time, some local forums mentioned this issue significantly happened in Asia area so everyone doubted a time zone problem because when you load in an Asian airport you technically have a day ahead. I changed days backwards, daytime or night, early morning or dead midnight, no effect at all.
-
Simply to fill in here a bit.
I've tried multiple injectors. FSHUD, BATC and AIGTC to be precise with MSFS2020 and still the same result, CTD. Tried both at small and large airports. I'm using AIG models. I did some tests with FSLTL models and that didn't always result in a CTD, not sure what that really means though, are they more lightweight somehow?
I'll try the beta and see how that works. :)
-
Simply to fill in here a bit.
I've tried multiple injectors. FSHUD, BATC and AIGTC to be precise with MSFS2020 and still the same result, CTD. Tried both at small and large airports. I'm using AIG models. I did some tests with FSLTL models and that didn't always result in a CTD, not sure what that really means though, are they more lightweight somehow?
I'll try the beta and see how that works. :)
You are right. FSLTL injects way less AI than AIG TC because it only gets live flights plus some ground parked aircraft which is adjustable. AIGTC injects live flights and local offline weekly planned flights together to fill your airport. That’s why somebody saw less CTD on FSLTL. Anyway, like I said, before 3.7.4 my pc can handle an airport with almost 200 ramp spots full of AI with still a very reasonable FPS. The problem is not about that.
-
Hi, I hope this can help in some way. I am still using MSFS 2020 and since the last update I am also having the issue with the CTDs. First I have tried to disable the couatl.exe from loading. Strangely I still had the CTDs as soon as I started a flight, airport and airplane didn´t matter. The only way to stop the CTDs was by deactivating the license which removed three linked GSX folders from the Community folder. Could the issue be lying in one of these three folders? By the way, I am using FSLTL and haven't changed anything in the settings for a very long time. Is it possible for us to just use the previous version until the culprit is found? I would really like to be able to use GSX!
-
Now, for full disclosure, I'm running a slightly updated version of GSX, that contains some fixes for some likely (but maybe not) unrelated problems with .NET. They should be unrelated, since they would happened with 3.7.3 as well, but in case they are, I suggest trying the Beta updater I posted here and see if it makes any difference:
Please test with the original 3.7.4 version that we are reporting problems with and using MSFS 2020.
-
Please test with the original 3.7.4 version that we are reporting problems with and using MSFS 2020.
Of course I won't do that: that will be part of the next update, and I don't see how it's helping anybody knowing if an soon to be outdated version could cause this, of course I couldn't replicate it with the older version, but I didn't test MSFS 2020. Now I also cannot replicate it with MSFS 2020 as well, but I'll always use the new version, and I urge everybody affected with this problem to test ONLY with the updated version I posted before, and I'll post it again now:
EDIT
The Fix is now included in the normal 3.7.5 update.
-
I did a test right now, with the updated GSX. Same result with BeyondATC injector: instant CTD. Maybe I did something wrong when installed the update version dowloaded from your link. I run the Addon Manager, install and play. I see that GSX needs manual start, despite in exe.html is set as autostart ( <Name>Couatl</Name>
<Disabled>False</Disabled>)
-
UPDATE: I managed to finally get my first CTD, using AIG models injected with BATC so, at least, I have something to work with now.
-
UPDATE
After being able to replicate the CTD, the fix was in fact quite easy.
Along the entire GSX code, in all places where we read the airplane "Title" (AI or User), we always used a string with up 256 characters, even if the official Simconnect specs says the Title can be up to 128 characters max. However, in the new centralized AI manager code that has been added in 3.7.4 so it could be shared between the Map and the new Progressive Taxi function, for some reason, the string to do the Simconnect request was set to be 64 characters.
This caused Simconnect to crash internally, if there were any AIs with names longer than 64 characters and, sure enough, there are several models in AIG with titles of 70+ characters.
The interesting thing is: in MSFS 2024 this Simconnect bug has been FIXED! Even if I purposely limit the max string size to 64 characters and there are AIs with longer titles, the sim returns what you would expect: a title truncated to 64 characters, as you can see in this test I just made by adding logging titles for all AIs at EPWA injected with BATC:
AIGAIM_LOT Polish Airlines Embraer EMB-195 - Belly Titles
AIGAIM_LOT Polish Airlines Embraer EMB-175
AIGAIM_LOT Polish Airlines Boeing 737 MAX 8 - Wifi dome Belly Ti
The last one has a title longer than 64 characters, and in MSFS 2020 it would have caused Simconnect to crash internally when queried, but in MSFS 2024 it just returns the truncated title (as expected), without crashing. It even works if I make a request with 32 chars strings; all AI titles are returned truncated to 32 chars, with no crashes:
AIGAIM_Wizz Air Airbus A321-200S
AIGAIM_LOT Polish Airlines Embra
AIGAIM_LOT Polish Airlines Embra
AIGAIM_LOT Polish Airlines Embra
It's very likely somebody must have reported this to Asobo for MSFS 2024, since I was very surprised to find they fixed a bug in Simconnect that must have been there for years. Unfortunately, to fix it in MSFS 2020 would require an update of the sim, but it's not really an issue, since now that we found the underlying cause, the fix was really easy.
Setting the max string length to 256 like the rest of the GSX code has fixed the CTD with AIG for me. If you download again the Beta version, it's already updated with the fix:
EDIT
The Fix is now included in the normal 3.7.5 update.
-
Interesting. I hope it solves the problem.
I had been wondering if there might have been a SimConnect issue with different versions for MSFS 2020 and 2024.
Is GSX for MSFS 2020 compiled and using the latest SimConnect from SU16 SDK, and for MSFS 2024 is it compiled and using the latest SimConnect from SU4 SDK?
-
Is GSX for MSFS 2020 compiled and using the latest SimConnect from SU16 SDK, and for MSFS 2024 is it compiled and using the latest SimConnect from SU4 SDK?
Sure, we have several couatl .exes depending on the sim ( FSX/P3D, MSFS 2020 and 2024 ) and each one is native built with the latest Simconnect SDK available.
However, I think in this case the problem lies in the sim itself (the Simconnect server) rather than the client (the one we get in our .exe by linking with the various SDKs), since the sim (MSFS 2020) just crashes with no errors, no Simconnect exceptions returned, not even an entry in the Event Viewer, while MSFS 2024 simply returns the title truncated to the max length specified, as one would expect.
-
Yes having no error reporting in MSFS 2020 has made things difficult to identify.
-
I just wanted to test with the new offline installer and received the following error message while activating GSX in the FSDT installer. This happened during the install within the updater before I ever used the offline installer. What does this mean?
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at Couatl_Updater2.Program.ApplyEnabledCore(DataTable table, List`1 paths, Boolean parentFolderMode, Boolean enabled, IProgress`1 progress)
at Couatl_Updater2.Program.<>c__DisplayClass289_0.<RunApplyServicesAsync>b__1()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Couatl_Updater2.Program.<RunApplyServicesAsync>d__289.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Couatl_Updater2.Program.<ReconfigureGSX>d__251.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9323.0 built by: NET481REL1LAST_25H2_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Couatl_Updater2
Assembly Version: 2.0.9488.42068
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Net.Http
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Net.Http/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Net.Http.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9321.0 built by: NET481REL1LAST_25H2_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9319.0 built by: NET481REL1LAST_25H2_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
QlmLicenseLib
Assembly Version: 18.0.24343.2
Win32 Version: 18.0.24343.2
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/QlmLicenseLib.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Web.Services
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Web.Services/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
INIFileParser
Assembly Version: 2.5.2.0
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
xEWPPkTHjwTb
Assembly Version: 0.0.65535.65535
Win32 Version: 18.0.24343.2
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/QlmLicenseLib.dll
----------------------------------------
?
Assembly Version: 0.0.0.0
Win32 Version: 18.0.24343.2
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/QlmLicenseLib.dll
----------------------------------------
System.Security
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Security/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Security.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.IO.Compression.FileSystem
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.IO.Compression.FileSystem/v4.0_4.0.0.0__b77a5c561934e089/System.IO.Compression.FileSystem.dll
----------------------------------------
Newtonsoft.Json
Assembly Version: 13.0.0.0
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
SharpCompress
Assembly Version: 0.41.0.0
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
System.Memory
Assembly Version: 4.0.5.0
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
System.Runtime.CompilerServices.Unsafe
Assembly Version: 6.0.3.0
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
ZstdSharp
Assembly Version: 0.8.6.0
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
System.Threading.Tasks.Extensions
Assembly Version: 4.2.4.0
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
System.Buffers
Assembly Version: 4.0.5.0
Win32 Version: 2.4.0.6
CodeBase: file:///D:/MSFS%20Addons/Addon%20Manager/Couatl_Updater2.exe
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
-
I've done my test in 4 different airports (RJTT, ZSPD, VHHH and RJAA) after new beta update, all passed with no CTD anymore! I loaded into the airport by using AIGTC auto injection to make sure it can inject AI as soon as possible, it seems no more issues as GSX is also running at the same time. Tomorrow I'll do some short and mid haul flights to see how stable it is. A side effect not very sure it's due to my new updated GPU driver today or this beta update itself, I felt my FPS is getting lower than before, even it's still acceptable. Hope it's just my illusion. Anyway, so far I believe we've solved that. Let's see more feedback.
-
I've done my test in 4 different airports (RJTT, ZSPD, VHHH and RJAA) after new beta update, all passed with no CTD anymore! I loaded into the airport by using AIGTC auto injection to make sure it can inject AI as soon as possible, it seems no more issues as GSX is also running at the same time. Tomorrow I'll do some short and mid haul flights to see how stable it is. A side effect not very sure it's due to my new updated GPU driver today or this beta update itself, I felt my FPS is getting lower than before, even it's still acceptable. Hope it's just my illusion. Anyway, so far I believe we've solved that. Let's see more feedback.
Happy to read that. For me its not solved. Can you pls test the mentioned scenario as well (EPWA)? Are you using MSFS 2020 as well?
Sorry, I've not read, that a bug in String length (in SimConnect) has been determined. I will test the new version now.
-
I am very happy to report that the offline installer seems to have fixed the problem on my MSFS2020. Tested with a flight from LFLB to LOWI. Everything worked perfectly, thank you for the fix!
-
Must I remove the GSX version installed before install the offline updated version? As I mentioned before I have CTDs with the offline updated version, and maybe I did something wrong.
I think the tests must be done always at same time and same place. The CTD occurs when a particular plane is injected. I have my CTD in EHAM at 19.00 Thurday, Saturday 14.00-16.00, etc, with BATC traffic injection using in first place AIG models.
Thanks for your help
-
In my case the sim crashed as soon as I loaded a flight. Sometimes the sim even crashed before it finished loading a flight. Airplane and airport didn´t matter in my case at all. I disabled the "Couatl64_boot.exe" in the exe.xml file and the sim still crashed. There are also three folders from GSX which are placed in the Community folder. The CTDs only stopped after removing the three GSX folders. I am also using FSLTL which I have never touched. All I have done is run the FSDT installer once and then I ran the offline installer. It is very important that you do not run the FSDT installer after running the offline installer. The offline installer is the last step you do. I hope this information helps in some way. So far I have only done the above mentioned flight and everything just magically worked!
Since I still have my sim loaded, I went ahead and loaded the Fenix in EDDF with FSLTL running. I haven´t restarted the sim since the last flight and there is no CTD. It indeed seems to be fixed.
-
Must I remove the GSX version installed before install the offline updated version?
No, of course not, the offline installer it's just the latest code, only 200MB, the whole GSX is like 16GB, if you uninstall it, nothing works.
As I mentioned before I have CTDs with the offline updated version, and maybe I did something wrong.
Your last post was made BEFORE I explained the problem has been found and a new Offline installer was posted, so you need to download it again and install it.
-
Please confirm all CTDs are gone now, so we can make it official.
Confirmed fixed. I did several tests at different airports and day times. Looks good! Thank you!
-
I can confirm that the issue is fixed from my side. No more CTDs at different airports in Asia where I had these CTDs since version 3.7.4.
Thank you for your help!
-
Confirming from my end that the offline update in this thread has fixed the problem. I could always pinpoint one exact AI variation which caused a CTD 100% of the times it was injected over the last few weeks, so I had been using that exact AI variant as my troubleshooting reference rather than just injecting any traffic and potentially not getting a CTD by luck. With this update I have been able to inject my troublesome AI variant successfully for the first time with 3.7.4 running.
Thank you!
-
All fine now with 3.7.5.
Thanks Umberto for digging and providing a fix. :)