-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Collision Detection Problems with b2ContactEdge and b2Distance #766
Comments
Are calling b2Distance directly? I need the data you are sending to that specific function. The world dump doesn't give me the data you send to that function. You'll have to print the input yourself somehow. I'm guessing you increased |
Is there some cleaner way to accomplish this printout of the data other than going through the docs and printing every member of every struct and class used? This is the code being used to try and detect the collisions, would I be trying to print all the fields relevant to dO, dc, and di?
|
Set a breakpoint before the call to Here is some example data I captured in Visual Studio.
|
@erincatto Apologies for the delay, here is a a dump of what was contained in di right before the function call. Is the
|
Closing out v2 issues since it is no longer supported. |
Hi there! I am currently working with the author of mvsim: https://github.com/MRPT/mvsim, which is a robot simulator which uses Box2D for collision detection. Box2D works great for preventing objects from penetrating each other. However, when we try to set a flag to true to expose this collision to the user, the behavior is inconsistent. Specifically, the problem seems to happen mostly when two edges are face to face (parallel), but occasionally happens for corner edges.
Current there are two techniques used to detect collision:
Here is a link to the issue in which we are discussing this problem: MRPT/mvsim#42
Any help would be greatly appreciated! Is there a better way to detect collisions than this method?
Attached below is the dump file as requested as a follow up from my Discord post, where the robot crashed head on into an obstacle, and using both 1 and 2 failed to detect the collision:
box2d_dump.zip
The text was updated successfully, but these errors were encountered: