I would like to enable crash detection again, but have three problems with it.  Can any, or all, of these be alleviated?

1 - on takeoff or landing I sometimes get a "building crash" notice ...even though I'm on a clear runway!

2 - on approach, with landing clearance, an AI will fly through me, causing my plane to disintegrate into flaming debris while the AI flies on to land unscathed!  (I at least want him scathed also!)

3 - after crash detection, FS9 immediately resets the flight.  This entails several minutes of black screen during which I can do nothing (unless I invoke Task Manager and shut down the sim), before I am again sitting in the cockpit at my departure point.  (I have installed the "Massive Crash" files but have never seen them because of this.)  Plus, unless I detect the crash before FS9, I can't hit pause and exit so at least getting the flight time in my logbook.  Can crash detection be enabled without the automatic flight reset?

BrandonF wrote on Nov 6^th, 2010 at 8:30pm:


Just hit ESC when I'm ready.

Thanks, Groundbound1.  I've had that utility for a while, but not the tutorial;  time to play with it some more (the utility!).

Don't know which is less "as real as it gets" - having planes move through each other as if they're phantoms (nebulous, not F4s) or having them trash me and fly away;  the latter being more irritating, I guess I live with 'no aircraft collisions'.   Though it seems if I have landing clearance and am on final, ATC wouldn't let the AI run over me like that.

There is an AutoSave utility which will save the flight at specified intervals, but it suffers the same problem as manually saving a flight and returning later (which is the same as I'm trying to avoid from that "building crash" and automatic reset after a long flight):  all flight data prior to the resumed save is lost so my logbook is inaccurate.   So I continue flying with no crash detection ...and learn nothing from hard landings.

big fireball on crashing.. Nick's Massive Crash Final,  add:

visual_damage=1

to the end of EACH [fltsim.#] as seen below to your aircraft's .cfg file.

[fltsim.0]
title=Cessna Skyhawk 172SP
sim=Cessna172SP
model=
panel=
sound=
texture=
kb_checklists=Cessna172SP_check
kb_reference=Cessna172SP_ref
atc_id=N176CM
ui_manufacturer=Cessna
ui_type="C172SP Skyhawk"
ui_variation="White with blue and gray"
description="A stable and trustworthy plane, most pilots have logged at least a few hours in a Cessna 172, since it's the most widely available aircraft in the rental fleet, and is used by most flight schools. Since the first prototype was completed in 1955, more than 35,000 C172s have been produced, making it the world's most popular single-engine plane.  One of Cessna's first tricycle-gear airplanes, the 172 quickly became the favorite of a growing class of business pilots.  Its reliability and easy handling (along with thoughtful engineering and structural updates) have ensured its continued popularity for more than 35 years."


for refference, i used the Default Cessna 172.  this will work in ANY aircraft that has crash damage modeled into it durring design stages.  (you may experience wings ripped off, tail ripped off, sparks, and smoke - but this also depends on altitude at point of initial impact)  Your flight will not RESET until after you hit the ground.

Capt.Propwash wrote on Nov 8^th, 2010 at 1:59pm:


I had done that even before  adding the massive crash files.  But when I experience an operator error situation, FS9 pops up the crash notice window immediately, then locks the keyboard so I can do nothing til the flight has been reset (except use the three finger salute).  I have a couple of seconds to read the popup before the screen goes black.

1olehippy wrote on Nov 9^th, 2010 at 6:50am:


FYI - One reason that I keep "crash detection" turned off is that I use a number of freeware airport enhancements - which are composed of various "objects" like buildings etc.

Apparently some (or perhaps most) of the object creation programs have the option to encase the object with an invisible "crash box" (for what reason I do not know) and that option is on, by default.

Many designers obviously forget to turn it off prior to compiling the object and never test throughly enough to find that it exists and can cause problems.

I can easily tell if and when I "crash" so have never found it necessary to have that FS option turned on.  This of course means that I have no issues with objects either.

One can exclude the offending buildings (objects) but that seems a bit like throwing out the baby with the bath water. The buildings etc. are what makes the scenery enhancement visually interesting.

Just a few thoughts on the subject.