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
A btRigidBody with all zero m_linearFactor but non-zero m_angularFactor should still collide with other static objects which changes the angular velocity. But due to the code in btSequentialImpulseConstraintSolver.cpp: solverBody->internalSetInvMass(btVector3(rb->getInvMass(), rb->getInvMass(), rb->getInvMass()) * rb->getLinearFactor()); in btSequentialImpulseConstraintSolver::initSolverBody
and if (!solverBodyA || (solverBodyA->m_invMass.fuzzyZero() && (!solverBodyB || solverBodyB->m_invMass.fuzzyZero()))) in btSequentialImpulseConstraintSolver::convertContact
the collision will not occur
The text was updated successfully, but these errors were encountered:
JiangboYu13
changed the title
btRigidBody with all-zero m_linearFactor and non-zero 'm_angularFactor ' will not collide with onther static objects btRigidBody with all-zero m_linearFactor and non-zero 'm_angularFactor' will not collide with onther static objects
Feb 21, 2024
JiangboYu13
changed the title
btRigidBody with all-zero m_linearFactor and non-zero 'm_angularFactor' will not collide with onther static objects btRigidBody with all-zero m_linearFactor and non-zero m_angularFactor will not collide with onther static objects
Feb 21, 2024
A
btRigidBody
with all zerom_linearFactor
but non-zerom_angularFactor
should still collide with other static objects which changes the angular velocity. But due to the code in btSequentialImpulseConstraintSolver.cpp:solverBody->internalSetInvMass(btVector3(rb->getInvMass(), rb->getInvMass(), rb->getInvMass()) * rb->getLinearFactor());
inbtSequentialImpulseConstraintSolver::initSolverBody
and
if (!solverBodyA || (solverBodyA->m_invMass.fuzzyZero() && (!solverBodyB || solverBodyB->m_invMass.fuzzyZero())))
inbtSequentialImpulseConstraintSolver::convertContact
the collision will not occur
The text was updated successfully, but these errors were encountered: