Quote:pagir wrote:
Did you update the edit voicepack recently???

Some crashes are related with it. See this thread:

(404: The post of this link doesn't existe anymore)

Those are the dates of the last Edit Voicepack Update from:

http://www.editvoicepack.com/DownloadOfflineUpdate.aspx

EditVoicepackUpdate2005-07-12_163509.EvpUpd 1872 kb 2005-07-12 16:35:09 6 days
EditVoicepackUpdate2005-07-05_181611.EvpUpd 1868 kb 2005-07-05 18:16:11 13 days
EditVoicepackUpdate2005-06-29_184331.EvpUpd 1867 kb 2005-06-29 18:43:31 19 days

As you know, The voicepack can update itself. So maybe you weren't aware of this update.

And as you can see, at least two updates were done about at the same time than FsP was released.

Please, confirm if your system is using edit voicepack or not.

Pagir

Quote:Okay, trying something else, loading another aircraft directly standing at a gate at EDDP - crash again. Next step
was loading Filemon.exe from
Sysinternals (http://www.sysinternals.com) to trace what my naughty Fs9 is doing on the harddisk. Last file was a
scenery bgl. Interesting, heard sometime
ago something about seasonal cdt.
Lets give it a try. Loading again, but change to dawn. Surprise, surprise - No Crash!
The same with dusk and night time - No Crash again. Loading at Daytime - Crash.
Change the date from 23.10.2005 to 23.09.2005 - No Crash!

I remember several similar crashes at airports in the past which have not been the default ones but addon
sceneries. When I deinstalled those
candidates the result was always no more crashes at the know active default ones.

My conclusion was, it must have to do something with the textures. A little research at http://forums.avsim.net/ gave
the easy and finally working
solution.

Simply loading Terrain.cfg to notepad and replace all

MaskClassMap=1 to MaskClassMap=0

and all

MaskClassMap=3 to MaskClassMap=0

From this point on everthing works fine again without crashes (fingers double crossed!). Found this in a thread
from 2002:

http://forums.avsim.net/dcboard.php?az=show_topic&forum=121&topic_id=186004&mode=full

Maybe this information may help some of you guys too!

Mick!

Quote:Steve Mc Lean wrote:
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

Quote:sascha wrote:
Hi all,
I have just found another issue which may help: the FS9 internal flight planner will not work from KSFO in the create flight menu, only if a
flight has already been started! Can'tt wait for an update!

Quote:Steve Mc Lean wrote:
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