Results 1 to 6 of 6

Thread: release droppable objects = object collision crash

  1. Default release droppable objects = object collision crash

    I have the weirdest bug in my FSX Acceleration program. Every time I release a droppable object I get an immediate end of mission/flight with the "Object Collision" notation. It doesn't matter whether I use a keyboard combo or assign a button Thrustmaster HOTAS X, the end result is the same. I think the first time I noticed it was after I tried to do a combat mission w/ my (legitimate) Iris PC-9. I thought maybe the bug was in that aircraft but it does it with the default Beaver when I fly the Tassie I adventure mission as well . In the "Lost in the Triangle" mission I can release both cargo pods from the Lear without an issue.

    Anyone else have or had a similar problem?

    Thanks in Advance.

    M. Slim

    WinXP Pro SP3 Intel Core Duo CPU E7500
    2.93ghz 2GB Ram ATI Radeon HD4350
    Last edited by mslim; 01-25-2012 at 07:42 PM. Reason: edited for clarity

  2. #2
    Join Date
    Nov 2006
    Salinas, CA



    I have Acceleration on Win 7 64 bit and had to turn off detect collisions with other aircraft (crash detection on) to prevent a crash when dropping an object. I had the problem on XP but never identified the cause.

    Jim F.

  3. #3


    I had a similar promblem as well. I determined that the issue was with the aircrafts C.O.G, and the corresponding contact points in the aircraft.cfg (or something). I suspect that it is just a bug with some of the aircraft, and/or what the aircraft is doing at the time of release. Is it happening when the aircraft is climbing/descending?

  4. Default

    Quote Originally Posted by jandjfrench View Post

    had to turn off detect collisions with other aircraft (crash detection on) to prevent a crash when dropping an object.

    Jim F.
    This fix eliminated the condition with the DH Beaver. I will try it w/ the Iris PC-9 combat scenario and see if it works also. I wonder if the airplane "sees" the dropped object as another nearby aircraft and interprets it as a collision?? Maybe because the "Lost in the Triangle" Lear is doing 250 KIAS it sees no conflict w/ the dropped object? Or.. it could be as blackout11c says and has to do w/ contact points.
    M. Slim
    FSX-SE ; Win7 Pro i7-6700K 3.50GHz 6MB
    ASUS Z170-K ATX mobo ; Ripjaws 8gb DDR4/3000MHz RAM
    NVIDIA GeForce GTX 970 4GB GDDR5 ; 512GB Samsung 850 PRO

  5. #5


    Yes, the droppable objects are other aircraft. This is because the droppable objects are also simobjects, they all have the .cfg's. This means that they are interpreted as other vehicles (not just aircraft), and then cause a collision. I revise my previous post - turning off collisions is the only way to fix this, unless your aircraft is travelling fast enough for the object to clear the collision boundrys before FS reads a collision.

  6. Default

    Turning off the crash detection will certainly fix this crash problem, but in the case of missions, you loose all other crash detection capability. A simple change to the aircraft.cfg file solves this problem WITHOUT turning on "Crash Detection". Check out Forums at for this solution and many more that plague FSX.

Similar Threads

  1. droppable object issue
    By hendrik357 in forum FSX
    Replies: 2
    Last Post: 04-08-2015, 02:58 PM
  2. Droppable Objects, how to define them?
    By degeus in forum Prepar3D
    Replies: 0
    Last Post: 12-12-2013, 07:56 AM
  3. List of Defaut Droppable Objects
    By bretwizer in forum FSX
    Replies: 2
    Last Post: 12-10-2011, 10:16 AM
  4. Droppable Objects
    By jamarogers in forum FSX
    Replies: 0
    Last Post: 06-05-2009, 09:55 AM
  5. Replies: 0
    Last Post: 01-17-2004, 11:17 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts