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

collide returns false on overlaping concave meshes #492

Closed
MFridlyand opened this issue Sep 1, 2020 · 2 comments
Closed

collide returns false on overlaping concave meshes #492

MFridlyand opened this issue Sep 1, 2020 · 2 comments

Comments

@MFridlyand
Copy link

I load two meshes from *.obj files and make BVHModel from them. One mesh is completely inside another, they don't intersect, but overlap. collide call returns zero contacts and distance call returns positive distance. I looked inside code and it looks like it could be reproduced on any noninstersecting overlaping meshes.

fcl_resources.zip

@SeanCurtis-TRI
Copy link
Contributor

That's got to be due to #488. Let me look into it quickly.

@SeanCurtis-TRI
Copy link
Contributor

Oops. My bad. I saw "concave" and thought "convex". This is wholly unrelated to #488.

The true answer is one that is not going to make you happy. The non-convex meshes cannot detect contact if the surfaces are not in contact. This is due to the fact that the algorithm being used to detect contact between general meshes makes no assumptions about meshes having an "inside" or an "outside" and therefore only detects contact on the surface. So, the scenario you describe will invariably be missed by FCL. There is no expectation (at least, none that I've heard) that this behavior will change any time in the future.

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