When I fly a long flight(1.5hr above), with Gees(landing monitor), pilot2ATC(with FSUIPC), and simToolKit Pro all turned ON, my understanding is that these client application all gets data via simconnect.
Everytime when these client application is ON, when I do the STAR or final approach, the game crashes.
When I turn these application OFF(with just FSUIPC connected to MSFS), I have no CTD.
My thought is that when other client application getting data from simconnect, it crashes the CTD.
I search the forum but it seems like this problem is already there since Jan 2021. However no solution or any official answer from the developers. I wonder if there is any update on this matter?
Surely quite a lot of people also use client application that draws data via simconnect. Have any of you guys experienced same issue or may be even fixed the problem?
Please share your comments.
1 Like
Given that you suspect third-party software Gees, Pilot2ATC and SimToolKit Pro, the first thing to do is to contact each vendor and see what troubleshooting and advice they have.
If the sim doesn’t crash when they’re all turned off, then one or all of them are part of the problem.
Have you tried using only one at a time to see which of the three might actually be the suspect? That would narrow down contacting three different makers.
The problem could be with the SimConnect API on the sim side, not the third party software (although I still agree with your recommendations to try one at a time and contact the third party software vendors).
For example Sim Update 2 back in December inadvertently added a CTD on the simulator side of SimConnect that was supposedly fixed in WU3.
I tried the following.
Only simToolKit Pro → CTD
Only pilot2ATC → CTD
nothing ON just FSUIPC connect to sim–> no CTD.
So I suspect it only happens when drawing data from simconnect.
Hi,
I use NaviGraph and there are no issues.
I am noticing this issue, too. I use Pilot2ATC often and I have been experiencing crashes. When not using Pilot2ATC then no crashes