-
Notifications
You must be signed in to change notification settings - Fork 41
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
Fix collision issue with detachable joints #31
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The issue occurs if a model is spawned and is attached to a parent model without a call to `step()` in between. This should be fixed in DART, but in the meantime, we can just call `incrementVersion` after `moveTo` is called on a DART BodyNode.
Just to clarify, what's the issue that occurs? Does one of the models fall through the floor? |
mxgrey
approved these changes
Apr 20, 2020
5 tasks
Yes, the child model falls through the floor. It appears that the moved BodyNode and its descendants are not added to a CollisionGroup in DART which prevents any collision between the moved BodyNodes and other BodyNodes from being detected. Sorry, I should described the issue better. |
nkoenig
reviewed
Apr 20, 2020
nkoenig
approved these changes
Apr 22, 2020
Signed-off-by: Addisu Z. Taddese <addisu@openrobotics.org>
7 tasks
azeey
added a commit
that referenced
this pull request
Jun 24, 2021
…268) When a joint is created between BodyNodes in different skeletons, the child BodyNode is moved to the skeleton of the parent BodyNode. When this happens, the BodyNode version of the child needs to be incremented. This is actually fixed by dartsim/dart#1445, but we don't have that merged into our fork. So in the meantime, we call incrementVersion after moveTo is called similar to #31. Signed-off-by: Addisu Z. Taddese <addisu@openrobotics.org> Co-authored-by: Louise Poubel <louise@openrobotics.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue occurs if a model is spawned and is attached to a parent model without a call to
step()
in between. This should be fixed in DART, but in the meantime, we can just callincrementVersion
aftermoveTo
is called on a DART BodyNode.