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

Unreliable plane-mesh collision detection #1235

Merged
merged 4 commits into from
Feb 11, 2019
Merged

Unreliable plane-mesh collision detection #1235

merged 4 commits into from
Feb 11, 2019

Conversation

mxgrey
Copy link
Member

@mxgrey mxgrey commented Feb 8, 2019

This PR is only for illustrative purposes. We can go ahead and decline it whenever. I just wanted to present a test that illustrates the findings that I reported in #1234.

I've noticed that the ODE collision detector can have totally inconsistent results in between tests, and the results also seem to be very sensitive to the order in which the tests are run (e.g. if you change the order of the some of the elements in the for-loops, the results can be dramatically different). This makes me suspect that there's some very serious undefined behavior occurring, either in our ODE wrapper or in ODE itself.

@jslee02
Copy link
Member

jslee02 commented Feb 8, 2019

I suggest merging this tests as disabled tests to have this tests compiled sussessfully with future changes.

@mxgrey
Copy link
Member Author

mxgrey commented Feb 11, 2019

Good idea! I've added the DISABLED_ label to them!

@mxgrey mxgrey changed the title [Never merge] Unreliable plane-mesh collision detection Unreliable plane-mesh collision detection Feb 11, 2019
@jslee02 jslee02 merged commit ca2dcd6 into release-6.8 Feb 11, 2019
@jslee02 jslee02 deleted the issue1234 branch February 11, 2019 02:33
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

Successfully merging this pull request may close these issues.

2 participants