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
The velocity projection considers one face fixed in space (i.e. current unprojected configuration), while doing a linear velocity based projection of the other face (e.g. into it's opposing contact face friend) and then checks to see if the interpen exceeds the max allowable. This was tested on problems where one object is stationary and the other is an incoming impactor.
The issue is that when both objects are coming toward each other, the current approach may not actually trigger a tribol dt vote, but excessive interpenetration may exist.
Solution:
Consider comparing one face's projected configuration against the other faces PROJECTED configuration. This will catch the case where the next cycle's current configuration is an interpenetrated configuration that has resulted from BOTH objects opposing velocities.
The text was updated successfully, but these errors were encountered:
The velocity projection considers one face fixed in space (i.e. current unprojected configuration), while doing a linear velocity based projection of the other face (e.g. into it's opposing contact face friend) and then checks to see if the interpen exceeds the max allowable. This was tested on problems where one object is stationary and the other is an incoming impactor.
The issue is that when both objects are coming toward each other, the current approach may not actually trigger a tribol dt vote, but excessive interpenetration may exist.
Solution:
Consider comparing one face's projected configuration against the other faces PROJECTED configuration. This will catch the case where the next cycle's current configuration is an interpenetrated configuration that has resulted from BOTH objects opposing velocities.
The text was updated successfully, but these errors were encountered: