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
At the moment, gravity is assumed to be a single simulation wide constant by the PoseIntegrator. Some simulations do not require gravity, and others may want to use per-body gravity of some form.
We can easily support the different use cases by letting the user supply a gravity callback in the same way that we support zero overhead narrowphase callbacks (generic structs). Since the pose integrator relies on body data in AOS format, it wouldn't be too terrible to rely on the user to provide the desired implementation.
The same sort of approach could be used to implement damping. The callback would effectively a general purpose velocity modifier.
The text was updated successfully, but these errors were encountered:
At the moment, gravity is assumed to be a single simulation wide constant by the PoseIntegrator. Some simulations do not require gravity, and others may want to use per-body gravity of some form.
We can easily support the different use cases by letting the user supply a gravity callback in the same way that we support zero overhead narrowphase callbacks (generic structs). Since the pose integrator relies on body data in AOS format, it wouldn't be too terrible to rely on the user to provide the desired implementation.
The same sort of approach could be used to implement damping. The callback would effectively a general purpose velocity modifier.
The text was updated successfully, but these errors were encountered: