Tow times in a row, one with the MADDOG2006, the other with the LDS 767. At two different places?I have FSUIPC disabling this though since I fly with RCv4.I checked I was OK with the RAM and page file...Anyone with any idea?ThanksGhiom

On none of the 2 airports, I had an open runway with no start locations.I fixed it and I flew again there with no CTD!For the other airport, there was no problem.Is the fault that I have known for causing this type of CTD?ThanksGhiom

Any active FS9 AFCAD file containing a runway without start locations or having double ones for the same runway will cause CTDs, almost always during any stage of your approach to that airport.Hans

Thanks for your reply.Can you please confirm it will happen only to THAT specific airport?ThanksGhion

All I can confirm is that AFCAD errors are the most frequent causes of CTDs in FS9. However, corrupt addon texture files will also cause CTDs, the main differences being that AFCAD CTDs mostly occur when still at between 10 and 20 miles from the destination airport, while texture CTDs will occur as soon as the corrupt texture becomes visible.Hans

ThanksWhat do you call a corrupt texture?can this be detected easily, I mean automatically?For the feedback, my ATC.DLL CTD occured as soon as I had touched the runway (open runway with no start location in the AFCAD file).Thank youGhiom

Yeah, that would be great to know how to determine if a texture is, (or has been), corrupted. Would be quite a coup for the entire FS community. Please tell us how to make that determination if you know!Mark

Yeah, that would be great to know how to determine if a texture is, (or has been), corrupted. Would be quite a coup for the entire FS community. Please tell us how to make that determination if you know!Mark

But a texture fault will not give an atc.dll error, which is what is being discussed here.Texture problems often relate to reflections (especially if neither Render to Texture or Reflections are turned on) and will give ntdll.dll or fe.dll (aircraft textures) or g3d.dll (scenery textures) failures. You can sometimes spot the textures as they are not the normal sizes.John

Be sure you have the FS 9.1 service pack installed. While it did not cure the atc.dll completely, it improved things and the FSUIPC statement "RemoveATC=Yes" in its general section for 3.85 or better should have helped.I suspect if tuning is the culprit RC will possibly read the ground frequency when you touch down as the next call will be to exit the runway contacting ground at xxxx when off the runway. Also post on the RC forum here at AVSIM and state your approach, tower, and ground frequencies used.For others, the RemoveATC statement is only for those not using FS ATC.

But a texture fault will not give an atc.dll error, which is what is being discussed here.Texture problems often relate to reflections (especially if neither Render to Texture or Reflections are turned on) and will give ntdll.dll or fe.dll (aircraft textures) or g3d.dll (scenery textures) failures. You can sometimes spot the textures as they are not the normal sizes.John

Thanks John, that is interesting information. It's one of those things that you would know pretty well I think! Sorry if I chimed in about the corrupted texture thing...always wanted an easy solution to that and didn't mean to hijack the thread :)Mark

Any active FS9 AFCAD file containing a runway without start locations or having double ones for the same runway will cause CTDs, almost always during any stage of your approach to that airport.Hans

I have not been able to duplicate your assertion regarding missing start locations causing CTDs.Just finished several tests where I deleted the start locations at several airports and then flew into them with no issues whatsoever.It has been my understanding that start locations are only used to offer a selection in the go to airport dialogue.There is no mention in the Afcad documentation of missing start locations causing a CTD problem when landing. All Mr. swrody says is that there "may" be a problem if you are wanting to start your flight on the "active" runway and there is no start location present.If others have experienced a CTD due to missing start locations I hope they will chime in.

Is there a tool that can detect corrupt AFCADs and textures?

I have not been able to duplicate your assertion regarding missing start locations causing CTDs.Just finished several tests where I deleted the start locations at several airports and then flew into them with no issues whatsoever.It has been my understanding that start locations are only used to offer a selection in the go to airport dialogue.There is no mention in the Afcad documentation of missing start locations causing a CTD problem when landing. All Mr. swrody says is that there "may" be a problem if you are wanting to start your flight on the "active" runway and there is no start location present.If others have experienced a CTD due to missing start locations I hope they will chime in.

I agree. I have discovered many less-than-perfect AFD files provided with freeware that lack all sorts of things, including start points. But none of these have caused Flight Simulator to crash - just strange behaviour.

Is there a tool that can detect corrupt AFCADs and textures?

Both Lee Swordy's free but old AFCAD2 software and the payware AFX have built in error checking, although it seems about 90% of scenery developers don't bother to use it. But errors do not create corrupt files. I have only occasionally encountered corrupt files caused during editing in AFX where, for some reason, every node gets a direct apron link to one specific node. But this just causes taxying route errors, not software crashes.The only cause I know of for software crashes is conflicting AFD files - usually when the airport co-ordinates are not the same. It is easily solved by eliminating duplicate AFDs - it will not happen if you only have MS's base details and one add-on AFD file.I know of no tool to detect bad textures. Generally, problems arise with wrong-format textures rather than corrupt ones. Identifying the origins of software crashes caused by these and other issues can often only by done by the tedious process of systematically temporarily eliminating some or all add-on aircraft and sceneries. It may take many hours on a large FS installation and requires much patience. Unfortunately, problems of this sort are a risk that we take when installing quantities of free add-on features.John