Physics in a separate worker process

Ok, I’m probably not the only thinking about that idea, but I would still like to hear the feedback/ideas/concerns of others who may have had the same thought.

I did actually got started on it, but haven’t made it far yet. Still, I would like to hear the feedback first, before I spend hours and hours on it, later realising it’s not possible because of xyz.

The issues I can think of right now:

• Async data (position, rotation, linear & angular velocity) – I guess that could be simply solved by having a dummy/proxy physics impostors on the main thread, that would only update the data
• Duplicate code - it would need to require to create separate version of each PhysicsPlugin as a worker version – not really sure if it would be possible to just simply reuse the PhysicsEngine container/wrapper on the worker side? Technically it seems it would be possible with webpack worker-loader (https://github.com/webpack-contrib/worker-loader#examples), but not fully sure yet.

I’m sure there were/must have been more issues related to workers, as I remember babylon having a worker for the native collisions, which were discontinued I think?

[deltakosh]

https://playground.babylonjs.com/#N7PGG3#2

[thomlucc]

Closing for no-activity. Feel free to re-open.