Enabling USE_SEPDISTANCE_UTIL2 requires 100% reliable distance computation, but there are issues with large size rations. todo: fix this

Make synchronizeMotionStates() pure virtual in btDynamicsWorld and public in btDiscreteDynamicsWorld. Thanks Chunky.
This commit is contained in:
erwin.coumans
2008-11-08 19:27:53 +00:00
parent 3e9af21cec
commit 075ba0b9d9
4 changed files with 13 additions and 7 deletions

View File

@@ -27,7 +27,11 @@ subject to the following restrictions:
class btConvexPenetrationDepthSolver;
#define USE_SEPDISTANCE_UTIL2 1
///Enabling USE_SEPDISTANCE_UTIL2 requires 100% reliable distance computation. However, when using large size ratios GJK can be imprecise
///so the distance is not conservative. In that case, enabling this USE_SEPDISTANCE_UTIL2 would result in failing/missing collisions.
///Either improve GJK for large size ratios (testing a 100 units versus a 0.1 unit object) or only enable the util
///for certain pairs that have a small size ratio
///#define USE_SEPDISTANCE_UTIL2 1
///ConvexConvexAlgorithm collision algorithm implements time of impact, convex closest points and penetration depth calculations.
class btConvexConvexAlgorithm : public btActivatingCollisionAlgorithm