GSX Pro no longer works on MSFS 2024 after 3.3.3 update

[edu2703]

Since 3.3.3 update, GSX Pro no longer works on MSFS 2024. The weird thing is that it works perfectly on MSFS 2020.

After investigating the problem, I discovered that the source of the problem is Couatl64_MSFS2024.exe specifically. It starts normally along with MSFS 2024, but as soon as I load a flight anywhere, it immediately closes and opens again, and thus begins a cycle of restarts, where it keeps opening and closing, and beacause of that, GSX Pro doesn't work on the simulator, showing the message ''Waiting for Couatl Scripting Engine to start''.

I don't have an antivirus other than Windows Defender. I checked the Windows Defender settings and the Addon Manager folder is still on the scan exclusion list. I've tried manually starting Couatl64_MSFS2024 using administrator rights and it didn't work. I  basically tried all the solutions in the manual and nothing worked. I believe that nothing in the manual is useful in solving my specific problem. I also did a clean reinstallation of both GSX and MSFS 2024 itself, which also did not solve the problem.

As a workaround, I'm manually starting Couatl64_MSFS instead with MSFS 2024, which has no problems on my PC, and it seems to work more or less well in 2024.

Since update 3.3.3 apparently brought an updated version of Couatl64_MSFS2024, I wonder if I could get access to the old version of it, which might work in my case?

[pete_auau]

3.3.4 is  the latest version of  gsx pro

[edu2703]

3.3.4 is  the latest version of  gsx pro

I know. I just reported that the issue started after the 3.3.3 update and still persist in version 3.3.4.

[virtuali]

I don't see any issues in your log, other than it stops when GSX is starting. Are you sure you ran an update CHECK in the installer, so all files are installed and checked ?

[edu2703]

I don't see any issues in your log, other than it stops when GSX is starting. Are you sure you ran an update CHECK in the installer, so all files are installed and checked ?

Yes. I did that and it's still the same.

I recorded a video showing the problem I'm having. As you can see, couatl64 doesn't crash immediately when booting with MSFS 2024. It loads and runs normally in the background. The problem only appears after loading any flight in the simulator and opening the GSX menu.

If it helps, I checked the Windows Event Viewer and it confirms that couatl64_MSFS2024 is crashing multiple times and says the faulting module causing this is igd12um64xeh.dll

Faulting application name: couatl64_MSFS2024.exe, version: 5.0.0.5577, timestamp: 0x678522aa
Faulting module name: igd12um64xeh.dll, version: 32.0.101.6557, timestamp: 0x679934e9
Exception code: 0xc0000409
Fault offset: 0x0000000000ed6058
Faulting process ID: 0x22C0
Faulting application start time: 0x1DB799A11F33305
Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS2024.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2133089e1a0733e8\igd12um64xeh.dll
Report ID: 09d14079-1250-4e93-9559-b2f6d3dc0a12
Faulting package full name:
Faulting package relative application ID:

https://www.youtube.com/watch?v=9WS1YUWKB-Y

[virtuali]

I recorded a video showing the problem I'm having. As you can see, couatl64 doesn't crash immediately when booting with MSFS 2024. It loads and runs normally in the background. The problem only appears after loading any flight in the simulator and opening the GSX menu.

If it helps, I checked the Windows Event Viewer and it confirms that couatl64_MSFS2024 is crashing multiple times

Couatl cannot crash the sim.

An external .EXE cannot crash another .EXE, this is something basic about how the Windows OS works, an .EXE don't have any access to the memory space of another .EXE, unless it attached itself to it posing as a Debugger, and Couatl doesn't do anything like that.

What is possible is the opposite. If the sim crashes for other reasons, it will MADE Couatl crash, because in order to exit cleanly, Couatl needs to receive a specific command via Simconnect the sim has quit. If the sim crashes abruptly, it won't send the normal quit message to it, which would trigger some extra memory cleanup Couatl must do on itself, which if not done, will result in Couatl crashing. Not that this matters much after the sim crashed because Windows itself will clean up the memory.

That's why you see the event related to Couatl.exe in the Event Viewer: it was made to crash because the sim crashed for other reasons, so you can be easily misled thinking Couatl was the cause, but it's not. It cannot, because as a regular .EXE, it doesn't have any way to make the sim crash. But the sim can crash it.

The Windows Event Viewer has timestamps, showing exactly when every event happened. I'm fairly sure that, if you check the time for the crash in Flightsimulator.EXE, it will show a timestamp a few seconds earlier than Couatl64_MSFS.EXE, clearly proving it was MSFS which caused the crash, and Couatl64_MSFS.exe crashed because of that, not the other way around.

says the faulting module causing this is igd12um64xeh.dll

Which further confirms the problem doesn't have anything to do with GSX, since that .DLL is not part of it. It belongs to the Intel graphic drivers so yes, the graphic driver made the sim crash, which MADE the Couatl engine crash because of the abrupt quit which didn't allow the Couatl engine to do its own memory clean up, misleading you it was the cause, when in fact it was the victim of the crash caused by the driver.

[edu2703]

Which further confirms the problem doesn't have anything to do with GSX, since that .DLL is not part of it. It belongs to the Intel graphic drivers so yes, the graphic driver made the sim crash, which MADE the Couatl engine crash because of the abrupt quit which didn't allow the Couatl engine to do its own memory clean up, misleading you it was the cause, when in fact it was the victim of the crash caused by the driver.

So, is there anything I could do about this?

[virtuali]

So, is there anything I could do about this?

If your graphic driver is crashing the sim, there's not much you can do other than possibly adjust (lower) your graphic settings, maybe your are exceeding the max available VRAM, and the driver is not very good handling the case, so instead of just slowing down, it crashes.

[edu2703]

So, is there anything I could do about this?

If your graphic driver is crashing the sim, there's not much you can do other than possibly adjust (lower) your graphic settings, maybe your are exceeding the max available VRAM, and the driver is not very good handling the case, so instead of just slowing down, it crashes.

Well, this is weird. My card is an Intel Arc A770 with 16 GB of VRAM. Since I play at 1080p, the simulator's performance is good and I've never had any VRAM limitations. But out of curiosity, I set the graphics to the lowest possible and the same problem persisted.

Since I have an Intel Arc card, my first suspicion was that the updated couatl64_MSFS2024 was somehow incompatible with Arc GPUs, but then someone on the GSX discord reported exactly the same issue as mine. I asked him what card he had and he replied that it was an RTX 4070.

With today's update (3.3.5), Couatl64_MSFS was updated and it also no longer works on my PC. As a consequence, GSX Pro no longer works in MSFS 2020 either and the GSX Pro is now completely unusable for me. This is getting ridiculous...

As I asked in the first comment, I would like to know if there is a way for me to install the old version of GSX Pro (3.3.2), which was the last version of GSX Pro that worked without problems in both simulators on my PC?

[virtuali]

Since I have an Intel Arc card, my first suspicion was that the updated couatl64_MSFS2024 was somehow incompatible with Arc GPUs

The Couatl engine doesn't have any relationship to anything graphic. It's just a custom Python interpreter, with no graphic libraries, and the one and only connection to the sim is through the standard Simconnect interface. No interaction whatsoever with any graphic systems in the OS.

but then someone on the GSX discord reported exactly the same issue as mine. I asked him what card he had and he replied that it was an RTX 4070.

It's impossible someone with an RTX 4070 could have the "exactly the same issue" you are having, because your crash happens in igd12um64xeh.dll and that's part of the Intel drivers, doesn't exists on other cards so no, the issue he's having is different.

With today's update (3.3.5), Couatl64_MSFS was updated and it also no longer works on my PC. As a consequence, GSX Pro no longer works in MSFS 2020 either and the GSX Pro is now completely unusable for me. This is getting ridiculous...

As I've said, nothing in the Couatl .exe can possibly crash the sim, this is not open to discussion, it just can't.

However, if the problem is related to your graphic driver ( we are not sure it still is, because you haven't provided with an updated Event viewer or said if you saw a crash in Flightsimulator.exe BEFORE the Couatl .exe crash ), it might be very possible that, because of a graphic driver bug, when GSX is creating what is a normally perfectly legal vehicle that works for everybody, since this vehicle has to be drawn by the sim, a graphic driver bug might crash the sim like that, so you can be easily mislead the problem was caused by GSX ( because "it doesn't happen if you remove it" ), but the real cause was some problem or bug that prevented the sim to create a fully working object on behalf of GSX and the graphic driver CAN crash the sim.

The way Simconect works, there's only one way to create objects, and it doesn't involve meddling with graphic at any level, it's just a command sent to the sim that says "please create the object named xxxxx at those coordinates", that's it, it's a black box for us, there's no "wrong" way to do it, if the object is legal according to the SDK ( and it surely is, otherwise the SDK wouldn't even compile it ), if the sim crashes, it's either because it has exhausted all RAM or VRAM, or because there are too many objects already, or if there's some problem in the graphic drivers.

Sometimes, MSFS simply doesn't start after Windows has been running for a very long while and MSFS was started too many times. A Windows restart usually fixes it. Again, nothing that has anything to do with GSX.

[edu2703]

Sometimes, MSFS simply doesn't start after Windows has been running for a very long while and MSFS was started too many times. A Windows restart usually fixes it. Again, nothing that has anything to do with GSX.

Is there any way I can install and use older versions of GSX (3.3.2 or earlier) or at least have access to older versions of couatl64_MSFS and couatl64_MSFS2024 to be able to use GSX on my PC or do I just have to accept that I can't use GSX Pro on my PC anymore and move on?

[edu2703]

Today, I found a person on the GSX discord who has an Intel Arc A750 reporting exactly the same issue with couatl64_MSFS crashing and the Event Viewer pointing to igd12um64xeh.dll as the faulty module.

I reiterate the request to have access to the old version of GSX Pro or at least the old versions of Couatl64_MSFS and Couatl64_MSFS2024 so that I can at least use GSX Pro while this is being investigated.

[Captain Kevin]

I reiterate the request to have access to the old version of GSX Pro or at least the old versions of Couatl64_MSFS and Couatl64_MSFS2024 so that I can at least use GSX Pro while this is being investigated.

The only real way to do that would be to back up the Add-on Manager folder before you update it. Then if something doesn't work, you can at least copy the files over from the backup. The files get modified enough over time that I'm not sure they would have an old version so to speak since it's multiple files that get updated, not just one.

[virtuali]

Today, I found a person on the GSX discord who has an Intel Arc A750 reporting exactly the same issue with couatl64_MSFS crashing and the Event Viewer pointing to igd12um64xeh.dll as the faulty module.

No, it's a report of the SIMULATOR crashing in igd12um64xeh.dll, which CAUSED the Couatl  engine to crash as well, because for reasons I already explained in my previous posts, when the simulator crashes abruptly, it will very likely make the Couatl engine crash, misleading your it was the cause, when in fact it was the victim,

I reiterate the request to have access to the old version of GSX Pro or at least the old versions of Couatl64_MSFS and Couatl64_MSFS2024 so that I can at least use GSX Pro while this is being investigated.

It won't change anything, since an older version of the Couatl engine will suffer from a simulator crash caused by your graphic driver just the same. Please don't keep confusing the cause with the effect. The cause if the graphic driver crashing, and making the sim crash. The effect is the Couatl engine crashing because of that.

[edu2703]

It won't change anything, since an older version of the Couatl engine will suffer from a simulator crash caused by your graphic driver just the same. Please don't keep confusing the cause with the effect. The cause if the graphic driver crashing, and making the sim crash. The effect is the Couatl engine crashing because of that.

The simulator is NOT crashing for me. I open the simulator, load a flight, couatl keeps crashing in the background, but I can simply exit couatl and fly normally in the simulator without any issues. Only GSX doesn't work and that's it.

Simconnect is also not having problems because I use other applications that depend on simconnect to work and they are working normally.

The problem literally started after updating GSX Pro. On the day that update 3.3.3 came out, I did a flight in MSFS 2024 with version 3.3.2. I opened the GSX menu and saw the message that GSX was out of date, but I continued flying anyway. After I finished the flight, I went to the FSDT Installer and updated GSX Pro to version 3.3.3. When I went to start a new flight, right after updating, the problem started. I didn't make any changes to my PC that day. The exact same thing happened with the 3.3.5 update, also without making any changes. The important thing is that I didn't install any new Intel graphics drivers between the GSX updates. Rolling back to an old driver version doesn't solve the issue.

The chances of this being just a coincidence are very, very slim. Every bit of evidence I have gathered about this issue points to changes made to couatl64_MSFS2024.exe and couatl64_MSFS.exe with the 3.3.3 and 3.3.5 updates respectively, where some modification made to them is probably causing the issue.

I'm absolutely sure that the previous versions of couatl64_MSFS2024.exe and couatl64_MSFS.exe work without any problems on the PC and I can prove this to you. You just need to provide them to me.