Ctd's and fs dll's error solved. NOT FSP's fault.

[Steve Mc Lean]

Hi all, I need to share what I found.

I finally solved my recuring CTD problems and they were "not" FSP related.

Somehow, FS doesn't like a lot of things that we tend to do with it particularily, with the add-on sceneries and their updates and fancy
panels. In my case, it turns out that most of the problems came from duplicate AFCAD files. These will crash FS straight to desktop
without any error report even so, many hundereds of miles away from the area you are flying.

To scan your AFCAD files, download the following tool: "scanafd 1.0" from, http://www.avsim.com/ . search for "scanafd.zip".
When you run it check the box, "show duplicates" in the left window you will see a list of duplicate AFCAD files you have and on the right
the details of each duplicate files; name size ect. choose the one you want to keep and, delete the others. You will find that scanning the
whole default scenery is not required unless you have added files there yourself.

Also, my second problem causing CTD's was related to some panels and the GPS utility causing the terrain.dll and gps.dll fault and the
error reports.

These were caused by corrupted nav data points used by some panels. The gps tries to map two coordinates for the same point and
goes nuts, the result, CTD. The only way I found to fix that is to avoid opening the GPS window when you use a panel that uses a FMC
using its own nav data such as some FDPA gauges and the Nav Data 2002 utility and like. I have tried to rebuild the index of the nav
database many times without results. It still CTD'ed FS but, by removing all references to the GPS in the Panel.cfg solved this. At least in
my case. By the way if anyone knows how to successfuly rebuild the nav databas of that program please let me know.

Also, the CTD's from above were also caused by some corrupted bgl files from sceneries, landclass or simply by a bad texture file, ex:
wrong format of bmp, that alone was enough to bring the gps.dll, terrain.dll fault and the ctd's.

Finally, at the very begining of my CTD galore, some were related to my updating of the FS voice pack. These were solved by restoring the
original one.

In conclusion, I used to CTD 7 out of 8 times before fixing all that. Now, I am 5 in 5 so far. I had to read a lot of posts before getting some
real answers and, in many different forums. But I must admit, even though I was tempted in pointing the finger at FSP, they were right, the
problem lied on my end of the stick.

Now, FSP still has some bugs but, most CTD's related problems come from FS and the way we handle the add-ons. At least in my case.
Hopefully the saga is behind me and now I can enjoy flying passengers around.

regards!

Steve

[pagir]

Thank you very much Steve!!!

I'll copy-paste this post in the Dan's CTD thread.

I hope it can be helpful!

Pagir