I guess it is related to AI traffic, but:is it caused by a faulty flightplans.bgl or a corrupted texture? or something else?My traffic is carefully maintained using ACA2007...Anyone with a suggestion?ThanksGhiom

I guess it is related to AI traffic, but:is it caused by a faulty flightplans.bgl or a corrupted texture? or something else?My traffic is carefully maintained using ACA2007...Anyone with a suggestion?ThanksGhiom

Going to need more details such as when do you get the CTD (upon starting up FS2004 or during flights or ????) and have you used the utility named FS9 Configurator (it edits the AI_PLAYR.DLL file) to edit the taxi speed etc. of AI traffic?

It was during a flight off HNL.I have patched this dll long time ago to improve ai taxing speed. But I have never have this problem since.I updated some traffic files recently in Hawaii... I wonder.But would this be related to the bgl, the afcad, some texture?ThanksGhiom

I updated some traffic files recently in Hawaii... I wonder.But would this be related to the bgl, the afcad, some texture?

Yes! Can you possibly go back to the state it was before this update?

Even if I would, it would not tell because I haven't flown in this area for quite some time. And I am sure I have made changes in this past time...ThanksGhiom

Could it be a missing AI night texture?As it happened at night?The question is therefore: is a missing light texture likely to cause a CTD?ThanksGhiom

I guess it is related to AI traffic, but:is it caused by a faulty flightplans.bgl or a corrupted texture? or something else?My traffic is carefully maintained using ACA2007...Anyone with a suggestion?ThanksGhiom

It may be caused by multiple AFCAD files that have differing co-ordinates. It isn't necessarily the nearest airport but one that has just come into range to load the AI aircraft.John