You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2022. It is now read-only.
If I understand correctly from what I've seen in bevy_rapier2d, it looks like it actually stores all of the simulation data such as rigid body positions, etc. in the bevy ECS, by implementing the ComponentSet trait. With the way we have heron right now we are storing the physics world data in Bevy resources that use arena based storage.
I'm curious if that has any advantages performance or otherwise and if that would be a useful strategy in heron or not. I'm mostly just musing over the possibility, but do you have any ideas why we would want to or not want to do that?
The text was updated successfully, but these errors were encountered:
If I understand correctly from what I've seen in
bevy_rapier2d
, it looks like it actually stores all of the simulation data such as rigid body positions, etc. in the bevy ECS, by implementing theComponentSet
trait. With the way we haveheron
right now we are storing the physics world data in Bevy resources that use arena based storage.I'm curious if that has any advantages performance or otherwise and if that would be a useful strategy in
heron
or not. I'm mostly just musing over the possibility, but do you have any ideas why we would want to or not want to do that?The text was updated successfully, but these errors were encountered: