Sorry, freighter.
I have the same problem as you, how did you get an old version of coautl?
Using an older version of the Couatl engine is the wrong solution to this problem, the correct solution is understanding why the Intel driver crashes.
For the next update, due out soon, we found a way to automate the selection of the main graphic driver (nVidia or AMD), and this should fix the problem with the app being selected to run on the Intel integrated graphics instead of the main graphic card.
However, it wonāt fix the issue for those using an actual Intel ARC discrete graphic, because the main graphic card is also Intel, and also requires the crashing driver.
Until november everything worked perfectly, then it didnāt work anymore. Thatās why i ask for an old version of coautl so that until the problem can be solved i can reuse gsx
And I already explained that nothing in the Couatl engine could possibly have any effect on the graphic drivers, since itās not doing ANY graphic calls, no DirectX, nothing.
Since you havenāt said which sim you are referring to, I can only explains the changes happened:
MSFS 2024
The Couatl engine for MSFS 2024 has been updated November 19th, the day MSFS 2024 came out (version 3.2.7) to be built with the released version of the MS2024 SDK. The previous version was made with the Alpha version of the SDK and, since it was only available to MS Partners in the Marketplace, saying āit worked until Novemberā in this case is not really relevant, since nobody except MS Marketplace partners could have possibly tested GSX in MSFS 2024 until then.
MSFS 2020
With version 3.3.5, released in January, both versions were updated again to subscribe only to the āVISUAL_FRAMEā Simconnect event, since it was reported by multiple developers the "SIM_FRAME " event sometimes stops, causing frozen instruments and, in GSX case, stuck menu, which is caused by simconnect events not arriving.
Some users with an Intel graphic card reported that while the 2020 version still used to work until January, now it also stopped working.
This seems to indicate the the Intel drivers are crashing ājustā because we now have more certainty to be called at every frame, which wasnāt always guaranteed before, due to the SIM FRAME event not always reliably happening at every frame.
Yes, thereās no difference in frequency: multiple tests have proven both VISUAL FRAME and SIM FRAME events happens with the same frequency, just that sometimes SIM FRAME stops for no reason.
Itās likely that internally, the two calls are not handled in the same way but of course, itās not as if we can control from GSX WHAT happens INSIDE the sim during a Visual Frame event and prevent the Intel driver being confused by this.
Thatās not how Simconnect apps work, we can only tell the sim ācall me back when this Event happensā, what happens inside itās a black box.
As Iāve said, we found a way to stay away from the Intel driver, by adding two variables in the .EXE that would help the nVidia and AMD drivers to be sure the Couatl engine will never use the integrated Intel adapter, so this will help all those with Hybrid graphics to use the correct card, but it wonāt fix the problem of the Intel driver for those using a discrete ARC graphic card.
And to finally dispel ANY possible remaining doubt about the issue being caused by a buggy Intel driver, we made the following test, with two separate PCs both using Hybrid graphics:
- On BOTH PC (two MSI laptops), we configured the settings to FORCE everything to run on the Integrated Intel adapter.
- The Couatl engine works perfectly fine with no crashes, even if MSFS itself was running extremely slow and the sim gave us a warning that it didnāt meet the minimum requirements.
I think this would finally prove the problem are the dedicated Intel drivers, because not having any need to run the sim on it, we were probably using the default Intel drivers that come with Windows, which are likely very slow, but they work, proving thereās just nothing wrong in the Couatl engine and of course nothing we can do about it, since the problem likely happens only with the dedicated Intel drivers.
1 Like
so youāre telling me I can uninstall it and ask for a refund because neither fsdt nor Intel solves the problem? mine is msfs 2020
CPU i710700kf
GPU Intel arc b580
32gb di ram
Yes, you should ask a refund to Intel because they sold you a video card with buggy drivers.
Does Intel has ANY explanation why:
- It WORKS with nVidia
- It WORKS with AMD
- It WORKS with the Intel drivers supplied with Windows
The one and only case where it doesnāt work, is with Intel ARC cards using Intel own drivers. What is crashing is the Intel .DLL here.
Somebody said he contacted Intel support, saying we should contact them. How, exactly ? Feel free to send me a PM with details.
Not that this would make any difference to our side. The most we can do, is just explaining we are not making any graphic calls, we are just using 100% standard MSFS SDK approved methods, so at best they might try to figure it out why their drivers has issues with MSFS itself, so perhaps they might fix it.
Please contact me with some info about your ticket with Intel, which might be useful to refer to, in case Iāll try to contact them.
I reported this on GitHub in February.
I received a response from Intel saying the GSX developer would need to report this issue directly on Developing Games on Intel Graphics forum so that Intel and the developer could work together on a solution.
I replied on Intel forum by supplying as much info as possible, letās wait for their answer.
can you tell me on which Intel forum you wrote so I can send them my errors too?
I opened a ticket on Intel supportā¦we are waiting for an answer
1 Like
Version 3.4.0 ā March 28th, 2025
-
GSX Pro NEW: New CHAMP70 Cargo Loaders, available in 3 variants (S, W, U), with loading bridges adapting automatically to the airplane cargo door width.
-
GSX Pro Change: Couatl engine updated to signal nVidia and AMD drivers to always use the discrete graphic adapter.
-
GSX Pro Change: Some improvements to iniBuilds A300 internal profile.
-
GSX Pro Change: Tooltips are temporarily disabled if MSFS 2024 SU2 Beta is detected, as a workaround for SHOW_TOOLTIP Coherent API call that stopped working in the first SU2 Beta. This will prevent the blue empty Tooltip stuck on screen in 2024 SU2 Beta.
-
GSX (all versions) Fix: Main Cargo wagon passing under the airplane when going away empty in some airports.
8 Likes
Just recently in MS 2024 the GSX on screen messages dont show anymore even with them enabled in the GSX settings. Is there something in the sim that can disable messages?
2 Likes
Yep, just experienced the same thing after the update.
Yet it works properly in 2020ā¦
Hi all, I am on SU2 beta and seems like GSX no longer recognizes that the plane is setup for ābeltā only cargo loading? Is this a known bug for SU2 beta. All was good in SU1. I have the latest version of GSX (downloaded today).
Thanks,
Same with 2020, since 3.4.0 I no longer have the refueling countdown messages and the number of passengers boarding
Assuming you are NOT on SU2 (so itās normal to have lost Tooltips, since they are not working in SU2 and are impossible to remove as well), can you enable Logging in GSX and check the Couatl.log to see which Simulator version is reported ?
Maybe, the problem is they havenāt changed the version reported through Simconnect with SU2 Beta, making impossible (or more difficult), for 3rd party apps to recognize itās the beta.
Is GSX able to be tweaked to slow down the baggage loading process and leave the belt loaders in place until before pushback? Currently it takes GSX only a few minutes to load a packed A321 with baggage and then the loaders pull away, leaving the cargo hatches open for the rest of the 20 minute boarding process. In RL even after loading is completed, you typically have one or both belt loader remaining in place so that any checked bags generated during the boarding process can be loaded into the cargo bays. Right now, itās pretty unrealistic how quickly these loaders are present for.
Also, is it possible to replicate external power coming from cables on the jetway instead of a generator sitting on the ramp, which I donāt think Iāve ever seen in RL? Not sure if this is within the realm of GSX or the sim itself.