btCollisionDispatcherMt), this eventually slows down the simulation. I did a few experiments and here is what I found:
When using both multi-threading and compound shapes, the function btCollisionDispatcherMt::releaseManifold will be called, but the variable m_batchUpdating will always be true during the simulation. Then I found the compoundcompound collision algorithm will attempt to deallocate collision algorithms while it is processing collisons. When the collision algorithm deallocates, it will release the contact manifold and in then calls the btCollisionDispatcherMt::releaseManifold. But because this funciton is called while the compound algorithm is processing collisions, the member m_batchUpdating will always be true, because the collision is processed in the parallel for after m_batchUpdating is set to true. As a result, this section of the code will never get run during the simulation and m_manifoldsPtr will keep increasing.
Is this a potential bug, or I'm missing something?Statistics: Posted by desaic — Thu Oct 28, 2021 6:18 pm
]]>