Main Menu

[CLOSED] Constant AIGTC Crash (MSFS)

Started by nishantdeshpande, November 16, 2021, 11:16:33 AM

Previous topic - Next topic

nishantdeshpande

It worked quite well till yestarday but today I am facing several CTDs either during flight or while injecting traffic.
Attaching the logs.  ??? ??? ?

Cheers,
N

Kaiii3

can you add the Windows Event logs as well

nishantdeshpande

Faulting application name: AIGTech - Traffic Controller.exe, version: 0.5.0.5, time stamp: 0x9dcafb2a
Faulting module name: clr.dll, version: 4.8.4420.0, time stamp: 0x6109cbc8
Exception code: 0xc0000005
Fault offset: 0x0000000000058dd5
Faulting process id: 0xc74
Faulting application start time: 0x01d7dad3b08b51c6
Faulting application path: D:\AIG\AIG_TrafficController\AIGTech - Traffic Controller.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: bdb86593-ab2c-477f-a117-1761be5c60bd
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: FlightSimulator.exe, version: 1.20.6.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.20.6.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001385060
Faulting process id: 0xac0
Faulting application start time: 0x01d7dad019b4302a
Faulting application path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: a34d4df9-89ee-4af2-aac3-eb075c465f26
Faulting package full name:
Faulting package-relative application ID:

nishantdeshpande

Deleted zip file in resource folder
Restarted the sim and the PC

Still, AIGTC crashing after 2-3 mins of flight.
Here is the log files:

kalynn.4

same here. uninstalled and bought aerosoft simple traffic.

nishantdeshpande

Quote from: kalynn.4 on November 17, 2021, 02:52:52 AM
same here. uninstalled and bought aerosoft simple traffic.

Good for you, and you are still here in AIG forum for what exactly?  ::confused::

Kaiii3

I have an idea, and will test that today on my system... We had this issue in P3D but it was very rare.... Seems the "old" lagacy FSX based SimConnect has more potential issues we need to take care of on different systems ::confused::

nishantdeshpande

Quote from: Kaiii3 on November 17, 2021, 08:19:54 AM
I have an idea, and will test that today on my system.. We had this issue in P3D but it was very rare... Seems the "old" lagacy FSX based SimConnect has more potential issues we need to take care of on different systems ::confused::

Update:
Did a flight just now without a single crash. Only changes that I did:

- Update the Manager with your hotfix from yestarday
- Remove KLM airlines (thought it was doing something wrong based on someones comment on Discord)

Full 50 mins flight, buzzing with traffic without any CTDs or any hiccups.

AndyM001

I've had the program crash a few times as well, here is the windows event log,

Application: AIGTech - Traffic Controller.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFB48F58DD5 (00007FFB48F00000) with exit code 80131506.




Faulting application name: AIGTech - Traffic Controller.exe, version: 0.5.0.5, time stamp: 0x9dcafb2a
Faulting module name: clr.dll, version: 4.8.4420.0, time stamp: 0x6109cbc8
Exception code: 0xc0000005
Fault offset: 0x0000000000058dd5
Faulting process ID: 0x32a0
Faulting application start time: 0x01d7dbab7f40b3ca
Faulting application path: F:\AIG_TrafficController\AIGTech - Traffic Controller.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report ID: 6d6851ae-4940-4474-8a87-aa80a04eb8e4
Faulting package full name:
Faulting package-relative application ID:

Kaiii3

as I said: Bug within SimConnect we can not handle ::fighting:: I am still working on a workaround

AndyM001

Quote from: Kaiii3 on November 17, 2021, 12:53:34 PM
as I said: Bug within SimConnect we can not handle ::fighting:: I am still working on a workaround

Thanks  8)