FS9 CTD question ....

[dk1213]

The unknown module CTD.

This is by far the most annoying problem you can have when it comes to FS9. You set up your plane, plan your flight, and at 57% of the loading screen "microsoft Flight Simulator has encountered a problem and has to close." You look at the Event Viewer and APPCRASH for FS9.exe but everything else is unknown.
UUUUUUUUGGGGGGGGGGGHHHHHHHHHHHH!!!!!!!!!!
My first impulse is to break something ...... it just drives me nuts. In this case, I had planned a regular sortie for an IRIS F-22 out of Langley, to the MOA airspace and bam! CTD. Dead in the water. No reason I can think of to cause this. I am usually pretty meticulous about my sim, so I have no idea what the deal is this time. I know I had this happen once before and it was texture related, so I reinstalled Langley and still no go so that isn't it. I took off from Oceana, and CTD. The area is compromised if you try to fly over there. So it is something with the area and only during the day. At night I can fly out of Langley, I didn't check Oceana. I am really frustrated with this, but I am not sure where to look for a solution on this. Google was no help, and I don't even know what would cause this issue. The textures at least for langley are new, I reinstalled it. There are not any duplicate afcads in my sim. Everything seems in order, but I know one of you guys will have an idea something I didn't think of or know about that will lead to a solution. Its a real pain in the ass. I had this problem once before at another base and someone here on the boards helped me fix it, so I am hoping I get this squared away because there is so much military flying in that area I can't have it out of commission. Thanks!

[JohnTenn]

Dan

The way I isolate things like this is to disable sceneries until the problem goes away. Add back sceneries until the problem returns.

I have found sceneries with FS2002 style flattens create problems that persist for one more initialisation of the program and then go away.
Something to do with the scenery.dat file being updated.

At 57% is likely to be a landclass file and related texture or a terrain modification.
Photo ground textures without mip-maps also cause crashes.

I have even had a landclass file for somewhere in Myanmar that caused a crash on the Isle of Mann.

Hope this gives some hope.

John

[Firebird]

The only advice that I can offer on something like this is that you need to do some testing to narrow down the problem.

What I would suggest first is to narrow down the problem to whether it is a scenery or an aircraft problem. So remove all AI bgls from the system to a safe place and try that flight again. Now if it crashes at least you know it is scenery, and if it doesn't you know that it's an aircraft texture.
Once you know the area you are looking at then you can start to add or remove things to narrow it down. For example if it doesn't crash, add back the first 50% of your traffic bgls and retry. If it crashes then the problem is in the first 50%, if not the last 50%. If it doesn't then add another 25% of traffic so that you now have 75% and retry. You have now narrowed it down to 25%, and so on.

For scenery, disable the last 50% on your list (suggest taking a back up of your scenery.cfg first). Using the same methodology as the aircraft narrow it down.

If you are lucky as you get closer to one aircraft or scenery something might stick out at you like, I only recently added that or that is close the area where the crash happens, and you test by leaving out that one item.

I once had a scenery issue with bloody great walls across all my Seattle airfields. It turned out to be a lib in a recently added Indian airfield I downloaded.

[dk1213]

Thanks guys. Wow this is going to be tedious isn't it? I mean, I have major 4 or 5 MAIW bases in that area, Andrews, Langley, Oceana, Patuxent River, CVN-69, etc. and all the associated ai traffic going in and out and all the add on traffic on top of the MAIW traffic. It is going to take forever to figure this out, unless I get really lucky.

Thanks for pointing me in the right direction guys, I will start disabling sceneries and give it a shot until it goes away and start there. My worst fear is that it could be one of the traffic files or an ai aircraft going in and out of any of those locations. There has to be hundreds of AI planes in that area alone at any given minute. I really added alot of AI packages to Oceana, that area easily has the most traffic and AI add-ons. Wish me luck, I am gonna dive into it and see what I come up with. Thanks again guys. I really appreciate it.

Dan

[Firebird]

Absolutely, Dan. Hence why I suggest that you start by figuring out whether it is scenery or AI aircraft at the beginning. It will make life easier down the road.

[JohnTenn]

Dan

I seem to recall that one off the packages had a landclass fix for another scenery in that area.

Search your setup for the MAIW landclass files.

Create a new folder. Cut and paste the landclass .bgls into this folder.

Check if your problem goes away.

I have had issues with installing sceneries in the reverse order to which they were released.

It might be that two landclass .bgls are conflicting.

Add the bgl,s back one by one until it crashes again.

John