assert setNeedToTestOverlap after modifying collisionbitmasks

[InfantEudora]

Hi. Thanks for this great and easy to use library.

I've recently upgraded from 0.9.0 to 0.10.2. And now noticed the following that I couldn't explain.

When I have a body with type::static with a dynamic body resting on top of it (with gravity): what I was previously able to do (in 0.9.0) was modify the static body to become dynamic. And they would both fall down as expected. The dynamic body would push the previously static body down.

In the new version, it crashes on the assert in OverlappingPairs::setNeedToTestOverlap().
The same happens when modifying the collision bitmasks while a body is currently in contact with another body.

It does work if I set the body to inactive first, then modify it's bits or type, and then set it to active all before running a new world update.

[MonsieurBleu]

I think I might have the exact same problem as you, and you saved my day ! In my case, I have a level editor and got the same exception while trying to move a table with a dynamic object on top of it. In gdb I saw that the problem is the existence of a pair inside the entity's related component that isn't inside the global pair list of the world.

Setting the body to inactive when modifying it fixed my problem, so many thanks to you. I don't know if it's a specific bug of RP3D, because in insight, it's not a really good practice to modify such data on a static body. It's like changing your tire while on the highway.

If it can help, my crashes where triggered with both setType and setTransform methods. I think anything that could interact with the overlapping pairs of the broad system could do the same thing.