-
Notifications
You must be signed in to change notification settings - Fork 942
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
contact/exclude
appears to ignore links which are rigidly attached to the worldbody
#2444
Comments
Thanks! Can you please try to use "world" as the excluded body and report what happens? IIRC, bodies that are kinematically welded to the world are considered to be the world for collision purposes. If my suggestion above works then this is basically a documentation issue. If not, we will examine more carefully. |
Mmmm this is technically documented but is rather hard to find. Assuming my diagnosis is correct, the |
Interestingly, setting
vs what I got with |
Thanks, I'll investigate. |
You're right, my mistake. In fact, this is almost word-for-word the "Surprising Collisions" section from the docs, which I hadn't found before now: https://mujoco.readthedocs.io/en/stable/overview.html#surprising-collisions |
Intro
I'm a researcher at Boston Dynamics.
My setup
I'm using the latest release 3.2.7 for linux x86_64.
What's happening? What did you expect?
Here's a minimal model that illustrates the problem. First, a working version:
This model consists of three spheres, each of which overlaps with the others. Collision between body_1 and body_2 is ignored because they are direct ancestors in the kinematic tree, likewise body_2 and body_3. I have manually excluded collision between body_1 and body_3 with a
contact/exclude
group. This all works correctly: When I run./bin/simulate minimal-repro.xml
, the three spheres fall together.However, if I remove the
freejoint
, like so:then body_3 immediately shoots away, presumably due to the collision with body_1.
I have also tried
<compiler fusestatic="false"/>
(even though I expect that to be the default), and it had no effect.Steps for reproduction
./bin/simulate
from the latest Mujoco release (3.2.7)Minimal model for reproduction
Code required for reproduction
No response
Confirmations
The text was updated successfully, but these errors were encountered: