5 ms·
One of my grievances with most engines is a poor story around networked physics. It’s desirable to me to be able to leverage historical physics states in a perf
by piefayth 4y ago
One of my grievances with most engines is a poor story around networked physics. It’s desirable to me to be able to leverage historical physics states in a performant way, sometimes querying or stepping many modified versions of those states at once.
Bevy’s data oriented design seems great for the kind of stateless physics required here, but I couldn’t find any physics OR networking features in a quick five minute browse. Is this something that is well supported by Bevy today, or will be in the future?
- _cart 4y agoWe haven't (yet) prioritized an official physics plugin for Bevy, but the Rapier physics engine has their own official Bevy plugin, which is the de-facto standard at this point. It supports opt-in determinism, which should be great for some networked physics scenarios. https://rapier.rs/docs/user_guides/bevy_plugin/getting_started_bevy https://rapier.rs/docs/user_guides/bevy_plugin/getting_start... The story is similar for networking. Ultimately we will have a built in api, but we're focused on more fundamental things at the moment. There are _tons_ of community-developed networking plugins though: https://bevyengine.org/assets/#networking https://bevyengine.org/assets/#networking