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
This seems fairly straighforward to me. You loop through all the detected contacts, and check whether the skeletons associated with these contacts are the two skeletons which you are looking for.
However, in the latest version of the code, this tutorial actually does things differently:
auto collisionEngine = mWorld->getConstraintSolver()->getCollisionDetector();
auto collisionGroup = mWorld->getConstraintSolver()->getCollisionGroup();
auto newGroup = collisionEngine->createCollisionGroup(newDomino.get());
dart::collision::CollisionOption option;
dart::collision::CollisionResult result;
bool dominoCollision = collisionGroup->collide(newGroup.get(), option, &result);
This is much less easy to follow. I don't really understand what a CollisionGroup is, nor how to tell whether two particular objects have collided. However, there doesn't seem to be any documentation on this, because the only tutorial on collisions uses an outdated version of the code.
Please could somebody explain how I can achieve this, or update the tutorial to reflect the new code?
Thanks!
The text was updated successfully, but these errors were encountered:
This solution to this tutorial also throws a segmentation fault on windows since it uses make_shared to instance shared ptrs to classes containing vectorizable constructs vs using Eigen::make_aligned_shared. This is similar to #513
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
I'm trying to determine whether two particular objects are in collision with each other. In the tutorial on your webpage (http://dart.readthedocs.io/en/release-6.0/tutorials/collisions/#lesson-3c-compute-collisions), it suggests to do the following:
This seems fairly straighforward to me. You loop through all the detected contacts, and check whether the skeletons associated with these contacts are the two skeletons which you are looking for.
However, in the latest version of the code, this tutorial actually does things differently:
This is much less easy to follow. I don't really understand what a CollisionGroup is, nor how to tell whether two particular objects have collided. However, there doesn't seem to be any documentation on this, because the only tutorial on collisions uses an outdated version of the code.
Please could somebody explain how I can achieve this, or update the tutorial to reflect the new code?
Thanks!
The text was updated successfully, but these errors were encountered: