Author Topic: CTDs are not caused by GSX  (Read 17179 times)

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51917
    • VIRTUALI Sagl
Re: CTDs are not caused by GSX
« Reply #15 on: December 21, 2024, 09:03:13 pm »
Since 3.3.1 everytime when I start a flight at the gate, I got an CTD with error:

0xc0000005 and coherentuigt.dll

When I unlink GSX, no crash. Tryied it several times...

The oherentuigt.dll is a very well known crash that it's completely unrelated to GSX, and it's caused by some airplane gauges, but it's not a problem of the airplanes either, it's a problem in the coherent GT version used in the sime.

I'll repeat it for the last time, GSX can't crash the sim, let alone in that .dll. Fact it "seems" to be fixed by unlinking GSX doesn't prove the slightest GSX is the cause, it's just because the problem might only appear after a certain amount of memory usage is surpassed so, it might have disappeared by removing any other add-on just the same.

Rangerbob

  • Newbie
  • *
  • Posts: 1
Re: CTDs are not caused by GSX
« Reply #16 on: December 24, 2024, 02:03:20 am »
For years I have heard many complaints about how GSX causes CTD’s. You remove GSX, everything works fine, and you think it’s all fixed only to find GSX wasn’t the cause.

Umberto, unlike many other software developers, has always responded to issues and reports very quickly with specific instructions on how to fix or avoid the issue. Compare that with the support we receive from others, especially MSFS 2024. Compare Umberto’s easy link to have GSX work with MSFS 2024 on day one while all the other addons not yet working with MSFS 2024.

I have enjoyed using GSX along with his numerous airport upgrades, and we in the flight sim community are lucky to have his programs to enjoy. Listen to his responses and instructions with care.

BigMike

  • Newbie
  • *
  • Posts: 4
Re: CTDs are not caused by GSX
« Reply #17 on: March 09, 2025, 11:01:15 pm »
Hello,

Just wanted to chime in, ever since I first installed GSX Pro into MSFS2024 (Steam edition) I get CTDs while sitting at the gate every single time. After unlinking GSX my sim works just fine. I'm not sure how GSX is not the culprit causing the crashes but I'm also not a programmer. I attached the couatl.log after my last CTD, maybe someone can enlighten me and reveal how I can fix this issue as this is becoming somewhat frustrating. Been enjoying GSX in P3D for years and am looking forward to using it in MSFS2024  :)

GSX Pro 3.3.7 installed
Config: GSX Jetway Replacements & GSX Airport Services both disabled

MSFS2024 (Steam edition) Sim Update 1 (1.3.23.0) installed

If any further information is needed from my side, just let me know.

Regards
Michael G.
Best Regards
Michael Göbel

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51917
    • VIRTUALI Sagl
Re: CTDs are not caused by GSX
« Reply #18 on: March 10, 2025, 01:00:56 pm »
Just wanted to chime in, ever since I first installed GSX Pro into MSFS2024 (Steam edition) I get CTDs while sitting at the gate every single time. After unlinking GSX my sim works just fine. I'm not sure how GSX is not the culprit causing the crashes but I'm also not a programmer.

GSX cannot crash the sim. This is not open to discussion of negotiation. What can crash the sim, instead, is issues with Navdata, it has already happened (more than once), that problems like duplicate navaids or other issues in Navdata caused the sim to crash. In one case the problem was in the MS original Navdata, another case was a problem with Navigraph Navdata.

GSX cannot possibly work without querying the Navdata using the standard Simconnect call method, and this explains how you can be easily misled GSX is the "cause" (because it seems to be fixed if you disable it), when in fact it isn't, the real cause is a problem in the Navdata itself, which might translate into a crash if an app uses the official Simconnect method to query it.

BigMike

  • Newbie
  • *
  • Posts: 4
Re: CTDs are not caused by GSX
« Reply #19 on: March 10, 2025, 05:52:23 pm »
Hello again,

In which case, does anyone know what the remedy is or anyone know who I can reach out to for this issue (Navigraph, Microsoft/Asobo?)? I'm trying to figure out what my next steps are, I apologize for my naive questioning and my gaps in knowledge. I admit I'm not that tech savy and just would like GSX to work in my sim. The only thing that I know for sure is, when I unlink or uninstall GSX, my sim works fine. If someone could point me in the right direction (or found a fix for this), I would be very grateful.

Regards
Michael G.
Best Regards
Michael Göbel

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51917
    • VIRTUALI Sagl
Re: CTDs are not caused by GSX
« Reply #20 on: March 10, 2025, 06:14:32 pm »
In which case, does anyone know what the remedy is or anyone know who I can reach out to for this issue (Navigraph, Microsoft/Asobo?)?

If you use Navigraph Navdata, the first thing to try is to disable that one, instead of GSX, and see if it makes any difference.

BigMike

  • Newbie
  • *
  • Posts: 4
Re: CTDs are not caused by GSX
« Reply #21 on: March 10, 2025, 11:26:00 pm »
Tried exactly that as per your recommendation. Loaded up my sim, once with the fenix and once with the ini A330, in both cases CTDs after a couple of minutes. After unlinking GSX, all worked fine again. I must be doing something wrong.
« Last Edit: March 10, 2025, 11:28:08 pm by BigMike »
Best Regards
Michael Göbel

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51917
    • VIRTUALI Sagl
Re: CTDs are not caused by GSX
« Reply #22 on: March 11, 2025, 12:49:12 pm »
Tried exactly that as per your recommendation. Loaded up my sim, once with the fenix and once with the ini A330, in both cases CTDs after a couple of minutes. After unlinking GSX, all worked fine again. I must be doing something wrong.

Your log clearly shows MSFS crashed before GSX, and GSX even recognized it crashed. I'll repeat it again: crashes are NOT caused by GSX, the real cause of bad Navdata and, as I've said in my previous message, it doesn't *necessarily* be Navigraph, it happen even with the default data.

If you look the MSFS official forum, some users reported a crash near Paris, but while some users *think* it was fixed by uninstalling GSX, others have confirmed they still get it with NO GSX installed so, because the problem is the data, not GSX.

GSX might just make the problem more apparent, because it must query the Navdata to work.