Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
The whole point of the btTransformAabb computations are to take rotation into
account.
This method is being used by several collision shapes, including btBoxShape:
void btBoxShape::getAabb(const btTransform& t,btVector3& aabbMin,btVector3&
aabbMax) const
{
btTransformAabb(getHalfExtentsWithoutMargin(),getMargin(),t,aabbMin,aabbMax);
}
If there would be a failure in the btTransformAabb, the broadphase collision
would fail and collisions would be missed, which would be very obvious. See
attached demo to visualize the aabb generated by btTransformAabb for arbitrary
rotations (not just 90 degrees).
Can you explain more in detail why you think there is a problem, and create a
reproduction case that shows the issue?
Original comment by erwin.coumans
on 19 Sep 2011 at 7:27
Attachments:
Ohhh, I missed the absolute() call on the basis matrix. That's a cute trick,
will have to remember that!
Nevermind! :)
Original comment by ejtt...@gmail.com
on 19 Sep 2011 at 7:55
no prob, I got the idea from Gino van den Bergen ( http://dtecta.com )
Original comment by erwin.coumans
on 19 Sep 2011 at 10:08
Original issue reported on code.google.com by
ejtt...@gmail.com
on 18 Sep 2011 at 3:21