[bug] collision reporting crashes Max when jit.phys.body has children

    Jan 03 2012 | 11:49 pm
    just noticed this when I started getting these weird "freeobject: 3a8a8ec0: bad object" errors.
    When I add few children to jit.phys.body and enable collision reporting in jit.phys.world, Max outputs these errors and if I try to use [dict] to collect collisions Max crashes. Same happens in the help patch of jit.phys.body if you enable collisions in jit.phys.world....
    Using Max 6.0.2 on Win7 64bit
    Any ideas what causes this? Seems like jit.phys.world doesn't like to report children collisions :/

    • Jan 04 2012 | 5:30 pm
      thanks for the report!
      i can reproduce and will have a fix for the next update.