I'm using MultiThreadedCall() to run a method that needs to create a lot of PathObstacles. However, sometimes it will crash (with an access violation) on the call to create() for some random PathObstacle. It seems to be completely random, i.e. it works fine most of the time, So I'm guessing one thread is trying to create a PathObstacle on a PathWorld at the same time as another thread.

If I create all the PathObstacles without using MultiThreadedCall(), then I don't seem to run into the problem. It just a lot slower.

If it isn't thread safe, any chance of making it thread safe? I know I can use CritSect, but was hoping it could be thread safe by default in EE.

Thanks for the reply, but unfortunately this has nothing to do with PhysX. I'm talking about the recast nav mesh obstacles.

I'll wait to hear from Esenthel before pursuing that.

This func is not multi threaded safe
It should be called only on main thread
Multi threaded improvement of that func is on the roadmap

OK, thanks. It will be a major help. At the moment, creating obstacles in a multi threaded environment is a real hit and miss thing. Sometimes, they create, sometimes they don't other times you just get access violations. Looking forward to it.