Real-Time Physics Simulation Forum

Hi guys - I couldn't find information on this anywhere: How thread-safe is the bullet API? As an example, could I create a btCollisionShape on one thread, update its local scaling on a second, and then add it to a btDyamicsWorld on a third, before say, removing it from a fourth? (Free threading)

Or do I need to be more careful? (Single-threaded only or explicit synchronization)

I'm only talking about thread safety with respect to calling the API, not synchronization that must be done on my own side (e.g. updating shared lists of rigid bodies etc).

Sorry to bump, but I'd really like some further insight on this one! - At the moment I'm coercing all calls through a single "master" thread just to be safe.

Some files are not thread safe (especially the MLCP solvers), but most things will be safe as long as you do it before stepping. If you want heavy thread safety and multithread support, there's a great fork on github that makes everything far easier (and sometimes faster)

And there is a thread on these forums that talks about that multi-thread fork.