Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to correctly handle Mesh to Mesh collision checking? #611

Open
Levi-Armstrong opened this issue Nov 6, 2023 · 1 comment
Open

How to correctly handle Mesh to Mesh collision checking? #611

Levi-Armstrong opened this issue Nov 6, 2023 · 1 comment

Comments

@Levi-Armstrong
Copy link
Contributor

This seems to only be an issue when using FCL to collision check Mesh to Mesh using compute distance request when the two objects are in collision. When using primitive shapes and convex hulls this does not seem to be an issue because there is only ever one contact results, but for mesh to mesh and mesh to primitive/convex there are multiple contacts. Though when using distance there is no way to get all contacts when an a collision occurs between these two shapes. Is the correct way using FCL to detect this when using compute distance and the call the collide method?

@Dmitry-Sedov
Copy link

I faced the same problem. I used DynamicAABBTreeCollisionManagerd as a collision manager and put there all objects I had in the scene and then I used my variant of collision function that is defined in
void DynamicAABBTreeCollisionManager<S>::collide(void* cdata, CollisionCallBack<S> callback) const
In my callback I just saved all contacts fit to my expectations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants