Obi roadmap

[whack]

The compute-based backend is still WIP, but many basic features have already been implemented.

Its biggest limitations stem from the fact that bringing simulation data from the GPU back to the CPU is extremely costly. It can be done asynchronously (let the GPU know that you need the data, continue running things in the CPU, get the data a few frames later) but this introduces latency. So two-way rigidbody interaction is probably out the window, since you need data from the GPU, and you need it the same frame it's been produced. Also, many things you'd be able to do in CPU-based backends will be harder or outright impossible to do in the compute backend. So it will be mostly aimed at pure eye-candy, simulations where you don't need to retrieve data every frame for gameplay reasons.

You can see it in action here (in the context of fluids/cloth, though):
https://www.youtube.com/watch?v=7w2D2rYEk1M
https://www.youtube.com/watch?v=BQzZzQMl7x8


Though I do get help with forum/webpage maintenance, it's just me 95% of the time . Thanks!

That second one reminds me of an old Sony ad: https://www.youtube.com/watch?v=0_bx8bnCoiU

If I remember correctly, the Xbox 360 was the first consumer machine to have shared addressable memory, which gave it rather ridiculous cpu-gpu bandwidth for its time. It's a shame that architecture never took off.

Still, not to add more to your plate, but the gpu backend would be a pretty cool feature.