29-03-2008, 11:06 PM
Since I had problems in the past with crashing in to buildings at airports (even though I was well away from them), I had disabled Force Crash Detection (1) and disabled Force Collide Detection (1) under "more options.cfg.". But, after a 2 1/2 hour flight from KATL to KDFW, FSP detected a collision as I was pulling up to the gate. Visually I had to be 20 yards or more away from anything, and FSP showed the speed as one knot. Not only did this erase a good flight, but it also prevented me from recording it in my DeltaVirtual ACARS.
Needless to say, I'm quite peeved - but understand things aren't perfect. In any event, just what can I do to prevent this from happening
again? I sure don't want to have to park away from the terminals - and, in fact, I had problems at KSLC when FSP showed I was hitting
objects even while on taxiways well away from any buildings??? Help with this very frustrating situation would be greatly appreciated.
And yes, I'm using add-on sceneries that are stored and configured in the proper place. Using FS9 BTW.
Post Edited ( 03-29-08 23:09 )
Needless to say, I'm quite peeved - but understand things aren't perfect. In any event, just what can I do to prevent this from happening
again? I sure don't want to have to park away from the terminals - and, in fact, I had problems at KSLC when FSP showed I was hitting
objects even while on taxiways well away from any buildings??? Help with this very frustrating situation would be greatly appreciated.
And yes, I'm using add-on sceneries that are stored and configured in the proper place. Using FS9 BTW.

Post Edited ( 03-29-08 23:09 )